On Tue, 2005-09-06 at 09:59 +0200, Henk van Lingen wrote:
Hi,
As there is no (decent) way to specify a particular repo for an particular package with yum, I'm having an odd problem: Although the version numbers differ, I have 2 spamassassin pkgs in different repo's (updates and my own addons) which are seen as updates to eachother:
jelsum:/root-# tail -11 /var/log/yum.log Sep 02 04:26:34 Installed: perl-Mail-SpamAssassin.i386 3.1.0-1 Sep 02 04:26:35 Updated: spamassassin.i386 3.1.0-1 Sep 03 05:01:36 Obsoleting: spamassassin.i386 3.0.4-1.el4 Sep 03 05:01:37 Erased: perl-Mail-SpamAssassin Sep 04 04:37:52 Installed: perl-Mail-SpamAssassin.i386 3.1.0-1 Sep 04 04:37:53 Updated: spamassassin.i386 3.1.0-1 Sep 05 04:21:15 Obsoleting: spamassassin.i386 3.0.4-1.el4 Sep 05 04:21:16 Erased: perl-Mail-SpamAssassin Sep 06 04:34:37 Installed: perl-Mail-SpamAssassin.i386 3.1.0-1 Sep 06 04:34:50 Updated: syslinux.i386 3.11-1.2.el4.rf Sep 06 04:34:51 Updated: spamassassin.i386 3.1.0-1
What can be wrong?
Not sure, but you can use an:
exclude=perl-Mail-SpamAssassin
in the repo that has the old one and see if that helps. (This would go in the configuration for that repo and not in the global configuration).
If it still happens, there is an issue with the new version of spamassassin.