https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6838
--- Comment #5 from Martin von Wittich <martin.von.witt...@iserv.eu> ---
> What version of SA are you using?
We're using SpamAssassin 3.3.1, as provided by Debian stable:
iserv ~ # LANG=C apt-cache policy spamassassin
spamassassin:
Installed: 3.3.1-1
Candidate: 3.3.1-1
Version table:
3.3.2-2~bpo60+1 0
100 http://backports.debian.org/debian-backports/
squeeze-backports/main i386 Packages
*** 3.3.1-1 0
500 http://ftp.de.debian.org/debian/ squeeze/main i386 Packages
100 /var/lib/dpkg/status
> Does the same sa-update instance through a 404 error and then go onto the
> next mirror or are you saying you have to run it again?
That's a good question... I don't run it manually, I just see a cron error
message almost every day (exactly the one that Patrice posted) and so I assumed
that it failed.
> This sounds like a dupe of 6761 and in short, sa-update is designed to have
> some mirrors out of sync and it should try other servers.
I've looked into the sa-update code and it does seem to work exactly as you
describe :)
I think it is very probable then that the update actually works fine every day,
it just prints this confusing error message when it encounters the broken
mirror. Maybe it should only print the error message for a failed mirror when
all mirrors have failed?
--
You are receiving this mail because:
You are the assignee for the bug.
