openSUSE Packaging March 2012

packaging@lists.opensuse.org

55 participants
40 discussions

[opensuse-packaging] What does 'RPATH "" ... is not allowed' mean?

by Christian Boltz

Hello, I got a build failure in security:apparmor:factory / apparmor today, but only for the factory build. The package itsself didn't change, so it must be caused by a recent change in factory. Can someone please explain me what the following lines in the build log mean and how I can fix the issue? calling /usr/lib/rpm/brp-suse.d/brp-35-rpath ERROR: RPATH "" on /home/abuild/rpmbuild/BUILDROOT/apparmor-2.7.2-126.20.i386/usr/lib/perl5/vendor_perl/5.14.2/i586-linux-thread-multi/auto/LibAppArmor/LibAppArmor.so is not allowed ERROR: RPATH "" on /home/abuild/rpmbuild/BUILDROOT/apparmor-2.7.2-126.20.i386/usr/lib/perl5/vendor_perl/5.14.2/i586-linux-thread-multi/auto/LibAppArmor/LibAppArmor.so is not allowed If you need the full build log: https://build.opensuse.org/package/live_build_log?arch=i586&package=apparmo… Regards, Christian Boltz -- > Manfred, Du solltest so spaet keine Emails mehr schreiben :-) Danke für die Berichtigung, werd mir den Tipp hinter die Ohren schreiben und nur noch Mailen, wenn ich die Augen zumindestens zu einem drittel aufkriege. [> Thomas Hertweck und Manfred Tremmel in suse-linux] -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

10 years, 3 months

Re: [opensuse-packaging] Need clarification on the new shared library packaging policy.

by Dave Plater

On 03/11/2012 05:46 PM, Nelson Marques wrote: > libconfig++9 > > That is most likely what you are looking for. Either way rpmlint does > provide you the correct name in the output (used to at least). Rpmlint does, I created the other new package, dbus-c++, needed to fix two ffado bugs this weekend and it was easier to accept the rpmlint given names than to work it out for myself. The reason I asked was libconfig was declined from factory for this reason but I suspect it was a demo of what the reopen button is for. I've been away for a while and a few build service features are new to me. Thanks Dave -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

10 years, 3 months

[opensuse-packaging] New maintenance work-flow for openSUSE on Thursday (15th March)

by Adrian Schröter

In the name of Maintenance, Security and OBS team: After long time designing and development of the new build system maintenance model, we (Security, Maintenance and OBS team) will do the switch on Thursday, 15th March What does this mean for plain openSUSE users? ============================================= - No actions required. The same repos will provide at the same place the same content. - patch naming will change from "packagename-<globalversion>" to "openSUSE-year-number" What does this mean for openSUSE developers? ============================================ Short version: - OBS and Bugzilla are the only tools for coordinating openSUSE updates. SUSE internal SWAMP is no longer used for openSUSE. - osc 0.134 is required. => A maintenance update will provide it. - With osc 0.134 "osc submitrequest" against update projects will actually not create submit requests anymore. Instead maintenance requests are used now. osc automatically detects that but you can also create maintenance requests manually using "osc maintenancerequest". - openSUSE:X.y:Update:Test is no longer used for package submissions. Submit against *:Update or use "osc maintenancerequest" instead - Running updates with open bugs assigned to the packager appear in patchinfos on the "my work" page. And on CLI: => osc my [work] - Every update _must_ have at _least_ one bnc# reference in the changelog which explains why an update is needed. If the change needs more explanation, the description from the maintenance request is used for the customer readable patch description. If anything is unclear, ask via bugzilla by NEEDINFO'ing maintenance(a)opensuse.org. Other comments, or CC'ed comments to individual persons will not be handled. - If you plan to stage changes to packages, it is heavily recommended to create a devel project for your 11.4 and 12.1 updates and set it in the buildservice via the "osc changedevelrequest" command. This ensures, similiar to how it works for openSUSE Factory, that you can collaborate on updates and test your changes prior submission for update. Different scenarios and workflow examples can be found in the OBS reference maintenance chapter: http://doc.opensuse.org/products/draft/OBS/obs-reference-guide_draft/cha.ob… Boring background details: - Updates get prepared in subprojects of openSUSE:Maintenance ("Incident Projects") and released from there. - Updates are now built against :Update instead of :Update:Test. Therefore not yet released updates don't influence each other anymore. That also means that updates that depend on each other need to be put into a common incident project. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

