Bob Taylor wrote:
On Fri, 2008-02-22 at 19:56 -0500, William L. Maltby wrote: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@xxxxxxxxx> wrote:<snip><snip>[snip]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.Thanks for your response, Bill. I added the protect lines attempting to locate this problem. I've removed all protect lines.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.Mind telling me what these are?
"protect=N" is part of the protectbase plugin. You do not want to install the protectbase and priorities plugins on the same machine.
Looking at your output of yum-\* you do not seem to have yum-protectbase installed, so the settings by themselves should not matter.
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos
