https://bugzilla.novell.com/show_bug.cgi?id=822128 https://bugzilla.novell.com/show_bug.cgi?id=822128#c2 Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | --- Comment #2 from Felix Miata <mrmazda@earthlink.net> 2013-06-04 09:14:44 UTC --- (In reply to comment #1)
Problem: conflicting requests Solution 1: do not keep kernel-desktop installed
You do not install/remove the package in spite of a lock, but you remove the lock rule to make the package installable/removable. It's the same behavior as in the UIs.
What UIs? IOW, what exactly can I do to reproduce so as to see behavior "in the UIs"? Maybe it needs changing too.
I don't think we want to change it.
I think we do. If it is not to be changed according to comment 0, then the language in the possible solutions in answer to the question need to be changed so that it is clear what is actually happening: lock removal rather than lock override as it appears now. *Override does not equate to remove* As it is now in M0 system overdue for upgrade to M1, even 'zypper -v --no-refresh rm kernel-desktop-3.8.2' with kernel-desktop locked produced: 1-no cmdline feedback indicating change to locks file in response to selecting "do not keep..." to indicate kernel-desktop removal from locks file. 2-no indication of change to locks file in /var/log/zypp/history 3-2188 lines added to /var/log/zypper.log to sift through to discover indication of lock removal cf. Mageia urpm behavior, which uses skip.list rather than a locks system to prevent automatic installation of enumerated packages. -- 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.