sa-update errors with 3.1.7

2007-01-01 Thread Steven Stern
-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

Re: sa-update errors with 3.1.7

2007-01-01 Thread Justin Mason
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

Re: sa-update errors with 3.1.7

2007-01-01 Thread Theo Van Dinter
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

Re: sa-update errors with 3.1.7

2007-01-01 Thread Nigel Frankcom
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

Re: sa-update errors with 3.1.7

2007-01-01 Thread Theo Van Dinter
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