Bugzilla – Bug 350532
YaST Software management will not allow a package to be locked
Last modified: 2008-06-04 10:28:26 UTC
Within Software Management there is the option to lock a package so that it does not get deleted or updated. Although this selection is still allowed to be made it is not saved on exit and reverts back to an unlocked status. This old status is shown the next time the Software Management module is used. The status of locked should be saved as the updater will try and upgrade this package if it is not locked. (package is X11-video-nvidiaG01)
This is a duplicate of a later bug. The feature is not implemented in the UI. Andrew, you can add X11-video-nvidiaG01 to /etc/zypp/locks file. i cant find the duplicate.
Ok, but I'm a little confused now. If this is not implemented in the UI why is there an option there to lock the package and when you do a padlock appears against it? I have also seen packages locked by the system and have had to unlock them to perform a particular upgrade to another package.
This bug also exist on i386 arch. A lock issued in yast2 will be ignored by zypper (e.g. when using zypper up --type=package). As flash is broken for most browser and the xorg bug this bug is becoming more and more critical.
Comment #3, the lock is valid, but only for that session, it is not persistent, regression since we migrated from the old package manager.
Ok, I think I understand what is going on with this now. The remaining question is whether this will be fixed for OpenSUSE 11 or even 10.3?
Hi, Do we have any update as to wether this is fixed in OpenSUSE 11?
Hello, anybody home?
(Yes, but on vacation or busy with 11.0 - sorry.) This is fixed on 11.0. Locks applied via yast or zypper are remembered on commit.