[Bug 7986] spamd test fails when in directory with absolute pathname length greater than 50

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7986 Sidney Markowitz changed: What|Removed |Added Summary|spamd fails when in |spamd test fails when in

[Bug 7986] spamd fails when in directory with absolute pathname length greater than 50

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7986 --- Comment #6 from Sidney Markowitz --- sure -- You are receiving this mail because: You are the assignee for the bug.

New Pre-Release: 4.0.0-pre1 - Testers Needed

Hello Everyone, 4.0.0 pre-release 1 is now available at https://people.apache.org/~sidney/devel It was brought to my attention that it was too early to call the previous one a "release candidate" as we are pretty sure there are still bugs that will show up when this is tried out in serious produ

[Bug 7986] spamd fails when in directory with absolute pathname length greater than 50

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7986 --- Comment #5 from Henrik Krohns --- As it's your bug, can you rename all the mk_safe_tmpdir() to $workdir, if you find it acceptable. I need to run now for a bit.. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 7986] spamd fails when in directory with absolute pathname length greater than 50

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7986 --- Comment #4 from Henrik Krohns --- >From what I see the whole mk_safe_tmpdir() is useless spamc_cf.t:my $sockpath = mk_safe_tmpdir()."/spamd.sock"; spamd_client.t: my $sockpath = mk_safe_tmpdir()."/spamd.sock"; spamd_plugin.t:my $sockpa

[Bug 7986] spamd fails when in directory with absolute pathname length greater than 50

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7986 --- Comment #3 from Henrik Krohns --- And anyway, my $sockpath = mk_safe_tmpdir()."/spamd.sock"; This can safely be changed to my $sockpath = "$workdir/spamd.sock"; As $workdir is always a safe private directory, since my parallel testin

[Bug 7986] spamd fails when in directory with absolute pathname length greater than 50

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7986 Henrik Krohns changed: What|Removed |Added CC||apa...@hege.li --- Comment #2 from

[Bug 7986] spamd fails when in directory with absolute pathname length greater than 50

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7986 Sidney Markowitz changed: What|Removed |Added CC||sid...@sidney.com --- Comment #1

[Bug 7981] Remaining tasks for 4.0.0 release

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7981 --- Comment #2 from Sidney Markowitz --- It looks like no other recent commits are about anything that has to be finished before the pre-release, so I'll start building it. -- You are receiving this mail because: You are the assignee for t

[Bug 7981] Remaining tasks for 4.0.0 release

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7981 Henrik Krohns changed: What|Removed |Added CC||apa...@hege.li --- Comment #1 from

[Bug 7986] New: spamd fails when in directory with absolute pathname length greater than 50

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7986 Bug ID: 7986 Summary: spamd fails when in directory with absolute pathname length greater than 50 Product: Spamassassin Version: 4.0.0 Hardware: PC OS:

Getting ready for a 4.0.0 pre-release

It was pointed out to me that we should be calling the builds "pre-release", we are not yet far enough along for something called a "release candidate". With the build now at the point that make test passes all tests without requiring it be in a checked out svn trunk directory, and no open bugs

[Bug 7982] make test failures running from 4.0.0 install package

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7982 Sidney Markowitz changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[auto] bad sandbox rules report

HTTP get: https://ruleqa.spamassassin.org/1-days-ago?xml=1 HTTP get: https://ruleqa.spamassassin.org/2-days-ago?xml=1 HTTP get: https://ruleqa.spamassassin.org/3-days-ago?xml=1 Bad performing rules, from the past 3 night's mass-checks. (Note: 'net' rules will be listed as 'no hits' unless you set