I am slightly confused though because the update I had installed DID
have a 72_scores.cf. Though it went from 140~ lines to 60 lines. That
could be, as I was saying, me mixing 3.2 and 4.0 rule sets by accident.
On 6/2/2017 9:11 AM, Dave Jones wrote:
This issue was resolved yesterday. See my
On 6/2/2017 9:10 AM, Dave Jones wrote:
On the ruleqa list yesterday, John Hardin confirmed that buildbot was
running before to centrally process the full uploaded corpora. Sigh.
This is going to be difficult to figure out and get going again so we
need to focus on the distributed masscheck con
This issue was resolved yesterday. See my last email about QA'ing the
update file from last night then we should be ready to start updating
DNS again for sa-update.
Dave
On 06/02/2017 08:05 AM, Kevin A. McGrail wrote:
On 5/30/2017 8:46 PM, Dave Jones wrote:
Only in old/: 72_scores.cf
Only
On 06/02/2017 07:40 AM, Kevin A. McGrail wrote:
I think you are right. And that the system needs a run to create the
files for the scores on the new server.
I ran a manual "force" with 9 masscheck contributors last night so we
have a test file out there that I have asked the ruleqa list for h
On 5/30/2017 8:46 PM, Dave Jones wrote:
Only in old/: 72_scores.cf
Only in old/: languages
Only in old/: MIRRORED.BY
Only in old/: sa-update-pubkey.txt
Only in old/: STATISTICS-set0-72_scores.cf.txt
Only in old/: STATISTICS-set1-72_scores.cf.txt
Only in old/: STATISTICS-set2-72_scores.cf.txt
On
I think you are right. And that the system needs a run to create the
files for the scores on the new server.
On 5/30/2017 8:25 PM, Kevin A. McGrail wrote:
It's quite possible bb does update rule qa. Don't take what I say as
absolute... Will look at this more tomorrow.
Regards,
KAM
On May 3
File /usr/local/bin/updateDNS.disabled exists, not updating DNS.
File /usr/local/bin/updateDNS.disabled exists, not updating DNS.
