-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have a list of rpms packages that I installed, i.e. xine and libxine*, that now matter how many times I go into YaST and try to mark as keep they revert back to locked. I generally use the option to show all changes to installations, which then presents all the locked files as being reinstalled. I then choose the option to change the status of all in the list to mark as "keep". Am I missing something? Is there a way to permenantly mark this as keep (the blue check mark rather than the gold lock symbol)? Any help would be greatly appreciated. TIA, Curtis. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE/hahjiqnGhdjCOJsRAqvUAJ9dRYxiZKUiYN6CE+e+O/2sGMzOjACfSSI1 7a7WeABPA2+O5DJEwRM8SI0= =OP6k -----END PGP SIGNATURE-----
In a previous message, Curtis Rey
I have a list of rpms packages that I installed, i.e. xine and libxine*, that now matter how many times I go into YaST and try to mark as keep they revert back to locked.
AIUI, YaST does this with any RPMs that you have installed yourself outside YaST (e.g. using GnoRPM or just the rpm command). This is so that it doesn't overwrite your versions with any SuSE-supplied versions in case the version numbers clash. Is there a particular reason you want them marked "keep" instead of locked? John -- John Pettigrew Headstrong Games john@headstrong-games.co.uk Fun : Strategy : Price http://www.headstrong-games.co.uk/ Board games that won't break the bank Fields of Valour: 2 Norse clans battle on one of 3 different boards
participants (2)
-
Curtis Rey
-
John Pettigrew