openSUSE Packaging April 2010

packaging@lists.opensuse.org

53 participants
51 discussions

[opensuse-packaging] Right usage of libexecdir?
by Vincent Untz 25 May '11

25 May '11

Hey, Dominique and I are currently wondering what to do wrt libexecdir for evolution-data-server. Should we leave it unchanged (so files will be in /usr/lib) or should we change it to /usr/lib/evolution-data-server? If the latter, is there any reason this is not done automatically? Also, hrm, would rpmlint have ways to warn about packages that put binaries in libdir instead of libexecdir? (I can find a few of them here with a grep) Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

6 9

[opensuse-packaging] Factory freeze
by Stephan Kulow 12 May '10

12 May '10

Hi, There seems to be some information missing about the state of Factory. With Milestone6 (the original deadline - last monday) all packages are version and feature frozen. This means: do not push new features / new versions / new packages towards Factory just because they are there. If you find that 11.3 will seriously lack something when not updating, then tell me personally or a list about it and give pros and cons. And let me get the biggest con straight: what we have in now has 2 months of testing, what we get later gets less testing. What you do in devel projects, is of course your concern - and pushing things there to test is of course a valid approach to convince me. Of course we exceeded the point where "succeeded" marks the end of testing. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 4

[opensuse-packaging] package rename
by Michal Seben 03 May '10

03 May '10

two weeks ago I ask here on packaging mailing list how to deal with package rename, (without response) so after some investigating and talk with my colleagues I setup wiki which could be useful for others http://en.opensuse.org/Cron_rename -- 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] openSUSE 11.1 KMPs and CODE11
by Tejas Guruswamy 30 Apr '10

30 Apr '10

Hello all, I was investigating the build failures of VirtualBox for openSUSE 11.1 ... The package builds two KMPs, and so uses a custom filelist i.e. %defattr (-,root,root) dir /lib/modules/%2-%1/ %dir /lib/modules/%2-%1/updates /lib/modules/%2-%1/updates/vboxdrv.ko /lib/modules/%2-%1/updates/vboxnetadp.ko /lib/modules/%2-%1/updates/vboxnetflt.ko But on openSUSE 11.1 we are getting failures like > File not found: /var/tmp/virtualbox-ose-3.1.6-build/lib/modules/2.6.27.7-9-debug-debug (it builds fine on openSUSE 11.2) so "%2" is expanding to "version-flavour" rather than just "version" like CODE11 says it should (and like how it behaves on 11.2). This means openSUSE 11.1 is behaving according (at least for this macro) to CODE10 rather than CODE11. Is this expected? I thought openSUSE 11.1 followed CODE11, and this is what the documentation [1] states ... As a side note, this issue is not mentioned in the "CODE10->CODE11 changes" section of the CODE11 documentation. Regards, Tejas [1] http://developer.novell.com/wiki/index.php/Kernel_Module_Packages_Manuals -- 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] LLVM (for Mono) in 11.3?
by Andrew Jorgensen 30 Apr '10

30 Apr '10

Hello, The Mono team would like to have LLVM available in 11.3. We will be using LLVM in upcoming versions of mono and having it in 11.3 would make development easier for us and our many outside contributors. I am told that Duncan (dmacvicar) has packages of LLVM 2.6 ready and they just need to be imported to Factory. Unfortunately he's on leave until July (or October depending on which standard he was using when he wrote 10.07.2010). Can I get someone on the SUSE side of the pond to take ownership of this? I'm willing to take part in basic package maintenance. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

4 4

[opensuse-packaging] rpmlint crash
by Andrew Jorgensen 29 Apr '10

29 Apr '10

Assuming it hasn't rebuilt and succeeded the error can be seen here: https://build.opensuse.org/package/live_build_log?arch=i586&package=mono-co… Relevant bit is this: raceback (most recent call last): File "rpmlint.py", line 352, in <module> File "rpmlint.py", line 158, in main File "rpmlint.py", line 218, in runChecks File "FilesCheck.py", line 1318, in check AttributeError: 'NoneType' object has no attribute 'startswith' Everything else seems okay. Fix? -- 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] XEN/kvm for "osc build"
by Stefan Seyfried 29 Apr '10

29 Apr '10

