January 2012 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] factory-auto rejects invalid licenses now
by Stephan Kulow 24 Jan '12

24 Jan '12

Hi, Please note that invalid-license is a warning to rpmlint only, so the build succeeds both in factory and the devel projects, but factory-auto will check the rpmlint.log and reject submits with invalid licenses. rpmlint checks that the licenses are in spdx.org format and that the licenses are from the list linked at license.opensuse.org. If you use obs-service-format_spec_file from openSUSE:Tools (0.4.1 currently), then osc will autoconvert the license for you. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0

[opensuse-packaging] horde3-* End of Life in April 2012
by Ralf Lang 20 Jan '12

20 Jan '12

Hi crowd, I'll retire horde3-* from factory if there is no opposition to that. * Horde 4 has already shipped with 12.1 alongside with Horde 3. * In April, Horde 4.1 will ship and Horde 3 will see end of life. No more patches apart from announced security updates. * By the time OpenSUSE 12.2 ships, most Horde 3 apps will have been ported to Horde 4. * As a part of the upstream team I will take care of the existing Horde 3 packages in released openSUSE versions for their remaining lifetime. * I will not delete the packages from server:php:applications for quite a while. * Kolab support in Horde 4 has improved and the heavily patched Horde 3 packages are not important anymore. -- Ralf Lang -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0

[opensuse-packaging] RFC: Cleanup of packages - checking doc files
by Andreas Jaeger 20 Jan '12

20 Jan '12

I just filed feature #313152 - to have a smaller base system which is beneficial for appliances. Looking at a basic installation (default text server install), I noticed that we have in /usr/share/doc/packages besides the license (which we need to keep) also other files. An example is glib2, it installs to /usr/share/doc/packages/libglib-2_0-0: -rw-r--r-- 1 root root 1344 Aug 16 02:51 AUTHORS -rw-r--r-- 1 root root 1895792 Oct 14 15:51 ChangeLog -rw-r--r-- 1 root root 25292 Aug 16 02:51 COPYING -rw-r--r-- 1 root root 197710 Oct 14 15:30 NEWS -rw-r--r-- 1 root root 9906 Oct 14 15:51 README I suggest to move everything to the devel package (or a doc package if it exists). On IRC, Vincent and Sascha suggested to keep README, NEWS (and maybe AUTHORS) in the base package and move only ChangeLog to the devel package. Another idea was to compress these files. My personal opinion is that the vast majority of our users does not need any of these. Those developers that need it, will get it from the devel/doc packages. What do you think? Any other ideas on getting a smaller base system? Note: I don't want to make this a hard rule, more a recommendation. Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

14 20

[opensuse-packaging] Setting environmental variables
by Robert Munteanu 20 Jan '12

20 Jan '12

Hi, I have a package (maven) which relies on the presence of a environment variable (MAVEN_HOME) . I have created /etc/profile.d/maven.{csh,sh} but these only work after the user logs out. How can I make the environment variable available immediately after the package is installed? Thanks, Robert -- Sent from my (old) computer -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 2

[opensuse-packaging] python-2.5 porting: ssizecheck.py
by Martin Vidner 20 Jan '12

20 Jan '12

Hi, Python packagers, yes, 2.5 :) When building a C extension for Python, I see: + /usr/lib/rpm/brp-check-python /usr/src/packages/BUILD/netifaces-0.5/netifaces.c:340: 'PyList_New' uses Py_ssize_t for input parameters [and several repetitions of it] but inspecting the build tool shows that it simply complains WHENEVER it seems PyList_New and other basic functions. Once I figure out the matter of the API change (http://www.python.org/dev/peps/pep-0353 ), how am I supposed to mark the package as OK? True, this only happens when building for SLE11, not on Factory. Should I just shrug it off? -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu

2 1

[opensuse-packaging] OBS tries to build previous version of uploaded specfile and blocks packages
by Ralf Lang 20 Jan '12

20 Jan '12

Hi, i've had something similar last year and I think Sascha manually fixed it somehow. Now it's back: The OBS tries to build outdated versions of the specfile of the following packages: https://build.opensuse.org/package/live_build_log?arch=i586&package=horde4-… https://build.opensuse.org/package/live_build_log?arch=i586&package=php5-pe… https://build.opensuse.org/package/live_build_log?arch=i586&package=php5-pe… I have tried wipe-binaries and trigger-rebuild but it always returns to the old specfile versions and dies because the old tgz files are missing now. Is there anything I can do about this? In files view, it shows the correct current versions of the uploaded files. -- Ralf Lang Linux Consultant / Developer Tel.: +49-170-6381563 Mail: lang(a)b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 3

[opensuse-packaging] how can 'Kernel release mismatch' be fixed ?
by doiggl＠velocitynet.com.au 20 Jan '12

20 Jan '12

Hello, How do I fix this error see[1] Thanks Glenn [1] make: Leaving directory `/home/abuild/rpmbuild/BUILD/kernel-vanilla-3.0.13/linux-3.0' ++ make -s kernelrelease -C /home/abuild/rpmbuild/BUILD/kernel-vanilla-3.0.13/linux-3.0 O=/home/abuild/rpmbuild/BUILD/kernel-vanilla-3.0.13/linux-obj + krel=3.0.17-24-vanilla + '[' 3.0.17-24-vanilla '!=' 3.0.13-24-vanilla ']' + echo 'Kernel release mismatch: 3.0.17-24-vanilla != 3.0.13-24-vanilla' Kernel release mismatch: 3.0.17-24-vanilla != 3.0.13-24-vanilla + exit 1 error: Bad exit status from /var/tmp/rpm-tmp.YnhCWX (%prep) Source https://build.opensuse.org/package/show?package=kernel-vanilla&project=home… -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0

[opensuse-packaging] I regularly experience conflicts in obs ci
by Ralf Lang 17 Jan '12

17 Jan '12

I experienced a lot of conflict states in *.spec when uploading updated packages to server:php:applications today and yesterday. It was around 1/3 of packages uploaded. It means some extra manual work each case. Any way to prevent this? -- Ralf Lang Linux Consultant / Developer Tel.: +49-170-6381563 Mail: lang(a)b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 1

[opensuse-packaging] broken suse_update_config macro
by Ruediger Meier 17 Jan '12

17 Jan '12

Hi, recently the suse_update_config macro got deprecated and rewritten, see https://build.opensuse.org/request/show/99371 But the new implementation makes IMO absolutely no sense because in past it respected argument [dirs...]. So currently autoreconf is called within random directories but not where it should! Hopfully the packager will notice that... I'd rather remove that autoreconf call by "false" and turn the warnings into errors. cu, Rudi -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0

[opensuse-packaging] How to create a dependency
by Mathias Homann 17 Jan '12

17 Jan '12

Hi, I'm banging my head against the wall here... how do i create a "alternate" dependency in a spec file? I need to create a i586 rpm that has a requirement to libgstapp but only the 32bit version. or, in pseudoboolean: Requires: libgstapp-0_10-0-32bit(x86-32) || libgstapp-0_10-0(x86-32) how do i do that... I can't point the Requires: line at absolute files, e.g. /usr/lib/libgstapp-0.10.so.0 because that would "force" the right package/architecture but doesn't get resolved by zypper 0.o bye, MH -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 9