http://bugzilla.novell.com/show_bug.cgi?id=592640 http://bugzilla.novell.com/show_bug.cgi?id=592640#c2 Ján Kupec <jkupec@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium CC| |jkupec@novell.com Summary|apparmor gets installed |patterns and/or their |even when pattern is |contents get installed even |tabooed at install |if the pattern is | |tabooed/locked --- Comment #2 from Ján Kupec <jkupec@novell.com> 2010-04-01 09:11:35 UTC --- Thanx for the report! IIRC we do not have any special pattern locking handling. That means, even if the pattern objects is locked, you still can install the packages it 'contains', since package locks lock different objects. And if you install enough packages to satisfy the pattern's dependencies, it is then reported as installed... This is of course a bug. That said, i see three options: 1) either we disable the pattern locking in the UIs 2) or we add additional logic for adding pattern locks which would also put locks on the packages it contains 3) or we change zypp/satsolver to do this automatically when a pattern lock is encountered -- 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.