http://bugzilla.novell.com/show_bug.cgi?id=546594 User lmuelle@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=546594#c1 --- Comment #1 from Lars Müller 2009-10-13 12:08:09 MDT --- Created an attachment (id=322320) --> (http://bugzilla.novell.com/attachment.cgi?id=322320) zypper ll output -- 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=546594 User ma@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=546594#c3 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low CC| |ma@novell.com Summary|zypper ignores lock while |zypper does not |update |treat/display complex locks | |correctly. --- Comment #3 from Michael Andres 2009-10-14 06:02:50 MDT --- You locked 'package named mono', and this is not installed. You probably want to lock 'package named *mono*', or 'package named mono-core' because this provides 'mono'. I don't see an error here. The bug is invalid, but I keep it for the issue below: AFAIK zypper supports adding package name locks only. But editing "/etc/zypp/locks" in order to lock any package providing mono is legal. Actually any serialized PoolQuery makes a valid entry for /etc/zypp/locks. type: package match_type: glob case_sensitive: on - solvable_name: mono + solvable_provides: mono libzypp will respect this and lock any provider of 'mono'. Unfortunately zypper does not seem to expect this. The above entry would be reported as: # | Name | Type | Repository --+------------------+---------+----------- ... 7 | virt-manager | package | (any) 8 | (any) | package | (any) Maybe zypper should list only those entries it actually understands, and just tell about the number of complex queries it did not understand. # | Name | Type | Repository --+------------------+---------+----------- ... 7 | virt-manager | package | (any) --+-------- ---------+---------+----------- 1 more possibly handcrafted lock(s) zypper does not understand. -- 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=546594 http://bugzilla.novell.com/show_bug.cgi?id=546594#c5 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #5 from Michael Andres --- Newer zypper versions allow to lock '*mono*'. Also -m/-s allow to inspect the actually locked packages, even if a complex lock has no nice 'Name' to display. -- You are receiving this mail because: You are on the CC list for the bug.