sa-update errors with 3.1.7
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - From this morning's log from three of our MX servers running SA 3.1.7. Does the channel for 3.1.7 have the wrong rules? config: configuration file /tmp/.spamassassin8654JTlidztmp/20_advance_fee.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_body_tests.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_compensate.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_dnsbl_tests.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_drugs.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_fake_helo_tests.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_head_tests.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_html_tests.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_meta_tests.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_net_tests.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_phrases.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_porn.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_uri_tests.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/23_bayes.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/72_active.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: warning: score set for non-existent rule
Re: sa-update errors with 3.1.7
Looks like Theo pushed through updates for the wrong version in the 3.1.x channel ;) Give it an hour or so and it should be fixed. By the way this is _totally_ harmless -- since the lint check failed, sa-update didn't make any change to the existing ruleset. --j. Steven Stern writes: - From this morning's log from three of our MX servers running SA 3.1.7. Does the channel for 3.1.7 have the wrong rules? config: configuration file /tmp/.spamassassin8654JTlidztmp/20_advance_fee.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_body_tests.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_compensate.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_dnsbl_tests.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_drugs.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_fake_helo_tests.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_head_tests.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_html_tests.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_meta_tests.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_net_tests.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_phrases.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_porn.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/20_uri_tests.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/23_bayes.cf requires version 3.002000 of SpamAssassin, but this is code version 3.001007. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Conf/Parser.pm line 345. config: configuration file /tmp/.spamassassin8654JTlidztmp/72_active.cf requires version 3.002000 of SpamAssassin, but this is code
Re: sa-update errors with 3.1.7
On Mon, Jan 01, 2007 at 07:11:03PM +, Justin Mason wrote: Looks like Theo pushed through updates for the wrong version in the 3.1.x channel ;) Give it an hour or so and it should be fixed. Um. No, I didn't. In fact, I upgraded my machines right after pushing the upgrade. Doing a little digging, it appears that a 3.2.0 update got pushed out with the same number and overwrote the 3.1 update. Speciically: $ head -1 /var/lib/spamassassin/3.001007/updates_spamassassin_org.cf # UPDATE version 491519 Looking at the updates dir: -r--r--r-- 1 updatesd other 118681 Jan 1 08:50 491519.tar.gz -r--r--r-- 1 updatesd other823 Jan 1 08:50 491519.tar.gz.asc -r--r--r-- 1 updatesd other 84 Jan 1 08:50 491519.tar.gz.sha1 Untarring that file does show a 3.2 update tree. Note the time on the file is 0850 GMT (0350 EST) on 1/1, and I pushed the update around 2030 EST on 12/31. So ... Bug in JM's code, not checking if there's already an update with that rev number? :P (looks like run_part2, lines 142-144 btw) -- Randomly Selected Tagline: I have a switch in my apartment that doesn't do anything. Every once in a while I turn it on and off. On and off. On and off. One day I got a call from a woman in France who said Cut it out! -- Steven Wright pgpKfUxW8wGyo.pgp Description: PGP signature
Re: sa-update errors with 3.1.7
On Tue, 2 Jan 2007 02:16:56 -0500, Theo Van Dinter [EMAIL PROTECTED] wrote: On Mon, Jan 01, 2007 at 07:11:03PM +, Justin Mason wrote: Looks like Theo pushed through updates for the wrong version in the 3.1.x channel ;) Give it an hour or so and it should be fixed. Um. No, I didn't. In fact, I upgraded my machines right after pushing the upgrade. Doing a little digging, it appears that a 3.2.0 update got pushed out with the same number and overwrote the 3.1 update. Speciically: $ head -1 /var/lib/spamassassin/3.001007/updates_spamassassin_org.cf # UPDATE version 491519 Looking at the updates dir: -r--r--r-- 1 updatesd other 118681 Jan 1 08:50 491519.tar.gz -r--r--r-- 1 updatesd other823 Jan 1 08:50 491519.tar.gz.asc -r--r--r-- 1 updatesd other 84 Jan 1 08:50 491519.tar.gz.sha1 Untarring that file does show a 3.2 update tree. Note the time on the file is 0850 GMT (0350 EST) on 1/1, and I pushed the update around 2030 EST on 12/31. So ... Bug in JM's code, not checking if there's already an update with that rev number? :P (looks like run_part2, lines 142-144 btw) It went in clean on all servers when I ran it this morning. I guess you fixed whatever the issue was? Kind regards Nigel
Re: sa-update errors with 3.1.7
On Tue, Jan 02, 2007 at 07:21:02AM +, Nigel Frankcom wrote: It went in clean on all servers when I ran it this morning. I guess you fixed whatever the issue was? I believe the order of what happened was: - I pushed the update on the evening of 12/31 - In the morning of 1/1, the automatic 3.2 update process pushed out an update with the same revision number, overwriting the 3.1 file - JM pushed out a new 3.1 update package So it's working now, but there was a time where the 3.1 channel pointed at a 3.2 file. Needless to say, the automatic update script needs at least a if [ -f ... ] snippet to avoid overwriting existing files. -- Randomly Selected Tagline: A CAT scan should take less time than a PET scan. For a CAT scan, they're only looking for one thing, whereas a PET scan could result in a lot of things. - Carl Princi, 2002/07/19 pgpJOrb0YrRZJ.pgp Description: PGP signature
