Your message dated Sun, 20 Feb 2022 09:11:14 -0800
with message-id <[email protected]>
and subject line Re: Bug#1005964: Successfully updated to ruleset v. 1898205
has caused the Debian Bug report #1005964,
regarding spamassassin: sa-update fails due to Perl experimental feature in
regex
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1005964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005964
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: spamassassin
Version: 3.4.6-1
Severity: important
I got the following mail due to sa-update error via /etc/cron.daily:
------------------------------------------------------------
/etc/cron.daily/spamassassin:
config: invalid regexp for __URI_TRY_3LD
'm,^https?://(?:try(?!r\.codeschool)|start|get(?!\.adobe)|save|check(?!out)|act|compare|join|learn(?!ing)|request|visit(?!or|\.vermont)|my(?!sub|turbotax|news\.apple|a\.godaddy|account|support|build|blob)\w)[^.]*\.[^/]+\.(?<!list-manage\.)(?:com|net)\b,i':
Variable length lookbehind is experimental in regex; marked by <-- HERE in
m/(?i)^https?://(?:try(?!r\.codeschool)|start|get(?!\.adobe)|save|check(?!out)|act|compare|join|learn(?!ing)|request|visit(?!or|\.vermont)|my(?!sub|turbotax|news\.apple|a\.godaddy|account|support|build|blob)\w)[^.]*\.[^/]+\.(?<!list-manage\.)(?:com|net)\b
<-- HERE /
channel 'updates.spamassassin.org': lint check of update failed, channel failed
sa-update failed for unknown reasons
------------------------------------------------------------
Is the version of Perl too old in Debian 11 (bullseye)?
-- System Information:
Debian Release: 11.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-11-amd64 (SMP w/1 CPU thread)
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages spamassassin depends on:
ii adduser 3.118
ii curl 7.74.0-1.3+deb11u1
ii init-system-helpers 1.60
ii libhtml-parser-perl 3.75-1+b1
ii libhttp-date-perl 6.05-1
ii libmail-dkim-perl 1.20200907-1
ii libnet-dns-perl 1.29-1
ii libnetaddr-ip-perl 4.079+dfsg-1+b5
ii libsocket6-perl 0.29-1+b3
ii libsys-hostname-long-perl 1.5-2
ii libwww-perl 6.52-1
ii lsb-base 11.1.0
ii perl [libarchive-tar-perl] 5.32.1-4+deb11u2
Versions of packages spamassassin recommends:
ii gnupg 2.2.27-2
ii libio-socket-inet6-perl 2.72-2.1
ii libmail-spf-perl 2.9.0-5
ii perl [libsys-syslog-perl] 5.32.1-4+deb11u2
ii sa-compile 3.4.6-1
ii spamc 3.4.6-1
Versions of packages spamassassin suggests:
pn libbsd-resource-perl <none>
pn libdbi-perl <none>
pn libencode-detect-perl <none>
pn libgeoip2-perl <none>
ii libio-socket-ssl-perl 2.069-1
pn libnet-patricia-perl <none>
ii perl [libcompress-zlib-perl] 5.32.1-4+deb11u2
pn pyzor <none>
pn razor <none>
-- Configuration Files:
/etc/default/spamassassin changed [not included]
/etc/spamassassin/local.cf changed [not included]
/etc/spamassassin/v310.pre changed [not included]
-- no debconf information
--
Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- End Message ---
--- Begin Message ---
On Sun, Feb 20, 2022 at 12:47:16PM +0100, Andreas Schamanek wrote:
>
> Confirmation as requested from someone impacted on Debian Buster:
>
> My machines running spamassassin 3.4.4-1~bpo10+1 and 5.28.1-6+deb10u1
> successfully updated to ruleset version 1898205 this morning around 6:00
> UTC.
Thanks to all of you who have confirmed the fix.
As to what happened, the problem was never with sa-update itself, or
with any of the packaged content. It was not only Debian that was
impacted. When sa-update runs, it downloads updated rulesets from
services provided upstream. Upstream runs numerous compatibility and
quality checks before publishing updated content, but somehow in this
case an incompatible change made it through their automated tests. The
developers are still investigating exactly how this happened.
noah
--- End Message ---
