[Bug 344888] New: solver silently changed my input and generated set of unbelievable conflicts then
https://bugzilla.novell.com/show_bug.cgi?id=344888 Summary: solver silently changed my input and generated set of unbelievable conflicts then Product: openSUSE 10.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: mvancura@novell.com QAContact: jsrain@novell.com Found By: L3 Created an attachment (id=185227) --> (https://bugzilla.novell.com/attachment.cgi?id=185227) archive with testcase, screenshot and logs situation: 10.3 GM installed from media ("KDE" type of installation) and online update run at the end of installation. After first run (patch for YaST2), the second set of patches contained a patch for mono. As I don't want to have any mono package on my system, I clicked on that patch to see mono packages and marked them all as "tabooed". Forgot to mark patch itself as tabooed too. what I got: Automatic check of dependencies showed me a set of conflicts where even conflicts among packages marked as tabooed were listed! what I expected: one conflict listed: "patch bytefx-data-mysql can't be installed" what was behind: when I moved the window with solver results, I saw that instead of reporting the conflict with patch, solver silently removed taboo flag from some packages and marked them as "to install" instead. Automatic and silent change of my input is something which should never happen. screenshot, testcase and logs are attached -- 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=344888 Martin Mrazik <mmrazik@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |yast2-maintainers@suse.de -- 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=344888 Arvin Schnell <aschnell@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |schubi@novell.com -- 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=344888 User schubi@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=344888#c5 Stefan Schubert <schubi@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #5 from Stefan Schubert <schubi@novell.com> 2008-04-23 04:04:08 MST --- The error message has been produced by missing requirements in the atoms. As we do not have atoms for Code 11 anymore this error will not happend anymore. -- 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=344888 User mvancura@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=344888#c6 Milan Vancura <mvancura@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #6 from Milan Vancura <mvancura@novell.com> 2008-04-23 04:13:29 MST --- OK. I think the problem was little different, but it doesn't matter. I already needed a solution or workaround and apt seemed to be the easiest way, so I switched to apt (not apt-rpm) on my most critical machines :-) -- 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