January 2011 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] shlib policy and letters in version
by Jan Matejek 18 Jan '11

18 Jan '11

hello, in packaging Python 3.2, i've run into a strange situation regarding the shlib naming policy. Python's shared library is now called "libpython3.2m.so.1.0", "3.2" being python series and "m" a so-called ABI tag. This was part of an upstream attempt to provide a stable ABI for python modules, so we might be stuck with "libpython3.2m" for the next few years. Without the "m", the right name for the library package would be "libpython3_2-1_0". It seems logical that with it, library package would be named "libpython3_2m-1_0". However, the relevant rpmlint check insists the library be called "libpython3_2m1_0". Is this a bug in the rpmlint check, or is there some part of the policy saying that this is how the package should be called? thanks m. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 2

[opensuse-packaging] What do I do with a package that contains only development files?
by Dave Plater 17 Jan '11

17 Jan '11

Hi, I've created a package home:plater/lv2core which contains doxygen docs, only one binary lv2config, lv2.h, lv2.ttl, manifest.ttl and lv2core.pc. I'm not really sure what the ttl files are for but the package is necessary for new package slv2 to build and that is it's only purpose. IMHO everything should be in one package but rpmlint doesn't like such things so I've put everything except lv2config in the main package and the rest in the devel package. I also get an rpmlint warning stating that the main package should be noarch, lv2config is a python script. Am I doing the right thing? Thanks Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

4 6

Re: [opensuse-packaging] rpmlint-checks: adding new gnome/desktop-related checks
by Michael Schroeder 17 Jan '11

17 Jan '11

On Mon, Jan 17, 2011 at 10:39:03AM +0100, Michael Andres wrote: > On Sunday 16 January 2011 19:44:50 Cristian Morales Vega wrote: > > FWIW, if instead of calling gtk-update-icon-cache on each package > > installation you change the %icon_theme_cache_post(un) macros to use > > ZYpp's update-scripts > > (http://lists.opensuse.org/zypp-devel/2010-06/msg00005.html) you have > > my vote to add those checks today. That should solve any problem with > > the installer. > > > > Michael, are update-scripts still the best way to run something that > > needs to be done for a lot of packages and it is enough if it's run > > once after all packages have been installed > > On libzypp level, yes. > http://old-en.opensuse.org/Software_management/Code11/Scripts_and_Messages > > > Or there is something new in the RPM version from 11.4 > > ("Collections", .... > > We should ask Michael <mls(a)suse.de> about the "Collections". He knows best > about the rpm version available on 11.4. 11.4 is going to ship with rpm-4.8.0, like 11.3 (rpm-4.9 is not yet released.) AFAIK 4.8.x doesn't support Collections, that's a 4.9.x feature. Cheers, Michael. -- Michael Schroeder mls(a)suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 2

[opensuse-packaging] Need help on a Evergreen kernel module
by Greg Freemyer 17 Jan '11

17 Jan '11

All, The evergreen project is evaluating using the 2.6.32 kernel instead of the 2.6.27 kernel that is currently in 11.1. I built a test repo in my home project with the 2.6.32 kernel from SLES11 SP1. I'm having issues with virtualbox-ose packaging with the 2.6.32 test kernel. To be honest, my first thought is just grab virtualbox-ose from SLES11 SP1 since we know it has the kernel modules tweaked to work with this kernel. Otherwise: Packaging / OBS experts, I branched virtualbox-ose from the new DISCONTINUED:openSUSE_11.1:Update repo to my home evergreen test repo which uses the same repo as its primary build repo (see home:gregfreemyer:Evergreen-11.1). The build log is here https://build.opensuse.org/package/live_build_log?arch=x86_64&package=virtu… But the build is failing with a couple of different errors: First several like: === /usr/bin/g++-4.1 '-Wl,-rpath,/usr/lib/virtualbox' '-Wl,-rpath,/usr/lib/virtualbox' -Wl,-z,noexecstack -Wl,--as-needed -m32 -o /usr/src/packages/BUILD/VirtualBox-2.0.6/out/linux.x86/release/obj/tstInit/tstInit /usr/src/packages/BUILD/VirtualBox-2.0.6/out/linux.x86/release/obj/tstInit/tstInit.o /usr/src/packages/BUILD/VirtualBox-2.0.6/out/linux.x86/release/bin/VBoxRT.so -lpthread -lm -lrt -ldl /usr/lib/gcc/i586-suse-linux/4.1.3/../../../../i586-suse-linux/bin/ld: error in /usr/lib/gcc/i586-suse-linux/4.1.3/crtend.o(.eh_frame); no .eh_frame_hdr table will be created. === see the error towards the end Then it ends with: === kmk_builtin_install -m 0755 -- /usr/src/packages/BUILD/VirtualBox-2.0.6/out/linux.x86/release/obj/tstGetPagingMode/tstGetPagingMode /usr/src/packages/BUILD/VirtualBox-2.0.6/out/linux.x86/release/bin/testcase/tstGetPagingMode /usr/src/packages/BUILD/VirtualBox-2.0.6/src/VBox/HostDrivers/Support/linux/SUPDrv-linux.c: In function 'VBoxDrvLinuxCreate': /usr/src/packages/BUILD/VirtualBox-2.0.6/src/VBox/HostDrivers/Support/linux/SUPDrv-linux.c:650: error: 'struct task_struct' has no member named 'euid' /usr/src/packages/BUILD/VirtualBox-2.0.6/src/VBox/HostDrivers/Support/linux/SUPDrv-linux.c:663: error: 'struct task_struct' has no member named 'uid' /usr/src/packages/BUILD/VirtualBox-2.0.6/src/VBox/HostDrivers/Support/linux/SUPDrv-linux.c:664: error: 'struct task_struct' has no member named 'gid' kmk[3]: *** [/usr/src/packages/BUILD/VirtualBox-2.0.6/out/linux.x86/release/obj/vboxdrv/linux/SUPDrv-linux.o] Error 1 kmk[3]: *** Waiting for unfinished jobs.... kmk[3]: Leaving directory `/usr/src/packages/BUILD/VirtualBox-2.0.6/src/VBox/HostDrivers' kmk[2]: *** [pass_binaries_before] Error 2 kmk[2]: Leaving directory `/usr/src/packages/BUILD/VirtualBox-2.0.6/src/VBox' kmk[1]: *** [pass_binaries_before] Error 2 kmk[1]: Leaving directory `/usr/src/packages/BUILD/VirtualBox-2.0.6/src' kmk: *** [pass_binaries_before] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.50343 (%build) RPM build errors: cannot open Pubkeys index using db3 - No such file or directory (2) Bad exit status from /var/tmp/rpm-tmp.50343 (%build) [ 574.400456] System halted. Script_lightning === If anyone has any advice, I'd appreciate it. Otherwise I will likely try virtualbox-ose from SLES11 SP1 this weekend. Thanks Greg -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 2

