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?
Cheers,
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.
On Tue, Sep 06, 2005 at 06:10:23AM -0500, Johnny Hughes wrote:
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:
<snip>
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.
It still happens. Also note that 'yum check-update' doesn't show anything, but yum update says:
Resolving Dependencies --> Populating transaction set with selected packages. Please wait. ---> Package spamassassin.i386 0:3.0.4-1.el4 set to be updated --> Running transaction check
Dependencies Resolved Transaction Listing: Install: spamassassin.i386 0:3.0.4-1.el4 - update
Other Transactions: Obsoleting: perl-Mail-SpamAssassin.i386 0:3.1.0-1 with spamassassin.i386 0:3.0.4-1.el4
Total download size: 680 k Is this ok [y/N]: N Exiting on user Command Complete!
So there probably is something with my new version. What to look for?
jelsum:/root-# rpm -qip --provides --requires /users/www/archive/CS-Yum/cs-addons/redhat/el4/RPMS/spamassassin-3.1.0-1.i386.rpm Name : spamassassin Relocations: /usr Version : 3.1.0 Vendor: Utrecht University Release : 1 Build Date: Thu 01 Sep 2005 10:56:35 AM CEST Install Date: (not installed) Build Host: sarastro.cs.uu.nl Group : Applications/Mail Source RPM: spamassassin-3.1.0-1.src.rpm Size : 834683 License: Apache License 2.0 Signature : DSA/SHA1, Thu 01 Sep 2005 10:56:36 AM CEST, Key ID d5ea1490b25d630f Packager : Henk van Lingen henkvl@cs.uu.nl URL : http://spamassassin.apache.org/ Summary : a spam filter for email which can be invoked from mail delivery agents Description : SpamAssassin provides you with a way to reduce, if not completely eliminate, Unsolicited Bulk Email (or "spam") from your incoming email. It can be invoked by a MDA such as sendmail or postfix, or can be called from a procmail script, .forward file, etc. It uses a perceptron-optimized scoring system to identify messages which look spammy, then adds headers to the message so they can be filtered by the user's mail reading software. This distribution includes the spamc/spamc components which considerably speeds processing of mail. config(spamassassin) = 3.1.0-1 libspamc.so spamassassin = 3.1.0-1 /bin/sh /bin/sh /bin/sh /bin/sh /sbin/chkconfig /usr/bin/perl config(spamassassin) = 3.1.0-1 libc.so.6 libc.so.6(GLIBC_2.0) libc.so.6(GLIBC_2.1) libdl.so.2 perl(Carp) perl(Config) perl(Cwd) perl(Digest::SHA1) perl(Errno) perl(File::Path) perl(File::Spec) perl(File::Spec) >= 0.8 perl(Getopt::Long) perl(IO::Handle) perl(IO::Pipe) perl(IO::Socket) perl(Mail::SpamAssassin) perl(Mail::SpamAssassin::ArchiveIterator) perl(Mail::SpamAssassin::Logger) perl(Mail::SpamAssassin::Message) perl(Mail::SpamAssassin::NetSet) perl(Mail::SpamAssassin::PerMsgLearner) perl(Mail::SpamAssassin::SpamdForkScaling) perl(Mail::SpamAssassin::SubProcBackChannel) perl(Mail::SpamAssassin::Util::Progress) perl(POSIX) perl(Pod::Usage) perl(Pod::Usage) perl(bytes) perl(lib) perl(strict) perl(vars) perl(warnings) perl-Mail-SpamAssassin = 3.1.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 jelsum:/root-#
Cheers,
On Tue, 2005-09-06 at 13:27 +0200, Henk van Lingen wrote:
On Tue, Sep 06, 2005 at 06:10:23AM -0500, Johnny Hughes wrote:
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:
<snip>
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.
It still happens. Also note that 'yum check-update' doesn't show anything, but yum update says:
Resolving Dependencies --> Populating transaction set with selected packages. Please wait. ---> Package spamassassin.i386 0:3.0.4-1.el4 set to be updated --> Running transaction check
Dependencies Resolved Transaction Listing: Install: spamassassin.i386 0:3.0.4-1.el4 - update
Other Transactions: Obsoleting: perl-Mail-SpamAssassin.i386 0:3.1.0-1 with spamassassin.i386 0:3.0.4-1.el4
Total download size: 680 k Is this ok [y/N]: N Exiting on user Command Complete!
So there probably is something with my new version. What to look for?
jelsum:/root-# rpm -qip --provides --requires /users/www/archive/CS-Yum/cs-addons/redhat/el4/RPMS/spamassassin-3.1.0-1.i386.rpm Name : spamassassin Relocations: /usr Version : 3.1.0 Vendor: Utrecht University Release : 1 Build Date: Thu 01 Sep 2005 10:56:35 AM CEST Install Date: (not installed) Build Host: sarastro.cs.uu.nl Group : Applications/Mail Source RPM: spamassassin-3.1.0-1.src.rpm Size : 834683 License: Apache License 2.0 Signature : DSA/SHA1, Thu 01 Sep 2005 10:56:36 AM CEST, Key ID d5ea1490b25d630f Packager : Henk van Lingen henkvl@cs.uu.nl URL : http://spamassassin.apache.org/ Summary : a spam filter for email which can be invoked from mail delivery agents Description : SpamAssassin provides you with a way to reduce, if not completely eliminate, Unsolicited Bulk Email (or "spam") from your incoming email. It can be invoked by a MDA such as sendmail or postfix, or can be called from a procmail script, .forward file, etc. It uses a perceptron-optimized scoring system to identify messages which look spammy, then adds headers to the message so they can be filtered by the user's mail reading software. This distribution includes the spamc/spamc components which considerably speeds processing of mail. config(spamassassin) = 3.1.0-1 libspamc.so spamassassin = 3.1.0-1 /bin/sh /bin/sh /bin/sh /bin/sh /sbin/chkconfig /usr/bin/perl config(spamassassin) = 3.1.0-1 libc.so.6 libc.so.6(GLIBC_2.0) libc.so.6(GLIBC_2.1) libdl.so.2 perl(Carp) perl(Config) perl(Cwd) perl(Digest::SHA1) perl(Errno) perl(File::Path) perl(File::Spec) perl(File::Spec) >= 0.8 perl(Getopt::Long) perl(IO::Handle) perl(IO::Pipe) perl(IO::Socket) perl(Mail::SpamAssassin) perl(Mail::SpamAssassin::ArchiveIterator) perl(Mail::SpamAssassin::Logger) perl(Mail::SpamAssassin::Message) perl(Mail::SpamAssassin::NetSet) perl(Mail::SpamAssassin::PerMsgLearner) perl(Mail::SpamAssassin::SpamdForkScaling) perl(Mail::SpamAssassin::SubProcBackChannel) perl(Mail::SpamAssassin::Util::Progress) perl(POSIX) perl(Pod::Usage) perl(Pod::Usage) perl(bytes) perl(lib) perl(strict) perl(vars) perl(warnings) perl-Mail-SpamAssassin = 3.1.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1
hmm .. also put spamasassin in the exclude= line for the repo like this:
exclude=spamassassin perl-Mail-SpamAssassin
On Tue, Sep 06, 2005 at 06:38:06AM -0500, Johnny Hughes wrote:
hmm .. also put spamasassin in the exclude= line for the repo like this:
exclude=spamassassin perl-Mail-SpamAssassin
Than it wants to do the one from [base]. After also excluding that, it's out of options and doesn't want to downgrade anymore. Remains the question why? Is yum using versionnumbers from somewhere else than what 'rpm -qip' shows?
Regards,
On Tue, 2005-09-06 at 13:50 +0200, Henk van Lingen wrote:
On Tue, Sep 06, 2005 at 06:38:06AM -0500, Johnny Hughes wrote:
hmm .. also put spamasassin in the exclude= line for the repo like this:
exclude=spamassassin perl-Mail-SpamAssassin
Than it wants to do the one from [base]. After also excluding that, it's out of options and doesn't want to downgrade anymore. Remains the question why? Is yum using versionnumbers from somewhere else than what 'rpm -qip' shows?
Yes. It's using Provides and Obsoletes which -qi won't pick up on.
On Tue, Sep 06, 2005 at 08:08:16AM -0400, Ignacio Vazquez-Abrams wrote:
exclude=spamassassin perl-Mail-SpamAssassin
Than it wants to do the one from [base]. After also excluding that, it's out of options and doesn't want to downgrade anymore. Remains the question why? Is yum using versionnumbers from somewhere else than what 'rpm -qip' shows?
Yes. It's using Provides and Obsoletes which -qi won't pick up on.
Oke, so the problem is the 'Obsoletes' from the CentOS one, which is a 'Requires' in my new version.
I'll have a look why RedHat makes it one package whereas spamassassin.org's specfile makes it two.
Cheers,
On Tue, 6 Sep 2005, Henk van Lingen wrote:
I'll have a look why RedHat makes it one package whereas spamassassin.org's specfile makes it two.
Yes, that is a major PITA.
Kind regards, -- dag wieers, dag@wieers.com, http://dag.wieers.com/ -- [all I want is a warm bed and a kind word and unlimited power]
On Tue, 2005-09-06 at 14:38 +0200, Henk van Lingen wrote:
On Tue, Sep 06, 2005 at 08:08:16AM -0400, Ignacio Vazquez-Abrams wrote:
exclude=spamassassin perl-Mail-SpamAssassin
Than it wants to do the one from [base]. After also excluding that, it's out of options and doesn't want to downgrade anymore. Remains the question why? Is yum using versionnumbers from somewhere else than what 'rpm -qip' shows?
Yes. It's using Provides and Obsoletes which -qi won't pick up on.
Oke, so the problem is the 'Obsoletes' from the CentOS one, which is a 'Requires' in my new version.
Ew, an unversioned Obsoletes. Please log this in RH's Bugzilla when you get a chance.
-
Dag Wieers -
Henk van Lingen -
Ignacio Vazquez-Abrams -
Johnny Hughes