On 5/1/19 7:59 AM, Kevin A. McGrail wrote:
Adding sysadmins@
Dave, I am guessing something got left in a previous run when svn
commit's failed. Can you or I delete a check out dir that is cruft?
I'm thinking a run went bad in february and couldn't commit. I figure
it should re-export, etc.?
On 1 May 2019, at 8:59, Kevin A. McGrail wrote:
Adding sysadmins@
Dave, I am guessing something got left in a previous run when svn
commit's failed. Can you or I delete a check out dir that is
cruft?
I'm thinking a run went bad in february and couldn't commit. I
figure
it should
Adding sysadmins@
Dave, I am guessing something got left in a previous run when svn
commit's failed. Can you or I delete a check out dir that is cruft?
I'm thinking a run went bad in february and couldn't commit. I figure
it should re-export, etc.?
Regards,KAM
On 5/1/2019 5:59 AM, Paul Stead
Looks like maybe sonic has lost a name server?
Forwarded Message
Subject:checkDNShosting.sh on sa-vm1.apache.org - 110 DNS hosting
issues found
Date: Wed, 1 May 2019 07:20:52 + (UTC)
From: root
Reply-To: sysadmins@spamassassin.apache.org
To:
Howdy!
As per -
https://lists.apache.org/thread.html/984ee3c26163e0281727256eabf0f29079a3fc053664416f58581ba0@%3Csysadmins.spamassassin.apache.org%3E
It looks as though the /tags commit is broken too -
http://svn.apache.org/viewvc/spamassassin/tags/?view=log
---8<---
+ promote_active_rules
+ pwd
+ /usr/bin/perl build/mkupdates/listpromotable
/usr/local/spamassassin/automc/svn/trunk
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
+ mv
spamassassin.org:
=
Registry Expiry Date: 2019-12-17T02:01:49Z
a.auth-ns.sonic.net:
-
..done
Results:
Matches: 110
Mis-matches: 0
