On Tue, 2006-09-05 at 07:48 -0400, Thomas E Dukes wrote:
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Johnny Hughes Sent: Tuesday, September 05, 2006 7:38 AM To: CentOS ML Subject: RE: [CentOS] Removed Plus kernel, yum still wants to update pluskernel
On Mon, 2006-09-04 at 14:47 -0400, Thomas E Dukes wrote:
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Jim Perrin Sent: Monday, September 04, 2006 2:35 PM To: CentOS mailing list Subject: Re: [CentOS] Removed Plus kernel,yum still wants
to update
plus kernel
So where does yum keep its 'memory', so I can remove
references to the
plus kernel and get back to the regular kernel?????
Either disable the centosplus repository, or exclude the
kernel from
that repository. I have no idea how yumex handles this, as I'm pretty much a console only type person. For general yum behavior, read 'man yum.conf' and look at the contents of /etc/yum.repos.d/
I have a similar problem but I use yum from the command
line so it may
be a problem with yum itself.
I installed GeoIP from Centos 'extras' repo. I also have
dag setup as
a repo. I have installed the protectbase plugin and it is
enabled.
In yum.conf I have enabled plugins. In the Centos repo
file, I have
all Centos repos protected and the dag repo set as unprotected.
Everytime I run yum update, it wants to 'replace' the geoip
from the
dag repo.
What's up with that?
TIA
Eddie
Dag has it named geoip and we have it named GeoIP
those are separate packages to yum ... set exclude=geoip in your dag repo.
Thanks, Johnny, but why is yum still wanting to install it if they are separate? I thought yum was case-sensitive.
Thanks,
Eddie
Because dag's package provides this:
Obsoletes: GeoIP < %{version}-%{release} Provides: GeoIP = %{version}-%{release} Provides: GeoIP-devel = %{version}-%{release} Obsoletes: GeoIP-devel < %{version}-%{release}
(notice the case)
and our package also provides the same things.
So ... they provide the same requirements BUT are named differently.
So, protectbase does not block them initially (different names), and protectbase does not recheck after the obsoletes section has one replace the other (as it sees them as different programs).
You need to pick one version to use and exclude it in the other repo.