On Mon, 2005-10-24 at 14:40 +0200, Kai Schaetzl wrote:
> 1. There was a (actually two) spamassassin.rpm of SA 3.1.0 installed, the
> rpm was built from the tar.gz sources for SA with the specs file provided
> with it. It produces two files for installation: perl-Mail-SpamAssassin
> and spamassassin. The update wiped them and installed SA 3.0.4 with this
> message:
> Obsoleting: perl-Mail-SpamAssassin.i386 0:3.1.0-1 with spamassassin.i386
> 0:3.0.4-1.el4
>
> Shouldn't this update get skipped because the version information is
> higher than the CentOS package? I found several mentions that I can
> exclude packages from yum updating. How can I do this? I don't want to
> update only specific packages, I only want to exclude a very few packages.
The name is different and the new package may have an unversioned
Obsoletes entry so the version will be ignored. The best thing to do is
to grab the SRPM, update the sources, change the version, and rebuild.
--
Ignacio Vazquez-Abrams <ivazquez@xxxxxxxxxxxx>
http://centos.ivazquez.net/
gpg --keyserver hkp://subkeys.pgp.net --recv-key 38028b72
-------------- 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/20051024/ea5d99be/attachment.bin
