Public bug reported: Please remove src:sbuild-launchpad-chroot and bin:sbuild-launchpad- chroot (Architecture: all, universe) from stonking. This request is not limited to a particular architecture.
The package cannot produce a working chroot on any series since 24.04. Its schroot setup hook reads the mirror from the chroot's /etc/apt/sources.list, but that file has been a comment-only deb822 stub since noble, with the real sources in /etc/apt/sources.list.d/ubuntu.sources. The chroots Launchpad currently serves for noble, questing and stonking all have no "deb" line there. So "create" succeeds and every schroot session then fails at setup. On a clean stonking VM with sbuild-launchpad-chroot 0.20build1, schroot 1.6.13-8, sbuild 0.91.10ubuntu1: $ sudo sbuild-launchpad-chroot create -n stonking-amd64 -s stonking -a amd64 [stonking-amd64] Done creating $ sudo schroot -c stonking-amd64 -- true I: 01launchpad-chroot: [stonking-amd64] Processing config I: 01launchpad-chroot: [stonking-amd64] Already up to date. E: 90apt-sources: error: failed to read mirror from /var/run/schroot/mount/stonking-amd64-c7cafb48-651c-489e-8930-6c8df3e3d8bb/etc/apt/sources.list E: stonking-amd64-c7cafb48-651c-489e-8930-6c8df3e3d8bb: Chroot setup failed: stage=setup-start This affects all 20 aliases the tool registers, and their source: variants. Creating a chroot for the host's own architecture also takes the emulation code path. The tool's architecture table lists only cross- architecture pairs (amd64 -> i386, arm64 -> armhf) and there is no same- architecture check, so the lookup raises KeyError and the tool runs "apt-get install qemu-user-static" (bin/sbuild-launchpad-chroot:66-85). That package stopped being a real binary package after plucky. On stonking apt reports it as virtual, provided by qemu-user-binfmt and qemu-user-binfmt-hwe, and refuses to pick one: E: Package 'qemu-user-static' has no installation candidate The exit status is discarded, so this is not fatal, but a native amd64 chroot has been trying to install user-mode emulation it does not need. The package is Ubuntu-native and is not in Debian, so no sync-blocklist entry is needed. Its packaging repository is also its upstream, https://git.launchpad.net/~motu/ubuntu/+source/sbuild-launchpad-chroot, last commit 2022-11-10. The only upload since then is 0.20build1, a no- change mass rebuild. LP: #1996205 ("-proposed schroots not really using -proposed in >= Lunar") has had no reply since 2022-11-14. The Ubuntu development setup documentation dropped it on 2026-06-14 as unmaintained (ubuntu-project-docs commit f4446fb9) and recommends mk-sbuild instead. $ reverse-depends -r stonking sbuild-launchpad-chroot No reverse dependencies found $ reverse-depends -b -r stonking sbuild-launchpad-chroot No reverse dependencies found $ seeded-in-ubuntu sbuild-launchpad-chroot sbuild-launchpad-chroot's binaries are not seeded. Two comments in livecd-rootfs still mention this package, in live- build/buildd/hooks/00-mirror.binary ("for the benefit of sbuild- launchpad-chroot") and 50-buildd-tar.binary; there are no code references, only those comments. Neither is a functional dependency as launchpad-buildd needs the chroot-autobuild top-level directory regardless, and the public-mirror rewrite benefits any consumer of the published tarball. Those comments can be dropped in a follow-up MP after the removal. I've subscribed stgraber, the maintainer in debian/control, in case they want to object or take the package over. Suggested deadline: end of the 26.10 cycle. I have discussed this with my mentor Utkarsh Gupta, who is +1 on filing this. ** Affects: sbuild-launchpad-chroot (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2168886 Title: Please remove sbuild-launchpad-chroot from stonking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sbuild-launchpad-chroot/+bug/2168886/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
