Re: [VOTE] SpamAssassin 3.1.2 release

2006-05-25 Thread Klaus Heinz
Theo Van Dinter wrote: Please test out these files and vote as to whether or not to release them as 3.1.2. Thanks. :) rules/v312.pre still contains: # This file was installed during the installation of SpamAssassin # 3.2.0 Apart from the warn: config: can not determine userstate dir

Re: [VOTE] SpamAssassin 3.1.2 release

2006-05-25 Thread Justin Mason
Theo Van Dinter writes: On Wed, May 24, 2006 at 11:35:18PM -0500, Michael Parker wrote: I fear that the warning is going to lead to a HUGE support headache. We either need to override the userstate dir for all the tests, add an additional possible userstate dir that will for sure exist or

[VOTE #2] SpamAssassin 3.1.2 release

2006-05-25 Thread Theo Van Dinter
Hi there, I have readied a new set of 3.1.2 files. They are available at: http://people.apache.org/~felicity/312/ Please test out these files and vote as to whether or not to release them as 3.1.2. Thanks. :) BTW: per ASF policies, only PMC member votes are binding for a release, but we

Re: [VOTE] SpamAssassin 3.1.2 release

2006-05-25 Thread Theo Van Dinter
On Thu, May 25, 2006 at 06:08:15PM +0100, Justin Mason wrote: fwiw, a long term fix would be option (b) -- tests should not be using the user's real userstate dir. Yeah, but that's not actually the issue. The warn() (now info()) is in the M::SA::get_and_create_userstate_dir() function which

Re: [VOTE] SpamAssassin 3.1.2 release

2006-05-25 Thread Justin Mason
Theo Van Dinter writes: On Thu, May 25, 2006 at 06:08:15PM +0100, Justin Mason wrote: fwiw, a long term fix would be option (b) -- tests should not be using the user's real userstate dir. Yeah, but that's not actually the issue. The warn() (now info()) is in the

Re: [VOTE #2] SpamAssassin 3.1.2 release

2006-05-25 Thread Radoslaw Zielinski
Theo Van Dinter [EMAIL PROTECTED] [25-05-2006 19:10]: I have readied a new set of 3.1.2 files. They are available at: [...] $ LANG=pl_PL prove -b t/gtube.t t/rule_names.t t/gtube.Not found: gtube = BODY: Generic Test for Unsolicited Bulk Email # Failed test 2 in

[Bug 4908] New: fix t/gtube.t to function in all languages, etc

2006-05-25 Thread bugzilla-daemon
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4908 Summary: fix t/gtube.t to function in all languages, etc Product: Spamassassin Version: 3.1.1 Platform: Other OS/Version: other Status: NEW Severity: normal

Re: [VOTE #2] SpamAssassin 3.1.2 release

2006-05-25 Thread Theo Van Dinter
On Thu, May 25, 2006 at 07:44:22PM +0200, Radoslaw Zielinski wrote: $ LANG=pl_PL prove -b t/gtube.t t/rule_names.t t/gtube.Not found: gtube = BODY: Generic Test for Unsolicited Bulk Email # Failed test 2 in t/SATest.pm at line 592 [...]

[Bug 4908] fix t/gtube.t to function in all languages, etc

2006-05-25 Thread bugzilla-daemon
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4908 [EMAIL PROTECTED] changed: What|Removed |Added Target Milestone|Undefined |3.2.0 --- Additional

Re: [VOTE #2] SpamAssassin 3.1.2 release

2006-05-25 Thread Michael Parker
Theo Van Dinter wrote: Hi there, I have readied a new set of 3.1.2 files. They are available at: http://people.apache.org/~felicity/312/ Please test out these files and vote as to whether or not to release them as 3.1.2. Thanks. :) BTW: per ASF policies, only PMC member votes are

Re: [VOTE #2] SpamAssassin 3.1.2 release

2006-05-25 Thread Justin Mason
+1 from me --j.

[Bug 4909] New: Some PL_* rules match their names, so t/rule_names.t fails

2006-05-25 Thread bugzilla-daemon
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4909 Summary: Some PL_* rules match their names, so t/rule_names.t fails Product: Spamassassin Version: 3.1.1 Platform: Other OS/Version: other Status: NEW

[Bug 4906] Uninitialized $score in PerMsgStatus::_handle_hit

2006-05-25 Thread bugzilla-daemon
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4906 --- Additional Comments From [EMAIL PROTECTED] 2006-05-26 00:55 --- I'm not completely clear about how often, or under what exact circumstances and config, you're seeing this but you're probably seeing bug 4179. The last