You are correct. I found that the filenames in the sha1 do not reflect
reality. Typically the files are really only used by sa-update so it
doesn't cause an issue.
--
Kevin A. McGrail
Asst. Treasurer & VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https:/
When investigating the recent report of my mirror returning bad tar.gz
files, I decided to try and validate the tar.gz files against the
tar.gz.sha1 files and I'm initially getting a lot of errors.
I first tried a sha1sum --check against each of the *.sha1 files (okay,
I rewrote the paths on t
On 03/19/2018 02:50 PM, Dave Warren wrote:
I'm going to keep a close eye on it for the next few days manually, and
then decide if adding automated validation is worthwhile or not.
I enjoy this kind of scripting challenge so I may do this anyway just so
we know if there are sa-update logs wit
I'm going to keep a close eye on it for the next few days manually, and
then decide if adding automated validation is worthwhile or not.
Could you (whoever is responsible) add me back to the mirrors list?
On 2018-03-19 13:36, Kevin A. McGrail wrote:
I would guess you caught it mid copy and it
I would guess you caught it mid copy and it arose because of the caching.
Just a guess but glad we know what's going on.
On Mon, Mar 19, 2018, 15:09 Dave Warren wrote:
> Howdy. I'm on this list.
>
> Okay, so this is a bit odd, it looks like the file 1827131.tar.gz was
> actually modified by rsyn
Howdy. I'm on this list.
Okay, so this is a bit odd, it looks like the file 1827131.tar.gz was
actually modified by rsync many hours after the initial write:
Date: Sun, 18 Mar 2018 02:36:30 -0600 (MDT)
.d..t.. ./
>f+ 1827131.tar.gz
>f+ 1827131.tar.gz.asc
>f+ 1827131
Fetching sa-update URLs from http://spamassassin.apache.org/updates/MIRRORED.BY
http://sa-update.dnswl.org/ (78.47.167.123): UP (CURRENT)
http://www.sa-update.pccc.com/ (69.171.29.39): UP (CURRENT)
http://sa-update.secnap.net/ (204.89.241.6): DOWN
http://sa-update.space-pro.be/ (176.28.55.20):
Fetching sa-update URLs from http://spamassassin.apache.org/updates/MIRRORED.BY
http://sa-update.dnswl.org/ (78.47.167.123): UP (CURRENT)
http://www.sa-update.pccc.com/ (69.171.29.39): UP (CURRENT)
http://sa-update.secnap.net/ (204.89.241.6): DOWN
http://sa-update.space-pro.be/ (176.28.55.20):
I found an email address in the SA archives from 2013. Hopefully this
makes it to him.
On 03/19/2018 08:33 AM, Dave Jones wrote:
Is Dave Warren on this list? If no response, does anyone have an old
email with his contact info so I can ask him how his rsync's are setup?
Dave
On 03/19/2018 0
Is Dave Warren on this list? If no response, does anyone have an old
email with his contact info so I can ask him how his rsync's are setup?
Dave
On 03/19/2018 08:26 AM, bugzilla-dae...@bugzilla.spamassassin.org wrote:
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7566
Dave Jones chang
Dave, any thoughts? This is odd!
--
Kevin A. McGrail
Asst. Treasurer & VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171
-- Forwarded message --
From:
Date: Mon, Mar 19, 2018 at 8:45 AM
Subjec
+ promote_active_rules
+ pwd
+ /usr/bin/perl build/mkupdates/listpromotable
/usr/local/spamassassin/automc/svn/trunk
HTTP get: http://ruleqa.spamassassin.org/1-days-ago?xml=1
HTTP get: http://ruleqa.spamassassin.org/2-days-ago?xml=1
day 2 contains a --net mass-check! offsetting by an extra day
Use
12 matches
Mail list logo
