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. dpkg passes its tests under lxc, but fails under incus. The relevant part of the failure is (hopefully): 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, dpkg 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.
Hi! I'm assuming that you did not have the time to look into this further, so I'll start preparing one, but otherwise let me know if you were still working on this! I think this is an unrelated, expected failure from the test suite, and the root for this report is what Arnaud had reported earlier. As I mentioned to Arnaud above, I'd prefer to disable the specific tests in that scenario instead of requiring a special case for dpkg, and a more heavy method to run the tests. Thanks, Guillem
Hi! In the end I went with a trivial solution, requiring explicitly enabling these tests. Once the test suite gets rewritten it can be switched to be autodetected, but for now this should be good enough. I'm attaching what I ended up with. Tested on a sid chroot, with /usr/bin/mknod removed, to simulate "no mknod allowed". :) Thanks, Guillem