top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Centos piority warning - 66 packages excluded due to repository priority protections

+2 votes

If I add priority=1 to [updates] in CentOS-Base.repo
when I run "sudo yum update" I get the warning 66 packages excluded due to repository priority protections

This does not seem to have any adverse effect, but what exactly does it mean?

posted Aug 15, 2013 by Abhay Kulkarni

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

2 Answers

+1 vote
Best answer

See ( take a close look at section 5 )

Generally all active repo's in Base would be given the same priority. If you have only added a setting of 1 for updates then all other repos will have a priority of 99 (lower).

answer Aug 15, 2013 by Bob Wise
I had actually read this section, but evidently do not understand it. I take it the 66 packages mentioned are in "unofficial" repositories, in my case rpmforge.repo.rpmnew ?
0 votes

If you have a repo called something.repo.rpmnew, it will be ignored. You would have to rename it to something.repo.

To oversimplify, say that you have rpmforge, base, and epel repos. Say that all of them have versions of perl. However, these versions may conflict with each other and break things.

So, if you gave base and updates priority of 1, then the others, even if they have a later version of perl, won't install it. The downside is that you're running the older version. The upside is that you don't risk this newer version of perl breaking some other package that you'd forgotten.

There are disadvantages--as the wiki page in question mentions, the late Seth Vidal disliked it.

answer Aug 15, 2013 by anonymous
Similar Questions
+1 vote

Is it possible to exclude all packages except one or two in a repo file? The man page for yum.conf didn't give me any hints. I tried unsuccessfully adding this line:


Is there a way to set up this repo so that when I run "yum upgrade" it will only check the firefox and xulrunner packages from the remi repo?

+2 votes

I have a small problem with some packages : I was doing an update over ssh and my connection was interrupted .. now i have a lots of duplicates and if i try to remove them, yum tries to uninstall all system (447 packages 1.4 gb)

Any idea how can I clean this mess? It would be pretty bad if the machine needs to be re-installed only because the connection went bad during the process...

+1 vote

During yum upgrade a couple days ago, I saw this:

Cleanup : kernel-3.10.0-229.20.1.el7.x86_64  35/64
warning: file /lib/modules/3.10.0-229.20.1.el7.x86_64/modules.softdep: 
remove failed: No such file or directory
warning: file /lib/modules/3.10.0-229.20.1.el7.x86_64/modules.devname: 
remove failed: No such file or directory

Should I be concerned about this? What could have caused it?

+2 votes

I am having problems with a CentOS 6.4 box that I was in the process of doing a yum update to 6.5. Unfortunately the system hung during the update and I was forced to reboot it and it is now a bit of a mess.

Can someone point me in the direction of any documentation that would assist in the recovering from this.

+1 vote

In order to make the same installation on two servers where all was installed via yum/rpm, I want to dump a list of all installed packages on the first server.

My problem is if I just "yum list installed", some weird formatting prints packages information on 2 lines...
I have to

 # yum list installed | awk '{print $1}' 
 | grep -v '@' | grep -vE '^[0-9]'

Is there a cleaner way?

 # rpm -aq

Is not OK because it includes version in a way it's more hard to parse just the package name.