Why I have some protected packages

marozsas · 06-01-2007, 02:47 PM

Hi,

I am using openSuse 10.2.
In the YaST2 sw_single, the installation tool, some packages are marked as a yellow lock and the tool-tip says the package is protected.

Why it is marked as protected ?
How to I got those protected packages ?
How to get a listing of all rpm packages marked as protected ?

The rpm tools say nothing about protected packages. I think this is a opensuse specific thing ?

How to control the protected status of a package ? I mean, what command line tool I must use to set/unset a package as protected ?

Protected packages will not upgrade even if a newer version is available, unless I manually un-protect them, in the YaST2 installation tool.

any info will be nice.

auxsvr · 06-02-2007, 11:50 AM

From yast2 help menu:

Quote:

Locked: This package is installed and should not be modified, especially not because of unresolved dependencies that other packages might have or get. Use this status for third-party packages that should not be overwritten by newer versions that may come with the distribution.

This has nothing to do with RPM, it's a setting of the package manager (yast) and can only be set through it. You can see the locked files when you select "installation summary" as a filter in software management.

jschiwal · 06-03-2007, 08:23 PM

That will happen if you install a package using the rpm command instead of using yast.

If you downloaded media related packages from a packman site, the package versions don't match the SuSE versions of the same packages. So they are locked to prevent a SuSE update from replacing these packages during an update.

If you have a packman repo added as an installation source, you can use "Installation Source" as the filter list, then in the right hand side pane, right click and select "all in this list..." -> update if newer available.

That allows you to update the xine, mplayer, audacity, etc. packages from another repo, such as packman.

If you simply installed a SuSE package using rpm, you could unlock it if you wanted.

---

If you select installation summary, you can list just the locked packages.

marozsas · 06-04-2007, 01:32 PM

Thanks for the enlightenment, fellows !

I was in doubt if there are something new in the rpm, but looks like it is a YaST thing.
I was in doubt too if locked packages means something bad or at least, an undesirable status.

Looks like packages installed from rpm cmd tool and from YaST via suse-guru and non-oss sources are marked are locked.

see'ya,