10 years, 3 months

[opensuse-packaging] perl-dependencies not autodetected?

by Stefan Seyfried

Hi all, https://bugzilla.novell.com/show_bug.cgi?id=738549 "vdradmin needs perl-libwww-perl" My question is: why does this not get autodetected by the buildservice? Or am I doing something wrong in the packaging? Package in question is obs://vdr/vdradmin Thanks for any insight -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

10 years, 3 months

[opensuse-packaging] Need clarification on the new shared library packaging policy.

by Dave Plater

I'm confused about how to name the shared library rpms in a new package destined for factory multimedia:libs libconfig. I thought I'd used the correct name for the two shared library packages : libconfig9 and libconfig++9. The libraries in the x86_64 libconfig++9 package are : /usr/lib64/libconfig++.so.9 /usr/lib64/libconfig++.so.9.1.2 and this is the internal soname # objdump -C -p /usr/lib64/libconfig++.so.9.1.2 |grep SONAME SONAME libconfig++.so.9 and in the past rpmlint would throw an error if this package was named anything else but reading the shared library policy there's an option for the full "current.age.revision" to be included in the name ie. libconfig++9_1_2 but surely this would cause an rpmlint error in this case? Thanks Dave -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

10 years, 3 months

[opensuse-packaging] 200 lines of changes?

by Greg Freemyer

All, I just updated perl-Image-Exiftool in my home project. I dumped all the changes from the change log into our *.changes file, but its 200 lines of info for just the last 6 months. Should I leave it that way, or replace it with a URL? https://build.opensuse.org/package/view_file?file=perl-Image-ExifTool.chang… Thanks Greg -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

10 years, 3 months

[opensuse-packaging]

by Marguerite Su

Hi, all, (I don't know if it's right to post it here, but I think it must be someone among us who wrote the wiki page) I'm translating specfile_guide wiki to Chinese. But I can't understand the following: "If the spec file contains conditional dependencies selected based on presence of optional --with(out) foo arguments to rpmbuild, build the source RPM to be submitted with the default options, ie. so that none of these arguments are present in the rpmbuild command line. The reason is that those requirements get "serialized" into the resulting source RPM, ie. the conditionals no longer apply." it seems initial writer copied it from Fedora. can anyone help me understanding this? #1 I know what conditional dependencies are. #2 “build the source RPM to be submitted" why build before submission? if builds locally, why submit the SRPM instead of the whole project? #3 "are presented in the rpmbuild command line" where the rpmbuild command line is? I never see them on OBS, although I know I can "rpm -ba *.spec --with condition 1 --without condition 2" #4 I can't understand the sentence from "the reason" to the end. Can anyone give me some hints? or a plain English example? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

10 years, 3 months

[opensuse-packaging] changed config location

by Lutz Thuns

Hi, I'm currently packaging wbar in my home-project. Recently upstream has changed the default config directory from /etc/default/wbar to /etc/wbar.d/ Now I want to make sure that any existing (changed) configuration in /etc/default/wbar will be kept in /etc/wbar.d Otherwise there would be both an old config dir (with possibly changed .conf files) and a new config dir (with "stock" configuration). I think I have to do this via a script in %pre. Any ideas how to exactly do this? -- Lutz Thuns openSUSE member (lOtz1009) LXDE team -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

10 years, 3 months

[opensuse-packaging] GCC regression - any hints on what should I do?

by Ilya Chernykh

Hi! There is apparent GCC regression so that a package which works well when built with GCC-4.3 crashes if it is built with GCC-4.5 and GCC-4.6. Is there an established procedure of handling this? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

10 years, 3 months

[opensuse-packaging] how do I fix "/usr/local/bin/python" is not allowed as Requires. Generated from running 05-check-invalid-requires.

by doiggl＠velocitynet.com.au

Hello How do I fix this message [1] in a opensuse 12.1 build ? A 11.4 version built ok Spec file is at [2] Thanks Glenn [1] https://build.opensuse.org/package/live_build_log?arch=x86_64&package=bugzi… ... running 05-check-invalid-requires "/usr/local/bin/python" is not allowed as Requires. [ 64.547377] SysRq : Power Off [ 66.563653] Power down. [2] spec file https://build.opensuse.org/package/view_file?file=bugzilla.spec&package=bug… -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

10 years, 3 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

openSUSE Packaging March 2012