Your message dated Wed, 23 Sep 2026 13:18:59 +0000
with message-id <[email protected]>
and subject line Bug#1144776: fixed in cron 3.0pl1-210
has caused the Debian Bug report #1144776,
regarding cron: autopkgtest fails under incus-lxc: check-significant-header
FAIL non-zero exit status 1
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.)
--
1144776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1144776
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: cron
Version: 3.0pl1-209
Severity: important
Justification: fails autopkgtest on Debian CI infrastructure
Tags: forky sid
User: [email protected]
Usertags: lxc
Hi,
Debian CI is switching away from lxc containers in favor of incus Containers.
This is motivated by security concerns from us; incus is based on lxc, but
orchestrates containers substantially different: containers are not privileged
(so root in the container is not uid 0 outside of it, and incus imposes a
stricter isolation from the host system.
cron passes its tests under lxc, but fails under incus.
The relevant part of the failure is (hopefully):
> Setting up libgnutls30t64:amd64 (3.8.13-1) ...
> Setting up libpython3.14-stdlib:amd64 (3.14.6-1) ...
> Setting up guile-3.0-libs:amd64 (3.0.11-2+b1) ...
> Setting up expect (5.45.4-8) ...
> Setting up libpq5:amd64 (18.4-1+b2) ...
> Setting up libgnutls-dane0t64:amd64 (3.8.13-1) ...
> Setting up libpython3.14:amd64 (3.14.6-1) ...
> Setting up exim4-daemon-light (4.99.4-2+b1) ...
> Created symlink '/etc/systemd/system/multi-user.target.wants/exim4.service' →
> '/usr/lib/systemd/system/exim4.service'.
> Setting up exim4 (4.99.4-2) ...
> Setting up libmailutils9t64:amd64 (1:3.20-3+b2) ...
> Setting up mailutils (1:3.20-3+b2) ...
> update-alternatives: using /usr/bin/frm.mailutils to provide /usr/bin/frm
> (frm) in auto mode
> update-alternatives: using /usr/bin/from.mailutils to provide /usr/bin/from
> (from) in auto mode
> update-alternatives: using /usr/bin/messages.mailutils to provide
> /usr/bin/messages (messages) in auto mode
> update-alternatives: using /usr/bin/movemail.mailutils to provide
> /usr/bin/movemail (movemail) in auto mode
> update-alternatives: using /usr/bin/readmsg.mailutils to provide
> /usr/bin/readmsg (readmsg) in auto mode
> update-alternatives: using /usr/bin/dotlock.mailutils to provide
> /usr/bin/dotlock (dotlock) in auto mode
> update-alternatives: using /usr/bin/mail.mailutils to provide /usr/bin/mailx
> (mailx) in auto mode
> Setting up libmu-dbm9t64:amd64 (1:3.20-3+b2) ...
> Processing triggers for libc-bin (2.42-17) ...
> autopkgtest [21:07:24]: test check-significant-header:
> [-----------------------
> +----------------------------------------------------+
> | Here we are testing the patch |
> | features/Add-helpful-header-to-new-crontab.patch |
> +----------------------------------------------------+
> ================= adding user 'dummy' =====================
> ========= make user 'dummy' fill his crontab ==============
> autopkgtest [21:07:25]: test check-significant-header:
> -----------------------]
> autopkgtest [21:07:25]: test check-significant-header: - - - - - - - - - -
> results - - - - - - - - - -
> check-significant-header FAIL non-zero exit status 1
The full autokpgtest logs are available at:
https://ci.debian.net/experiments/8/regressions/
(please beware of pagination)
Common types of failure and suggested fixes are being documented at:
https://wiki.debian.org/ContinuousIntegration/LxcToIncus
Note that for the time being, cron is still being tested under lxc to
avoid disturbing its testing migration test results.
If you decide to add the `isolation-machine` restriction to get this package
tested under qemu, please mention that explicitly when closing this bug (it's
fine to do that only in the package changelog entry that closes the bug) so
that we can configure your package for qemu on ci.debian.net.
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: cron
Source-Version: 3.0pl1-210
Done: Georges Khaznadar <[email protected]>
We believe that the bug you reported is fixed in the latest version of
cron, 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.
Georges Khaznadar <[email protected]> (supplier of updated cron 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: Wed, 23 Sep 2026 15:04:59 +0200
Source: cron
Architecture: source
Version: 3.0pl1-210
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar <[email protected]>
Changed-By: Georges Khaznadar <[email protected]>
Closes: 1144776
Changes:
cron (3.0pl1-210) unstable; urgency=medium
.
* added a dependency on python3 in debian/tests/control, as the error in
tests run inside an icus container fail durinf a python script.
Maybe, Closes: #1144776
Checksums-Sha1:
0f91184ad3653125fa6ea59a36619345d584b838 2189 cron_3.0pl1-210.dsc
cb1bd6314b85e239e15c87f511a2b90faa9134d1 141968 cron_3.0pl1-210.debian.tar.xz
f70aae0c27f03d6b5f90f2f26b78e89082bb7f0b 6379 cron_3.0pl1-210_source.buildinfo
Checksums-Sha256:
d5332e123b3cdd11a070ad810d5d877bc4850a1e0d1dfdf0396070633c73095d 2189
cron_3.0pl1-210.dsc
08e9970b075c59f402d96f55226c64c282e58150208e73ad1cc6132c1f194bd0 141968
cron_3.0pl1-210.debian.tar.xz
a389788c284b4d70e4f9d89454153f0373f124eab8868841e845600c809363c3 6379
cron_3.0pl1-210_source.buildinfo
Files:
e1eccbb33683f82abd3ab474bd6a659f 2189 admin important cron_3.0pl1-210.dsc
1f6478183203012d847eec1d3fb64e4e 141968 admin important
cron_3.0pl1-210.debian.tar.xz
f6c83a241b44a86291543e949d62a4cc 6379 admin important
cron_3.0pl1-210_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJIBAEBCgAyFiEEM0CzZP9nFT+3zK6FHCgWkHE2rjkFAmqzz1sUHGdlb3JnZXNr
QGRlYmlhbi5vcmcACgkQHCgWkHE2rjnByA/8CN7l6kyzLeDzWr50OyEnNACsDzbc
2B+ViyqJWxOUk9xArDoNCspdMTU6K2IJcbFWEdk82GuN71ZVjNC+24W4mY9D/N4i
8ZPR+R7wdWhCDn8wXkgP8fLraASVkyQi90B28lsEF6zS3Qed4f4TTbofby5Nat17
yBGx1Nl+0qNNkP/kHm6+Vkm6JCfSl3mzUHfveID5TIEghRBB3226VZH0OSTGsI/6
8kOM4mB2AYcHaxJORZd9H/YgFHMaZBXz0TgBh0XX/yjhRR7OhTTaBlQEIH4qWa/z
CQhFmPruXTg/D7iT3ojGo4RJN5vfqoBxaAtfN9uEGXlcb0MnXS6vpU1acfbhkXmI
KoeB2AeNELWZkbO1uNE6+grxG0Vui2m1Wxq2TZIZlSGl4jgCZC/Wp6FGdwCfj5oA
Gs92MtuU5+IkoJMg/OE/A0j2hAFCqklMRwm44PdgGqN54Q4bc10SnJ79Ch7nF/Sb
5G5H6elVm+ujBMcoUCc9UB8PC72QQuJTubygbtFaFUC/2RzQwRWWT3NDep8E2OkD
PfKzQ08sPEL91RbRedIedZmtzEwocfsvrYWbir1O/gPsKmeUztGrlIM+1L/Al+0d
62EsPqIkp+dSkwGEvkj4YpNhBFPUuWBXEELiPWvTkCbO019L847eQIVMnyvbDz8q
ZaJSCPLKdXEOvKA=
=2k7x
-----END PGP SIGNATURE-----
pgpWDMZh0r6n7.pgp
Description: PGP signature
--- End Message ---
