differences between yum update and yum check-update

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



On Sun, 2006-05-07 at 10:37 -0500, Johnny Hughes wrote:
> 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
> anyone?
> _______________________________________________

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.  

That being the case, neither repo taking action IS acceptable (as each
repo is OK individually, and this is a cross repo problem). 

Therefore to fix this issue (if the repo maintainers have not / do not
update the repos ... or until they do) is to do this:

------------------------------------
If you want to use Dags repo for clamav:

in the kbs-CentOS-Extras repo add this line:

exclude=clamav*

-----------------------------------
If you want to use kbs repo for clamav:

in the dag repo add this:

exclude=clamd clamav*
-----------------------------------

As a side note, this kind of problem happens quite frequently when more
than one repo is used.

Thanks,
Johnny Hughes
-------------- 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/84912efe/attachment.bin

[Index of Archives]     [CentOS]     [CentOS Announce]     [CentOS Development]     [CentOS ARM Devel]     [CentOS Docs]     [CentOS Virtualization]     [Carrier Grade Linux]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Linux USB]
  Powered by Linux