Re: [opensuse-packaging] Check for KDE SC version inside SPEC files
by Tejas Guruswamy 15 Jan '11

15 Jan '11

On 15/01/11 13:15, Matthias Fehring wrote: > Am Freitag, 14. Januar 2011, 19:18:32 schrieb Tejas Guruswamy: > >> The original macro failed just because the output from kde4-config >> changed format slightly with the KDE rebranding. >> >> I've been using this one in my spec files for a while >> >> %define kde4_version %(/usr/bin/kde4-config --version | sed >> -r '/KDE.*:/! { d }; { s/KDE.*: (([0-9]+)\\.([0-9]+)\\.([0-9]+)) >> .*/\\2\\3\\4/g }') >> >> Works on all KDE versions I've seen. >> >> Regards, >> Tejas >> > When I try this in terminal I get the following: > > KDE: 4.9.95 (4.6 RC2) > > I would expect something like > > 4995 > > I am only a novice in sed... ;-) > > Best Greetings > Matthias > The macro I gave has extra escapes to work inside the spec file. To test it in the terminal use only one backslash ('\' instead of '\\') everywhere. And make sure it's all on one line. Regards, Tejas -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 1

[opensuse-packaging] Check for KDE SC version inside SPEC files
by Matthias Fehring 15 Jan '11

15 Jan '11

Hello list, I am searching for a way to determine the KDE SC version of the build system inside a SPEC file. In the past I used this way: http://bit.ly/eABmJb But this does not work anymore in recent openSUSE releases or with recent versions of KDE SC - I do not know the real reason. Is there a better way to check for the used version? Good would be a macro like suse_version, that can be used in conditionals. Best regards Buschmann

4 8

[opensuse-packaging] The link contains errors: conflict in file series.conf
by doiggl＠velocitynet.com.au 14 Jan '11

14 Jan '11

Hello, I get this error message "The link contains errors: conflict in file series.conf" in package [1] My series.conf only has these lines in it. ######################################################## #Reiser4fs Patches - Add to series.conf ######################################################## patches.rpmify/reiser4-for-2.6.36.patch patches.rpmify/reiser4-fix-entd_flush.patch [1] https://build.opensuse.org/package/files?expand=0&package=kernel-reiser4&pr… How can this error be fixed ? Thanks Glenn -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 1

[opensuse-packaging] python-cdecimal packages available
by Hans-Peter Jansen 13 Jan '11

13 Jan '11

Hi, there's a python-cdecimal package available in d:l:p for those of you, that have huge amounts of python decimal data to process. It's a drop-in replacement for Decimal, that uses an asm optimized c-lib for processing, hence that's not a bottleneck anymore.. Have fun, Pete -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 3

[opensuse-packaging] evergreen updates
by Wolfgang Rosenauer 13 Jan '11

13 Jan '11

Hi, this is targetted to openSUSE community packagers (or those being both openSUSE/Novell ;-)) If you prepare (mainly security) updates for 11.2/11.3 and you feel like it, please prepare one for 11.1 as well and submit it to openSUSE:Evergreen:11.1:Test. You can obviously decide yourself if you want to contribute or not but it would be nice if you would. Thanks, Wolfgang -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 3

[opensuse-packaging] Package does not build for >11.2
by Ilya Chernykh 13 Jan '11

13 Jan '11

Hi! Can anybody tell me why this package does not build for > 11.2? https://build.opensuse.org/package/show?package=kcall&project=home%3AAnsus%… The linker says it cannot find some files... -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0