Johnny Hughes wrote on Thu, 04 May 2006 17:06:00 -0500:
It is a replacement and not an upgrade that is causing the issue ... kbs (it seems) doesn't have clamav-db.
No. It seems that clamav-db is the whole signature db, providing it as an upgrade package is somewhat mute I guess.
So it seems that clamav-db gets to be installed, since it is not protected. Installing it causes something else to get removed (which should be protected) ... but that happens after the initial calculations, and it seems protectbase is not working on that set.
I am sure this is a protectbase plugin issue and not a yum issue. Though it should be consistent between check-update adn update.
I have submitted for a bugzilla account at the yum duke site, but am still waiting for the mail. I hope I'll get one soon. Then I submit it.
Kai