http://bugzilla.novell.com/show_bug.cgi?id=549940 http://bugzilla.novell.com/show_bug.cgi?id=549940#c9 --- Comment #9 from Ján Kupec <jkupec@novell.com> 2009-11-30 15:58:19 UTC --- (In reply to comment #8)
Whatever we do, someone will complain.
That's true :O)
I see lots of bugs where people obviously do no understand why 'in' does it and 'up' does not. They don't seem to recognize (or expect), that a problem reported in 'up' corresponds with a package deleted in 'in'.
Hmm.. yes, i agree.
Stay with the current rule and say: This bug is invalid. You need to use 'zypper in --no-force-resolution -t patch k3b'.
What about making it configurable in zypper.conf? [solver] <cut> ## Comma-separated list of commands in which the resolution should be forced ## when solving package dependencies. This means the solver ## will automatically opt to remove problematic packages instead ## of asking the user how to resolve the dependency problem. ## ## This is particularly useful in the 'remove' command, since one ## typically wants to remove the requested package and all the packages ## which depend on it, without being asked. But one may find it convenient ## to force the resolution also in the 'install' command, or perhaps even ## others. ## ## This setting can be overridden ad-hoc by the --force-resolution and ## --no-force-resolution command line options. ## ## Values: remove, install, update, patch, verify ## Default: remove forceResolution = remove, install
Or enable 'zypper patch k3b'. That's pure patch installation.
good idea, too -- 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.