Hello,
I run CentOS 3.4 on 3 machines (i386). Original yum.conf
If I do a yum update: No actions to take
If I do a yum upgrade a machine that has no spamassassin: No actions to take
If I do a yum upgrade on 2 machines that have perl-Mail-SpamAssassin-3.0.1-1 installed (3rd party rpm, more recent than the CentOS/RHEL one):
I will do the following: [update: spamassassin 2.55-3.4.i386] I will install/upgrade these to satisfy the dependencies: [deps: perl-Time-HiRes 1.38-3.i386] Is this ok [y/N]:
Could someone please explain this behavior? Why is yum upgrade trying to upgrade a package that is a newer 3rd party rpm, with a different name?
Thanks, Francois
On Tue, 2005-03-29 at 23:26 -0800, Francois Caen wrote:
Hello,
I run CentOS 3.4 on 3 machines (i386). Original yum.conf
If I do a yum update: No actions to take
If I do a yum upgrade a machine that has no spamassassin: No actions to take
If I do a yum upgrade on 2 machines that have perl-Mail-SpamAssassin-3.0.1-1 installed (3rd party rpm, more recent than the CentOS/RHEL one):
I will do the following: [update: spamassassin 2.55-3.4.i386] I will install/upgrade these to satisfy the dependencies: [deps: perl-Time-HiRes 1.38-3.i386] Is this ok [y/N]:
Could someone please explain this behavior? Why is yum upgrade trying to upgrade a package that is a newer 3rd party rpm, with a different name?
Thanks, Francois
I think it is because the names are not the same for the packages ... you should be able to stop this by adding this line to the top of your /etc/yum.conf file:
exclude=spamassassin
On Tue, 2005-03-29 at 23:26 -0800, Francois Caen wrote:
Hello,
I run CentOS 3.4 on 3 machines (i386). Original yum.conf
If I do a yum update: No actions to take
If I do a yum upgrade a machine that has no spamassassin: No actions to take
If I do a yum upgrade on 2 machines that have perl-Mail-SpamAssassin-3.0.1-1 installed (3rd party rpm, more recent than the CentOS/RHEL one):
I will do the following: [update: spamassassin 2.55-3.4.i386] I will install/upgrade these to satisfy the dependencies: [deps: perl-Time-HiRes 1.38-3.i386] Is this ok [y/N]:
Could someone please explain this behavior? Why is yum upgrade trying to upgrade a package that is a newer 3rd party rpm, with a different name?
The why must be that something you have installed must require "spamassassin"
download both rpms and do:
rpm --requires -qp package_name
and
rpm --provides -qp package_name
then you can see what yum uses from each package to solve dependencies ... something is telling yum that you need ... and don't have spamassassin. I bet that the other package doesn't provide spamassassin.
Francois Caen wrote:
If I do a yum upgrade on 2 machines that have perl-Mail-SpamAssassin-3.0.1-1 installed (3rd party rpm, more recent than the CentOS/RHEL one):
I will do the following: [update: spamassassin 2.55-3.4.i386]
If you do "rpm -q spamassassin", what do you get?
Aleksandar Milivojevic wrote:
Francois Caen wrote:
If I do a yum upgrade on 2 machines that have perl-Mail-SpamAssassin-3.0.1-1 installed (3rd party rpm, more recent than the CentOS/RHEL one):
I will do the following: [update: spamassassin 2.55-3.4.i386]
If you do "rpm -q spamassassin", what do you get?
BTW, thinking of it more, is your (newer) SpamAssassin RPM called "spamasassin" or "perl-Mail-SpamAssassin"? If later, than you introduced inconsistency into your distribution. All packages that might reference spamassasin in dependencies etc will reference it as spamassassin, not as perl-Mail-SpamAssassin. Also, yum can't really deal with same package having different names. As far as yum is concerned, you do not have "spamassassin" installed on the system. You have "perl-Mail-SpamAssassin", and for yum, those are two completely different packages.
I don't think there is a way to easilly rename RPM package short of rebuilding it.
My advice, rebuild perl-Mail-SpamAssassin as "spamassassin". The easiest way is to fetch SRPM from CentOS 4 or Fedora 3 (both include version 3.x.x of SpamAssassin). "rpmbuild --rebuild srpm_file.src.rpm" should work just fine. Remove perl-Mail-SpamAssassin, and install this new "spamassassin" package.
BTW, hopefully you don't have both spamassassin and perl-Mail-SpamAssassin installed in parallel?
-
Aleksandar Milivojevic -
Francois Caen -
Johnny Hughes