September 2009 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] State of Devel Projects for Factory?
by Andreas Jaeger 02 Sep '09

02 Sep '09

With the factory opening, we have named a couple of projects as development projects for factory. It was also suggested to document in the OBS project page the purpose and communication channels of the devel project (http://en.opensuse.org/Factory/Packaging). Where are we with this? What do you think is missing? How are the teams itself working? Andreas -- Andreas Jaeger, aj(a){novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

1 0

[opensuse-packaging] Known vulnerability in phpMyAdmin
by Javier Llorente 02 Sep '09

02 Sep '09

Hello listmates, There is a known vulnerability in phpMyAdmin 3.2.0, which is the version available in the OBS (server:php:applications). It's considered to be serious. http://www.phpmyadmin.net/home_page/security/PMASA-2009-5.php The latest version fixes that. Two months ago I submitted a request to update phpMyAdmin to 3.2.0.1. I waited and there was no response. So I contacted the maintainer... I waited and got no response. I understand that we could have more work to do in some periods of the year or that we could be on holidays ;-) Anyways, a few weeks ago I revoked that request (15315) and created a new one since there's a new version of phpMyAdmin (3.2.1). So, could anyone take a look at my request (18482) to update phpMyAdmin to 3.2.1? :-) Thanks, Javier

2 3

[opensuse-packaging] query - Linking in another project.
by doiggl＠velocitynet.com.au 01 Sep '09

01 Sep '09

Hello, I am trying to build the wflogs rpm and have gotten the result back It says - checking for shl_load in -ldld... no configure: error: wfnetobjs-incdir: no directory found, use configure option error: Bad exit status from /var/tmp/rpm-tmp.36404 (%build) References: project -> https://build.opensuse.org/package/show?package=wflogs&project=home%3Adoiggl spec file -> https://build.opensuse.org/package/view_file?file=wflogs.spec&package=wflog… logs -> https://build.opensuse.org/package/live_build_log?arch=x86_64&package=wflog… I know I need to include or depend on Package wfnetobjs. It is located in another persons project -> https://build.opensuse.org/package/show?package=wfnetobjs&project=home%3Ael… Ouestions. ========= 1. How do I link in wfnetobjs to my wflogs project so it can compile. 2. There are possible parameters I can use Parameter switches e.g --with-wfnetobjs-incdir --with-wfnetobjs-library --with-wfnetobjs-libdir An example I have seen in the past is ./configure --with-wfnetobjs-libdir=/usr/include/wallfire/ 3. Where in the spec file does the line go, if so which section ? Any help appreciated Cheers Glenn. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

4 10

[opensuse-packaging] new versions for 11.2
by Stephan Kulow 01 Sep '09

01 Sep '09

Hi, The distribution is in feature and version freeze since Aug 06 and still I see a daily flood of version updates. To make this crystal clear: I want to know _forehand_ about the reasoning of every version update. Basically I want to see a reasonable risk vs. value check. There is no point in doing version updates because we can. Examples: Keinnutzen 0.1 is in the distribution, but noone cares about this package anyway - and noone checked that 12.4 is available since 2004. Value of doing the update: none! Risk: unknown -> NO Garnichtwahr 7.54 has one great feature everyone always looks for. The release is brandnew and 7.53 is already 3 weeks old! Value: We can't miss that great feature Risk: 7.55 will appear in another 3 weeks and make the feature actually work for everyone but the author -> Most likely NO, depends on how many bugs 7.54 fixes. We want bug fixes! alsa-tools 1.0.21 is a new upstream version that includes all our patches Value: we correctly mark which upstream version we have Risk: potentially breaking things that rely on "1.0.20" and we might break something unforseen -> Yes yast2-theme 2.18.6 adds new icons and increases the version because we always did for yast -> Yes lyx 1.6.4 fixes stability problems and crashes with later Qt versions Value: many bugs fixed upstream, pure maintenance release for 1.6.x Risk: lyx might see little testing during the beta phase, so switching versions during beta phase may half the actual testing -> Yes, because the emphasise on this release is clearly bug fixing So please file a bug, assign it to me and note the bug report number in the .changes file and/or the submit request. Oh, one exception from the rule: I said repeatedly that I will accept feature versions from teams without bugs. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0