Mailinglist Archive: opensuse (3336 mails)

< Previous Next >
Re: [SLE] How do I protect a YaST package from upgrades?
  • From: "Stephen Carter" <stephen@xxxxxxxxxxxx>
  • Date: Thu, 01 Dec 2005 16:25:24 +0000
  • Message-id: <s38f2406.042@loopback>
>>> Stephen Carter 11/28/05 1:17 PM >>>
>>>> "Carlos E. R." <robin1.listas@xxxxxxxxxx> 11/27/05 2:57 PM >>>
>>Hash: SHA1
>>The Sunday 2005-11-27 at 12:56 -0000, Stephen Carter wrote:
>>> I've customised a package I installed through YaST from the default
>>> installation DVD on SuSE 10.0 so never want to have the option to
>>> upgrade it via YOU if one should come available.
>>> In YaST I can see there is a 'protected' option for a package that's
>>> already been installed but when I select this then click Finish, and go
>>> back into YaST the package is no longer marked as protected.
>>Yes, for some unknown reason the "taboo" mark does not stick. It has been
>>a feature aka bug for a long time (ie, years).
>>> Is there some way of marking a package 'protected' after it has been
>>> installed via YaST?
>>I change the release nunmber to .999 in the rpm. If that is not enough,
>>change the version number.
>>- --
>> Carlos Robinson
>So you can't do it if the installation source is non-writable media such as
>CD/DVD or a public web source, and the only way is to copy the rpm to
> your hard disk, edit it, then install it via YaST.
>Well at least it's a workaround, although an ugly one...
>Thanks Carlos,

Found a solution to this issue.

It appears the protected option will only stick if any other package installation state in YaST is changed, i.e. installed or removed.

This option is also only available to already installed packages.

If you want to install a SuSE rpm via YaST and protect it from any future updates via YOU, install it as normal then go back to the installation screen, right-click the package and select 'protected' then select *another* arbitary package and install that as well.

Now go back to the installation screen one more time and remove the arbitary package you just installed. You will also notice the protected tag has now 'stuck' to the original package.



< Previous Next >
This Thread
Follow Ups