Your message dated Fri, 07 Aug 2026 07:49:13 +0000
with message-id <[email protected]>
and subject line Bug#1051957: fixed in mailman3 3.3.10-5
has caused the Debian Bug report #1051957,
regarding mailman3: autopkgtest is might be flaky at times
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.)
--
1051957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051957
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: mailman3
Version: 3.3.8-3.1
Severity: minor
Hi,
I had to retry a test two times to unblock systemd-cron migration.
The test alway fail at the very last step.
Example failure:
""""""""""""""""
>483s Created symlink /etc/systemd/system/multi
>484s Processing triggers for libc-bin (2.37-7) ...
>497s autopkgtest [06:49:27]: test mailman3-api: -----------------------]
>498s autopkgtest [06:49:28]: test mailman3-api: - - - - - - - - - - results -
>- - - - - - - - -
>498s mailman3-api FAIL non-zero exit status 7
Example OK:
"""""""""""
>489s Created symlink /etc/systemd/system/multi....
>490s Processing triggers for libc-bin (2.37-7) ...
>504s {"mailman_version": "GNU Mailman 3.3.8 (Tom Sawyer)",
"python_version": "3.11.5 (main, Aug 29 2023, 15:31:31) [GCC 13.2.0]",
"api_version": "3.1",
"self_link": "http://localhost:8001/3.1/system/versions";,
"http_etag": "\"2c68f151bb20bd0ba4086e11e7f98f20a28fdceb\""}
autopkgtest [19:03:55]: test mailman3-api: -----------------------]
>504s autopkgtest [19:03:55]: test mailman3-api: - - - - - - - - - - results -
>- - - - - - - - -
>504s mailman3-api PASS
Can you please have a look ?
The CI apt resolver will pick Vixie cron as prefered
cron-daemon; so these tests are totaly pointless
from systemd-cron side anyway...
but that would be a bug for the CI system.
> 31s The following additional packages will be installed:
> 31s cron cron-daemon-common
https://ci.debian.net/packages/m/mailman3/testing/i386/
3.3.8-3.1 2023-09-14 19:04:02 UTC systemd-cron/2.1.3-1
src:systemd-cron from unstable
8m 32s pass britney test log (53 KB) artifacts (3.54 KB)
3.3.8-3.1 2023-09-14 06:49:34 UTC systemd-cron/2.1.3-1
src:systemd-cron from unstable
8m 24s fail britney test log (51.8 KB) artifacts (3.56 KB)
3.3.8-3.1 2023-09-13 15:29:34 UTC systemd-cron/2.1.3-1
src:systemd-cron from unstable
8m 40s fail britney test log (52.5 KB) artifacts (3.56 KB)
3.3.8-3.1 2023-09-11 15:51:54 UTC systemd-cron/2.1.2-1
src:systemd-cron from unstable
8m 41s pass britney test log (53.2 KB) artifacts (3.55 KB
T H A N K S
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (501, 'testing'), (450, 'unstable'), (400, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.4.0-4-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_BE:fr
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: mailman3
Source-Version: 3.3.10-5
Done: Jordi Mallach <[email protected]>
We believe that the bug you reported is fixed in the latest version of
mailman3, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jordi Mallach <[email protected]> (supplier of updated mailman3 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Fri, 07 Aug 2026 09:06:47 +0200
Source: mailman3
Architecture: source
Version: 3.3.10-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Mailman Team <[email protected]>
Changed-By: Jordi Mallach <[email protected]>
Closes: 990336 1051957 1055449 1135067
Changes:
mailman3 (3.3.10-5) unstable; urgency=medium
.
* Add upstream patch to fix correct rotation of log files.
* logrotate: use systemctl, handle all log files and keep 14 days
(closes: #990336).
* Add postgresql to After and Wants in systemd service file (closes:
#1055449).
* Poll for the REST API instead of a fixed sleep to fix flaky autopkgtest
(closes: #1051957).
* Don't allow autopkgtest failures on riscv64 anymore.
* Avoid output to stderr during failed connection attempts in the curl loop.
* Use publicsuffix data from the Debian package (closes: #1135067).
* Mark upstream patches as Forwarded: not-needed
Checksums-Sha1:
6fc1fb259dc269572d903883bbaab74ba4827d6f 3123 mailman3_3.3.10-5.dsc
704131f1c8cb2361f7316c75a3ca628fdc5177a0 33860 mailman3_3.3.10-5.debian.tar.xz
60a58c4442a1c3a5dbaa1e3a5d266395860cab9f 11089
mailman3_3.3.10-5_amd64.buildinfo
Checksums-Sha256:
f5a054c5fa966e83d64784491d83aec3657e984d6ff6aa6f35803a3f23d4c33a 3123
mailman3_3.3.10-5.dsc
85ea14adacf66839a43ab0d51e19b8d6d50ef59118221f445eff27a5f04b5a08 33860
mailman3_3.3.10-5.debian.tar.xz
f3ab436b7467960d3de637513b14586ddbd2372ecff509d412911d365c222edd 11089
mailman3_3.3.10-5_amd64.buildinfo
Files:
433ce0ac409c775300da40fb5016dfa4 3123 mail optional mailman3_3.3.10-5.dsc
69948c2d465b41a1bc3278736d5c359d 33860 mail optional
mailman3_3.3.10-5.debian.tar.xz
0c82b1f36fc6020fe4dee2814538e7a3 11089 mail optional
mailman3_3.3.10-5_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE6BdUhsApKYN8KGoWJVAvb8vjywQFAmp1h6oACgkQJVAvb8vj
ywSWixAAqcViHSdgwVSVz14YOos8RHk530ishQsj6XqdW8VYaW0fRkEfq6WqSN56
wAq6ED03Pw3A7XgIdmHBLO3wId1vONB+PeOLLCp5KmrIpH1uqMl6vhOtA5ryMGxj
Pen1YNy53Deq1Fc/jNo81DXGX5oJ7Y0FueO5tRvAVO1hX6RN7hC0oD8k9xgu12ok
G5gy5j1hzrZAqJwRPZ0ISo0TKS092iv/F5aDHInaATm8Bn0VJgJC5hCo9Ct21CcD
Mf3+r5lC3yoCIovnHkiQ2qYn88nqMZpVq7OzQXetPa93wCoL51as8dbGspHu+F1Z
XiyV42YSrneWsL6EIyJSJM9Ysn7iI8lBJNC2Sv2jC8TslBoJ9fLaioheNJgQvuui
gu6c+0g6qMPjvY+7Fq0PkPBGhCHlSbjK2AV15583yUss1iqnyQK48sPRaMIBXg7q
oGP9c0X2QvMg9FI1UKYG1x0W05WUTjyHU6BzNt3RYrmmPFzafsoGHEQ16wB/Y3Q3
1oTlhEjeOd/Qd8IychmKS6ZNtNxudSAk5iEqzoJw9NnXXAJHzX99z99kTOifbPeU
D2mttuJxqqv7wDrJ5UvrpqynWeDV8OExTVtmumZgZSFYEONFOYsvaa9v8vYbEf8i
zmdYKLZqYrSxn08wH/JjlFzkEZz1JxwiwT/sqBLYXJEPRwg06lY=
=6F7d
-----END PGP SIGNATURE-----
pgpx8KKj2LzSu.pgp
Description: PGP signature
--- End Message ---
