SpamAssassin update is broken?
Under SuSE Professional 9.0 on x86
Ever since I installed the updated SpamAssassin package from SuSE, I have
been getting the following errors when attempting to start spamd:
Can't locate Mail/SpamAssassin/NetSet.pm in @INC (@INC contains: lib
../lib /usr/lib/perl5/site_perl/5.8.1/i586-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.1
/usr/lib/perl5/5.8.1/i586-linux-thread-multi /usr/lib/perl5/5.8.1
/usr/lib/perl5/site_perl
/usr/lib/perl5/vendor_perl/5.8.1/i586-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.8.1 /usr/lib/perl5/vendor_perl) at
/usr/sbin/spamd line 35.
BEGIN failed--compilation aborted at /usr/sbin/spamd line 35.
I notice that no update was issued for the perl-spamassassin package
(Still 2.55-75) when the spamassassin package (now 2.64-4) was updated.
Am I missing something or did SuSE just release a broken update?
Cheers.
-----
/"\ Happiness Will Prevail!
Ichaelmay wrote regarding '[SLE] SuSE update broke spamd on SuSE 9.0' on Wed, Aug 25 at 12:45:
SpamAssassin update is broken?
Under SuSE Professional 9.0 on x86
[...]
I notice that no update was issued for the perl-spamassassin package (Still 2.55-75) when the spamassassin package (now 2.64-4) was updated. Am I missing something or did SuSE just release a broken update?
Normally I really advocate staying with the SuSE packages for things, even if it means remaining a minor version ro two behind. But for perl modules, I make an exception. Just go to CPAN and update the Mail::SpamAssassin module (and everythign else that it thinks needs an update). CPAN works *very* reliably. --Danny, not really answering the question, but sort of...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 25 August 2004 18:45, Ichaelmay Ewlynay Akeblay wrote:
SpamAssassin update is broken?
Under SuSE Professional 9.0 on x86
I notice that no update was issued for the perl-spamassassin package (Still 2.55-75) when the spamassassin package (now 2.64-4) was updated. Am I missing something or did SuSE just release a broken update?
They provided another update today. But I have had no problems with any of these updates, so perhaps your problem is caused by something else? Steve -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBLPd794mqX5AIfgARAmXzAJ4t2eYxBGt4DSazMLw2dsmvoutEQwCfbtM6 o8hKH/AhloUqXu+QpAVbg9Y= =6v2D -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 25 August 2004 21:32, Steve King wrote:
On Wednesday 25 August 2004 18:45, Ichaelmay Ewlynay Akeblay wrote:
SpamAssassin update is broken?
Under SuSE Professional 9.0 on x86
I notice that no update was issued for the perl-spamassassin package (Still 2.55-75) when the spamassassin package (now 2.64-4) was updated. Am I missing something or did SuSE just release a broken update?
They provided another update today. But I have had no problems with any of these updates, so perhaps your problem is caused by something else?
Steve
<blush> Just spotted you are using 9.0, and the update I am referring to is 9.1. But I suppose a 9.0 update can't be far off. S. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBLPlz94mqX5AIfgARAkKGAJwMKT9V4GnsvJIumgM64ZJe35JFxgCdFsJh SX2p7Xva5DOKH5LO7cIwevQ= =cr/6 -----END PGP SIGNATURE-----
Interesting... used online update to check for new updates to spamassassin. It installed a new update to spamassassin... with the same version: 2.64-4. Looking in /var/lib/YaST2/you/mnt/i386/update/9.0/patches I see two very recent spamassassin patches: -rw-r--r-- 1 root root 1757 Aug 24 12:14 spamassassin-51567 -rw-r--r-- 1 root root 2618 Aug 25 13:46 spamassassin-51604 Tsk tsk. Sloppy. They should have incremented the version of the RPM so it was clear that 2.64-4 was broken, and 2.64-5 or whatever was the new good package. Now nobody will be able to easily tell if they have the good or broken package. What's the problem of having the -version if you're not going to use it? Don't get me wrong.. I'm glad they fixed their mistake. I'm just a little dispapointed in the sneaky way they did it. Cheers. On Wed, 25 Aug 2004, Steve King wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wednesday 25 August 2004 21:32, Steve King wrote:
On Wednesday 25 August 2004 18:45, Ichaelmay Ewlynay Akeblay wrote:
SpamAssassin update is broken?
Under SuSE Professional 9.0 on x86
I notice that no update was issued for the perl-spamassassin package (Still 2.55-75) when the spamassassin package (now 2.64-4) was updated. Am I missing something or did SuSE just release a broken update?
They provided another update today. But I have had no problems with any of these updates, so perhaps your problem is caused by something else?
Steve
<blush> Just spotted you are using 9.0, and the update I am referring to is 9.1. But I suppose a 9.0 update can't be far off.
S. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFBLPlz94mqX5AIfgARAkKGAJwMKT9V4GnsvJIumgM64ZJe35JFxgCdFsJh SX2p7Xva5DOKH5LO7cIwevQ= =cr/6 -----END PGP SIGNATURE-----
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-----
/"\ Happiness Will Prevail!
Ichaelmay Ewlynay Akeblay wrote:
Interesting... used online update to check for new updates to spamassassin. It installed a new update to spamassassin... with the same version: 2.64-4.
They just missed perl-spamassassin with the update the first time, which broke it. No real need to increment the version number, but definitely a need to give the complete update.
Tsk tsk. Sloppy. They should have incremented the version of the RPM so it was clear that 2.64-4 was broken, and 2.64-5 or whatever was the new good package.
2.64.4 wasn't really a bad package, but they do have to be matched, i.e spamassassin and perl-spamassassin. ;-) -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
participants (4)
-
Danny Sauer -
Ichaelmay Ewlynay Akeblay -
Joe Morris (NTM) -
Steve King