On Fri, 2008-02-22 at 15:37 -0800, Bob Taylor wrote:
On Fri, 2008-02-22 at 14:41 -0800, Akemi Yagi wrote:
On Fri, Feb 22, 2008 at 1:02 PM, Bob Taylor bob8221@gmail.com wrote:
<snip>
<snip>
# CentOS-Base.repo # # This file uses a new mirrorlist system developed by Lance Davis for CentOS. # The mirror system uses the connecting IP address of the client and the # update status of each mirror to pick mirrors that are updated to and # geographically close to the client. You should use this for CentOS updates # unless you are manually picking other mirrors. # # If the mirrorlist= does not work for you, as a fall back you can try the # remarked out baseurl= line instead. # #
[base] name=CentOS-$releasever - Base mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch= $basearch&repo =os #baseurl=http://mirror.centos.org/centos/$releasever/os/$basearch/ gpgcheck=1 gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-5 priority=1 protect=1
Priority *and* protect? Supposed to be a no-no.
Worse, it's on the updates too. I would carefully examine all your repo defs and have *either* protect or priority, but not both. Also make sure the settings are appropriate sionce you've add some other repos.
I've been using Rpmforge for a long time, NP. But at the time I established priorities, I disabled all protect settings.
And there are a couple exclude and include setups for a few special instances.
#released updates [updates] name=CentOS-$releasever - Updates mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch= $basearch&repo =updates #baseurl=http://mirror.centos.org/centos/$releasever/updates/$basearch/ gpgcheck=1 gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-5 priority=1 protect=1
Conflict?
<snip>
HTH