On Friday 11 December 2009, 10:52:31 Marcus Meissner wrote:
On Fri, Dec 11, 2009 at 10:06:16AM +0100, Hans-Peter Jansen wrote:
Hi,
I stumbled across the %debug_package issue a few times now. Latest one:
+ exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --define 'jobs 4' --define 'disturl obs://build.opensuse.org/KDE:KDE3/openSUSE_11.1/f42dda8a858fcd5ab869234 8db18ba3d-kmymoney' --eval %suse_insert_debug_package /usr/src/packages/SOURCES/kmymoney.spec error: Package already exists: %package debuginfo
and while I do not understand the background, I guess, it's due to some projects adding %debug_package automagically, and build falls flat on its face, if the spec contains another %debug_package statement. Since adding it to local builds is highly desirable, it's a pain in the <beep> to being forced to remove that darn thing before checking in...
Maintaining KDE:KDE3 since a few days, I accepted a sr containing this bugger. Later I tried to check the diff again, but failed. Is it possible to see the --diff again _after_ a request was accepted?
You could diff revisions via osc diff -r...
The KDE:KDE3 repo has <debuginfo> <enable/> </debuginfo>, while the submitters branch project does not.
Remove the %debug_package from the .spec in KDE:KDE3 and tell the submitter to add <debuginfo> <enable/> </debuginfo> to his project metadata.
Thanks for this useful info. What I had in mind is a more intelligent behavior of rpmbuild in build service: before applying the project debug setting it might be a good idea to check if it's already there, doesn't it? IMHO, this issue deliberately break builds way to often. Cheers, Pete -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org