[CentOS] differences between yum update and yum check-update

Sun May 7 15:37:10 UTC 2006
Johnny Hughes <mailing-lists at hughesjr.com>

On Thu, 2006-05-04 at 19:28 +0200, Kai Schaetzl wrote:
> yum check-update:
> clamav.i386             0.88.1-1.el4.kb        kbs-CentOS-Extra
> clamav-data.i386        0.88.1-1.el4.kb        kbs-CentOS-Extra
> clamav-lib.i386         0.88.1-1.el4.kb        kbs-CentOS-Extra
> clamav-update.i386      0.88.1-1.el4.kb        kbs-CentOS-Extra
> yum update:
> Installing:
>  clamav-db     i386       0.88.2-1.el4.rf  rpmforge          4.0 M
>      replacing  clamav-update.i386 0.88-1.el4.kb
> Updating:
>  clamav        i386       0.88.1-1.el4.kb  kbs-CentOS-Extras  545 k
>  clamav-lib    i386       0.88.1-1.el4.kb  kbs-CentOS-Extras  143 k
> Updating for dependencies:
>  clamav-data   i386       0.88.1-1.el4.kb  kbs-CentOS-Extras  3.4 M
> The installed clam rpms on this machine are from kbs-CentOS-Extras (which 
> is protected=1 while rpmforge/dag is not!)
> I think not only should the replacement not happen if the replaced 
> rpm/repo is protected, there should also be no difference between update 
> and check-update! A bug in yum?
> Kai

I am still looking at this particular issue, but this is what I think I
have found:

clamav-db (dag) IS a different name ... but the same thing as clamav-
data (kbs).

It also seems that clamd (dag) is the same thing as clamav-server (kbs).

So .. it seems that what is required to make both of these repos to be
enabled at the same time is for dag to add these obsoletes:

In clamav-db:		obsoletes clamav-data
In clamd:		obsoletes clamav-server

and for kbs to add these:

In clamav-data:		obsoletes clamav-db
In clamav-server:	obsoletes clamd

Anyway ... that is what I think I see as the problem ... conformation
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://lists.centos.org/pipermail/centos/attachments/20060507/5c8b536b/attachment-0005.sig>