Package: spamassassin Version: 3.4.0-1 Severity: normal Tags: upstream After today's upgrade in Sid to 3.4.0 it no longer can find a working channel. After trying several things I purged spamassassin entirely and then installed it again fresh. The problem persisted. I ran:
$ sa-update --debug --gpghomedir /var/lib/spamassassin/sa-update-keys channel: could not find working mirror, channel failed The problem is upstream. I am posting this bug to Debian so that others looking for the problem will have a log of it. The problem is: Feb 17 14:56:37.483 [7333] dbg: dns: 0.4.3.updates.spamassassin.org => 1567423, parsed as 1567423 ... Feb 17 14:56:37.577 [7333] dbg: channel: no mirror file /var/lib/spamassassin/3.004000/updates_spamassassin_org/MIRRORED.BY, will fetch it Feb 17 14:56:37.577 [7333] dbg: channel: DNS lookup on mirrors.updates.spamassassin.org Feb 17 14:56:37.968 [7333] dbg: http: url: http://spamassassin.apache.org/updates/MIRRORED.BY Feb 17 14:56:37.968 [7333] dbg: http: downloading to: /var/lib/spamassassin/3.004000/updates_spamassassin_org/MIRRORED.BY, new Feb 17 14:56:37.968 [7333] dbg: util: executable for curl was found at /usr/bin/curl Feb 17 14:56:37.968 [7333] dbg: http: /usr/bin/curl -s -L -O --remote-time -g --max-redirs 2 --connect-timeout 30 --max-time 300 --fail -o MIRRORED.BY -- http://spamassassin.apache.org/updates/MIRRORED.BY Feb 17 14:56:38.857 [7333] dbg: http: process [7335], exit status: 0 So far so good. Feb 17 14:56:38.859 [7333] dbg: http: /usr/bin/curl -s -L -O --remote-time -g --max-redirs 2 --connect-timeout 30 --max-time 300 --fail -o 1567423.tar.gz -- http://www.sa-update.pccc.com/1567423.tar.gz Feb 17 14:56:39.130 [7333] dbg: http: process [7337], exit status: 5632 ... channel: could not find working mirror, channel failed Checking manually finds: $ dig 0.4.3.updates.spamassassin.org +short txt "1567423" Previously for version 3.3.2 was: $ dig 2.3.3.updates.spamassassin.org +short txt "1568594" It appears that the upstream release isn't in sync with the mirrors. This has been reported and will hopefully be resolved soon. Downgrading to 3.3.2-7 in testing worked around the problem by using the previous version. apt-get install spamassassin=3.3.2-7 apt-mark hold spamassassin As soon as the upstream mirror issue is resolved then the package can be unheld and the upgrade should be fine. apt-mark unhold spamassassin apt-get upgrade Thank you for maintaining spamassassin in Debian! Bob -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
