https://bugzilla.novell.com/show_bug.cgi?id=690038
https://bugzilla.novell.com/show_bug.cgi?id=690038#c14
--- Comment #14 from Dieter Jurzitza
I am lowering the severity, as it is not straightforward to reproduce. You need to get the requires of a locked package and then do another operation to get the reset lock commited.
is kind of strange. As an administrator I am urged now to live with kpackagekit, and everyone knows that defective packages hang around all the time. And if you argue that an effect that happens _immediately_ and _always_ when using the services of kpackagekit you're urged to use as the former yast frontend for updates does not exist any more is not straightforwad to reproduce, hmm, then, please tell me what would be straightforward in your opinion? It is 100% reproducible ..... ;-) Don't get me wrong, I am glad you fix this, but I cannot agree with your points. This bug is severe IMHO because it touches the basics of system administration. If I have to tell people don't use this service because it definitively destroys functionalities (talking about the defective package of mgetty that is being distributed) then it is serious. At least much more serious than a simple broken feature of a non-system relevant program. Thank you anyway for fixing this quickly, take care Dieter Jurzitza -- 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.