Bugzilla – Bug 332853
yast2 sw_single Taboo -- Never Install does not stick
Last modified: 2008-11-04 09:31:56 UTC
In openSuSE 10.3 when a package is marked as Taboo -- Never Install, the setting is sticky only for the current session, it is cleared when the the session is quit, even with "File/Quit -- Save Changes" Although the number of forcefully installed packages has been reduced remarkably, there remain a few I'd like to block out permanently ( Smartlink Softmodem for one ). Likewise the flag Protected -- Do Not Modify does not stick permanently either. workstation6l:/home/cjp # rpm -qa | grep yast yast2-trans-en_US-2.15.5-6 yast2-core-2.15.12-6 yast2-control-center-qt-2.15.4-12 yast2-gtk-2.15.9-34 yast2-nfs-client-2.15.0-25 yast2-x11-2.15.11-22 yast2-registration-2.15.3-15 yast2-ldap-server-2.15.5-76 yast2-ftp-server-2.15.9-24 yast2-slp-2.15.0-31 yast2-qt-2.15.16-19 yast2-control-center-gnome-2.13.2-91 yast2-country-2.15.20-7 yast2-runlevel-2.15.3-19 yast2-fingerprint-reader-2.15.2-27 yast2-security-2.15.1-23 yast2-iscsi-client-2.15.2-39 yast2-installation-2.15.54-4 yast2-samba-server-2.15.7-57 yast2-backup-2.15.4-50 yast2-control-center-2.15.4-12 yast2-repair-2.15.8-0.1 yast2-schema-2.15.0-123 yast2-2.15.58-12 yast2-ca-management-2.15.2-28 yast2-pam-2.14.0-128 yast2-sysconfig-2.15.3-58 yast2-ntp-client-2.15.12-7 yast2-ldap-client-2.15.12-37 yast2-http-server-2.15.7-27 autoyast2-2.15.17-17 yast2-storage-lib-2.15.27-4 yast2-ncurses-2.15.27-16 yast2-printer-2.15.6-4 yast2-dns-server-2.15.3-81 yast2-metapackage-handler-0.7.1-9 yast2-restore-2.15.4-22 yast2-xml-2.15.0-55 yast2-transfer-2.14.0-107 yast2-theme-openSUSE-2.15.14-4 yast2-perl-bindings-2.15.3-29 yast2-mouse-2.15.1-81 yast2-apparmor-2.1-26 yast2-nfs-server-2.15.4-25 yast2-support-2.15.3-14 yast2-packager-2.15.81-4 yast2-kerberos-client-2.15.7-32 yast2-users-2.15.38-7 yast2-storage-2.15.27-4 yast2-mail-2.15.23-2 yast2-tune-2.15.7-20 yast2-update-2.15.23-21 yast2-samba-client-2.15.11-33 autoyast2-installation-2.15.17-17 yast2-bootloader-2.15.29-2 yast2-trans-stats-2.15.0-32 yast2-pkg-bindings-2.15.51-4 yast2-ldap-2.15.1-83 yast2-bluetooth-2.15.4-17 yast2-scanner-2.15.5-42 yast2-nis-client-2.15.3-21 yast2-network-2.15.81-2 yast2-online-update-2.15.23-9 yast2-profile-manager-2.15.0-52 yast2-sudo-2.15.3-86 yast2-hardware-detection-2.15.8-36 yast2-sound-2.15.11-18 yast2-firewall-2.15.8-8 yast2-tftp-server-2.14.0-105 yast2-online-update-frontend-2.15.23-9 yast2-inetd-2.15.1-41 yast2-add-on-2.15.17-4
Created attachment 177596 [details] YaST2 Logs
There is a similar problem regarding to protected packages, see bug #325955.
This applies to YOU too. Unsure if a different report should be filed for it. If you taboo an update in YOU it will not be tabooed in next run. And also openSUSE Updater won't be affected.
*** Bug 325955 has been marked as a duplicate of this bug. ***
Will be handled in 11.0. Definitely not in 10.3
bug persists in 11.0 A3
It works for me. The issue is that you need to commit (accept changes) even if there are no packages marked for install for locks to be saved. Fixed in 2.16.44 where saving changes also saves Locks first.
The introduced fix is wrong and also leads to a crash (bug #395040). Persistent are simply not available in Alpha3, they were introduced: ------------------------------------------------------------------- Thu May 1 00:50:51 CEST 2008 - ma@suse.de - Load and maintain persistent hard locks stored in /etc/zypp/locks. Locks are loaded together with the target, and changes are writen back on commit. zypp.conf option locksfile.apply can be used to turn this feature on or off. (FATE #120352) - version 4.18.0
Bad fix reverted in 2.16.47
As 11.0 is in maintenance mode now, we need to release an update for this bug.
Reopened for update process. Anja: we need a SWAMPID... Michael: please provide a Patchinfo for 11.0
Package/patchinfo submitted for 11.0.
closing
released
*** Bug 164445 has been marked as a duplicate of this bug. ***
QA - Could you please have a look at this and its duplicate - There is a great deal of issues which never recieved a response. Sorry to dump this on you - However I think everyone involved would like to know - Is if Fixed and released in V nnn.nn
This should be released and fixed.