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
