On Sun, 2006-05-07 at 22:53 +0200, Kai Schaetzl wrote:
> Johnny Hughes wrote on Sun, 07 May 2006 10:49:42 -0500:
>
> > Assuming what I found to be true ... this is not a bug with yum or
> > protectbase ... or even I problem with the repos individually ... but a
> > problem if dag and kbs are used together.
>
> It is a problem whenever a package obsoletes another package and that or
> it's name is in other repos as well.
>
> > ------------------------------------
> > If you want to use Dags repo for clamav:
> >
> > in the kbs-CentOS-Extras repo add this line:
> >
> > exclude=clamav*
>
> Sure, I can do this, but I have to do this without protectbase, anyway.
>
> > As a side note, this kind of problem happens quite frequently when more
> > than one repo is used.
>
> But the whole point of protectbase is that it *protects*, isn't it? I mean
> in my eyes "protect" means "protect" against replacement by another repo
> by whatever means. I don't care if it updates, obsoletes or whatever. Why
> should "obsoletes" be handled different?
Because ... that is a second set of calculations
In the first set of calculations, all the packages where the names match
up are done .. hmmm, a new package named clamav-db is needed (and there
is nothing protected to prevent that). In a second set of
calculations ... clamav-db obsoletes something else.
If you try to install it doesn't do it ... NOW ... if the names were the
same (with or without the obsoletes) this would not happen.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.centos.org/pipermail/centos/attachments/20060507/213ebad5/attachment.bin
