[Bug 487400] New: "osc build --local-package --alternative-project" builds debug packages by default

https://bugzilla.novell.com/show_bug.cgi?id=487400 Summary: "osc build --local-package --alternative-project" builds debug packages by default Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: BuildService AssignedTo: adrian@novell.com ReportedBy: bitdealer@gmail.com QAContact: adrian@novell.com CC: mrueckert@novell.com, suse-tux@gmx.de Found By: --- "osc build --local-package --alternative-project" builds debug packages by default although "-d" isn't used. Besides that contradicting the documentation it also makes it impossible to build Mandriva 2009 packages locally since that one builds the debug packages by default and therefore it fails with error: Package already exists: %package debug -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=487400 User bitdealer@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=487400#c1 --- Comment #1 from Stephan Kleine <bitdealer@gmail.com> 2009-03-20 13:35:27 MST --- How to reproduce: E.g for openvas-libnasl in security:openvas:UNSTABLE: 1. "osc co security:openvas:UNSTABLE openvas-libnasl" 2. "cd security\:openvas\:UNSTABLE/openvas-libnasl" 3. "osc build --local-package --alternative-project=security:openvas:UNSTABLE openSUSE_11.1 i586 libopenvasnasl.spec" creates libopenvasnasl-debugsource-2.0.1-1.0.i586.rpm & libopenvasnasl-debuginfo-2.0.1-1.0.i586.rpm although "-d" isn't used and 4. "osc build --local-package --alternative-project=security:openvas:UNSTABLE Mandriva_2009 i586 libopenvasnasl.spec --clean" fails with "error: Package already exists: %package debug" because Mandriva 2009 always creates debug packages. As you can see in neither of those calls "-d" was used and therefore it should not build any debug packages which it currently does (or tries to in Mandrivas case). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=487400 User suse-tux@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=487400#c2 --- Comment #2 from Marcus Hüwe <suse-tux@gmx.de> 2009-03-22 10:18:06 MST --- (In reply to comment #1)
4. "osc build --local-package --alternative-project=security:openvas:UNSTABLE Mandriva_2009 i586 libopenvasnasl.spec --clean"
fails with "error: Package already exists: %package debug" because Mandriva 2009 always creates debug packages.
As you can see in neither of those calls "-d" was used and therefore it should not build any debug packages which it currently does (or tries to in Mandrivas case).
The problem is that the debuginfo generation is enabled project wide. If you pass --local-package or --alternative-project to "osc build" the package wide settings are ignored. So this behaviour is expected:) You can workaround it if you add <debuginfo> <disable repository='Mandriva_2009'/> </debuginfo> to the project's metadata. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=487400 User bitdealer@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=487400#c3 --- Comment #3 from Stephan Kleine <bitdealer@gmail.com> 2009-03-22 15:02:41 MST --- It doesn't respect project wide settings either. E.g. debuginfo is disabled in security:openvas:STABLE for Mandriva 2009 but "osc build --local-package --alternative-project=security:openvas:STABLE Mandriva_2009 i586 libopenvasnasl.spec" still fails with "error: Package already exists: %package debug". Also I don't see a reason for ignoring package wide settings but respecting project wide settings. IMHO it shouldn't respect any build debuginfo settings but simply default to not to build any debuginfo packages until one uses "-b" to signal one wants some. The reasoning simply is that otherwise it would be impossible to override server side settings locally (which e.g. makes it impossible to build packages for Mandriva 2009 locally if debuginfo is enabled on the server side) while my solution would allow one to locally do what one prefers. Or, in other words, it should not be impossible to override server side settings for local builds. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=487400 User suse-tux@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=487400#c4 --- Comment #4 from Marcus Hüwe <suse-tux@gmx.de> 2009-03-24 12:22:10 MST --- (In reply to comment #3)
It doesn't respect project wide settings either.
I just committed to small fixes for this (see r6911 and r6914).
Also I don't see a reason for ignoring package wide settings but respecting project wide settings. IMHO it shouldn't respect any build debuginfo settings but simply default to not to build any debuginfo packages until one uses "-b" to signal one wants some.
The package is only ignored if you use --local-package or --alternative-project because in both cases your package doesn't exist in the specified project (or at least the intention of the options is that it doesn't exist). IMHO it makes sense to respect the project/package wide settings for the debuginfo generation. What we can do is the following: osc build --debug ... simply inverts the value which is stored in the buildinfo. For example: * debuginfo generation is enabled => it will be disabled * debuginfo generation is disabled => it will be enabled But this might also lead to confusion. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=487400 User bitdealer@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=487400#c5 --- Comment #5 from Stephan Kleine <bitdealer@gmail.com> 2009-03-24 14:29:46 MST ---
I just committed to small fixes for this (see r6911 and r6914).
Thanks a lot for looking into it so fast!
IMHO it makes sense to respect the project/package wide settings for the debuginfo generation. What we can do is the following: osc build --debug ... simply inverts the value which is stored in the buildinfo.
I don't really care as long as I'm able to override the server side settings. However, IMHO, it's really much easier to understand "use -d to generate debug packages" than "use -d to invert the current server side setting for debug packages" ;D Last but not least your solution would force me to look at the server side setting to find out if I need -d or not while, with mine, I would know it in the first place so it also would be a bit simpler to use. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=487400 User suse-tux@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=487400#c6 --- Comment #6 from Marcus Hüwe <suse-tux@gmx.de> 2009-03-31 05:48:19 MDT --- I just committed a fix for it (r6967). If --debuginfo is specified build will create debuginfo packages. If --disable-debuginfo is specified build will not create debuginfo packages. Both switches override the server side settings. If neither --debuginfo nor --disable-debuginfo is specified build will use the server side settings. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com