[Bug 543484] New: Scheduler ignores Obsoletes tag
http://bugzilla.novell.com/show_bug.cgi?id=543484 Summary: Scheduler ignores Obsoletes tag Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: BuildService AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: vuntz@novell.com QAContact: adrian@novell.com Found By: --- To fix a build failure, we renamed the libseed-0 package to libseed0 and the latter now provides/obsoletes the former. So for zypper, libseed0 will replace libseed-0. However, in the build service, we have some expansion errors: have choice for libseed.so.0 needed by seed: libseed-0 libseed0 (this is because libseed0 is in G:F and libseed-0 is in oS:F, I guess) The scheduler should probably consider the Obsoletes/Provides tag to make a choice there. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=543484 Marcus Meissner <meissner@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |mls@novell.com |ovo.novell.com | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=543484 User mls@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=543484#c1 Michael Schröder <mls@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Enhancement --- Comment #1 from Michael Schröder <mls@novell.com> 2009-10-02 02:24:25 MDT --- I not sure about this. We want consistent builds, so we treat every choice as error. To implement this we also would need to extract the obsoletes data from the packages, which we currently don't do. (Extracting conflicts would also be nice.) (Btw, a simple workaround is to add a "Prefer: libseed0" to your project configuration.) (Changed priority to "enhancement") -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=543484 User vuntz@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=543484#c2 --- Comment #2 from Vincent Untz <vuntz@novell.com> 2009-10-02 02:48:04 MDT --- (In reply to comment #1)
I not sure about this. We want consistent builds, so we treat every choice as error.
If you always handle Obsoletes, then the builds will be consistent :-)
(Btw, a simple workaround is to add a "Prefer: libseed0" to your project configuration.)
Yeah, I know the workaround, but I think it shouldn't be needed in this case. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=543484 User mls@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=543484#c3 --- Comment #3 from Michael Schröder <mls@novell.com> 2009-10-02 03:06:15 MDT --- Well, the main idea is that adding a package to a project can't influence the build of other packages of the same project. Thus you get a "have choice" error when multiple packages provide the same thing. It's different for packages coming from different projects, so we might consider pruning the choice list to the packages from the highest priority. That would also solve your "obsoletes" problem, I think. -- Configure bugmail: http://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