http://bugzilla.novell.com/show_bug.cgi?id=549940 http://bugzilla.novell.com/show_bug.cgi?id=549940#c8 --- Comment #8 from Michael Andres <ma@novell.com> 2009-11-30 12:23:39 UTC --- Whatever we do, someone will complain. 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'. Zypper should follow easy rules. The easiest rule would have been "per default report problems. Use 'force' to fore a resolution". Zyppers rule is slightly more complex: "zypper 'in' does force, 'up' does not". You are right that my suggestion was not objective, because I'd favor the easiest rule. Sorry for this. But you IMO should consider reverting your change. You should not use different solver options, just because a non-package is, or could be, on the commandline. Stay with the current rule and say: This bug is invalid. You need to use 'zypper in --no-force-resolution -t patch k3b'. Or enable 'zypper patch k3b'. That's pure patch installation. -- 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.