On 20 Dec 2018, at 18:11, Kevin A. McGrail wrote:
> Wouildn't an easier fix would be curl on the yesterday's update and
> sa-update from a file?
Well, yes. That would be easier and less error-prone...
Wouildn't an easier fix would be curl on the yesterday's update and
sa-update from a file?
--
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171
On Thu, Dec 20, 2018 at 5:56 PM Bill Cole <
sa-b
On 20 Dec 2018, at 17:04, Kevin A. McGrail wrote:
> So this will resolve with the masscheck tonight and subsequent rule build?
Yes. Also see my latest post to the Users list for an immediate workaround.
So this will resolve with the masscheck tonight and subsequent rule build?
--
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171
On Thu, Dec 20, 2018 at 4:58 PM Bill Cole <
sa-bugz-20080...@bil
Fixed.
It turns out that bug 7302 exists and I misinterpreted a response to the
immediate case as an actual fix for the underlying flaw. I have now
committed a real fix.
On 20 Dec 2018, at 16:14, Kevin A. McGrail wrote:
+1
--
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Cha
+1
--
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171
On Thu, Dec 20, 2018 at 4:04 PM Bill Cole <
sa-bugz-20080...@billmail.scconsult.com> wrote:
> On 20 Dec 2018, at 15:53, Bill Cole wrote
On 20 Dec 2018, at 15:53, Bill Cole wrote:
On 20 Dec 2018, at 14:25, Bill Cole wrote:
This caused a failure in the run_nightly script which apparently
doesn't prevent a broken update from being built and distributed.
I'm looking at run_nightly...
It's a problem in the 'make' step: a lint f
On 20 Dec 2018, at 14:25, Bill Cole wrote:
This caused a failure in the run_nightly script which apparently
doesn't prevent a broken update from being built and distributed.
I'm looking at run_nightly...
It's a problem in the 'make' step: a lint failure emits a nice obvious
error message:
On 20 Dec 2018, at 12:00, Kevin A. McGrail wrote:
Interesting...
Mea culpa. Sorta. My bit is fixed now.
See
http://svn.apache.org/viewvc/spamassassin/trunk/rulesrc/sandbox/billcole/24_mixed_es.cf?r1=1849420&r2=1849419&pathrev=1849420
This caused a failure in the run_nightly script which ap
Interesting...
-- Forwarded message -
From: Marcus Schopen
Date: Thu, Dec 20, 2018, 11:55
Subject: sa-update is broken on updates.spamassassin.org channel [was: Re:
config: warning: description exists for non-existent rule EXCUSE_24]
To:
Am Donnerstag, den 20.12.2018, 12:35 +01
+ promote_active_rules
+ pwd
/usr/local/spamassassin/automc/svn/trunk
+ /usr/bin/perl build/mkupdates/listpromotable
HTTP get: http://ruleqa.spamassassin.org/1-days-ago?xml=1
HTTP get: http://ruleqa.spamassassin.org/2-days-ago?xml=1
HTTP get: http://ruleqa.spamassassin.org/3-days-ago?xml=1
+ mv rul
11 matches
Mail list logo