Hi, Is there some documentation for configuring osc to use kvm for building? I tried yesterday, but was not successful. The only doc I could find was the sermon that was written into the .oscrc of a new user, and it was not too helpful. This is what's in my .oscrc: seife@susi:~/buildservice/testing/bluez> egrep -v '^(#|$)' ~/.oscrc [general] apiurl = https://api.opensuse.org packagecachedir = /local/osbuild-packagecache su-wrapper = sudo build-root = /local/abuild/osc/%(repo)s build-type = kvm build-device = /local/abuild/kvm/root.img build-swap = /local/abuild/kvm/swap.img build-memory = 512 [https://api.opensuse.org] user=seife email = seife(a)opensuse.org That's the result: seife@susi:~/buildservice/testing/bluez> osc build bluez.spec Building bluez.spec for openSUSE_Factory/x86_64 Getting buildinfo from server and store to /local/buildservice/home:seife/home:seife:testing/bluez/.osc/_buildinfo-openSUSE_Factory-x86_64.xml Getting buildconfig from server and store to /local/buildservice/home:seife/home:seife:testing/bluez/.osc/_buildconfig-openSUSE_Factory-x86_64 Updating cache of required packages 0.0% cache miss. 132/132 dependencies cached. Skipping verification of package signatures due to secure VM build Writing build configuration Running build sudo "/usr/bin/build" --root="/local/abuild/osc/openSUSE_Factory/.mount" --rpmlist="/tmp/rpmlist.d_Ekq9" --dist="/local/buildservice/home:seife/home:seife:testing/bluez/.osc/_buildconfig-openSUSE_Factory-x86_64" --arch=x86_64 --kvm /local/abuild/kvm/root.img --swap /local/abuild/kvm/swap.img --memory 512 --norootforbuild --changelog --jobs 2 --debug "/local/buildservice/home:seife/home:seife:testing/bluez/bluez.spec" mkswap /local/abuild/kvm/swap.img mkswap: /local/abuild/kvm/swap.img: warning: don't erase bootbits sectors on whole disk. Use -f to force. Setting up swapspace version 1, size = 524284 KiB no label, UUID=38b9f02d-81a6-4716-b692-8d6cf6487daa BUILD_ROOT=/local/abuild/osc/openSUSE_Factory/.mount must be owned by root. Exit... The buildroot was: /local/abuild/osc/openSUSE_Factory/.mount of course, the error is wrong: seife@susi:~/buildservice/testing/bluez> ls -ld /local/abuild/osc/openSUSE_Factory/.mount drwxr-xr-x 2 root root 6 28. Apr 13:25 /local/abuild/osc/openSUSE_Factory/.mount but I did add debug output to the build script and indeed, at the moment the test is performed, that directory belongs to me... :-( Bug? Feature? Has anybody ever used this successfully? -- Stefan Seyfried "Any ideas, John?" "Well, surrounding them's out." -- 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] Shared Libraries and plugins
by Cristian Morales Vega 28 Apr '10

28 Apr '10

I have a package that started failing for Factory with: liballeg4_4-dga2-plugin.x86_64: E: shlib-fixed-dependency (Badness: 440) liballeg4_4 = 4.4.1.1 liballeg4_4-jack-plugin.x86_64: E: shlib-fixed-dependency (Badness: 440) liballeg4_4 = 4.4.1.1 liballeg4_4-oss-plugin.x86_64: E: shlib-fixed-dependency (Badness: 440) liballeg4_4 = 4.4.1.1 Your shared library package requires a fixed version of another package. The intention of the Shared Library Policy is to allow parallel installation of multiple versions of the same shared library, hard dependencies likely make that impossible. Please remove this dependency and instead move it to the runtime uses of your library. To be honest, I don't know the details of this one. But in general I expect plugins being able to use functions exported by the main library but not documented as public API, so they can change in any new minor version and I need to require the exact same version of the main library. Reading the explanation I am still not very sure about the objective of this check. Could someone give me one example where there would be a problem with parallel installation of multiple versions? So... - rpmlint needs to be fixed? - should plugin packages not be named libXXX? - should I just require liballeg4_4 >= 4.4.1.1? (not sure if rpmlint would complain anyway) -- 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] Recent rpmlint changes
by Stephan Kulow 28 Apr '10

28 Apr '10

Hi, We introduced some new rpmlint failures you'll see: 1. /var/run was supposed to be mounted tmpfs in 11.3 and if we manage to change all packages, it will be. So rpmlint now will give it a pretty bad score, so please change the packages not to put files in there, but use %ghosts or purely files generated by init scripts 2. rpm in combination with pkg-config will add requires to your package if it has a .pc file that requires other pkg-config files. For this all packages that have .pc files need to buildrequire pkg-config, or it will break on either side. The change is trivial to do, so anyone can fix the build failure as it pops up. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

4 4

[opensuse-packaging] Maintainership of checkbashisms
by Guido Berhoerster 27 Apr '10

27 Apr '10

Hello, could somebody with the appropriate privileges please add gberh to the maintainers and bugowners of checkbashisms in devel:tools? Thanks in advance, -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

openSUSE Packaging April 2010