Hello Jochen, On Sun, 1 Dec 2024 at 09:46, Jochen Sprickerhof <jspri...@debian.org> wrote: > > Hi Samuel, > > * Samuel Henrique <samuel...@debian.org> [2024-12-01 09:15]: > >With the MR, we now enable sbuild to automatically create chroots for > >$codename-release, but this could be improved further. Would it be possible > >to > >have sbuild use the regular stable chroot and enable the following arguments > >whenever %r contains "-backports"? > >--build-dep-resolver=aptitude --extra-repository="deb > >http://deb.debian.org/debian bookworm-backports main" > > I think sbuild should pass all --extra-repository, > --extra-repository-key and --extra-package parameters to mmdebstrap, > piuparts and autopkgtest.
Do I understand correctly that you want a chroot specifically for backports, since you're saying it should be set on mmdebstrap instead of doing it at build-time and picking a regular $release chroot? Do you want to have, for example, both a stable and a stable-backports chroot, instead of having a single stable chroot? I forgot to mention in my previous email that the issue of duplicated chroots also affects builds for "*-security". And regarding the MR I opened with Johannes suggestion causes issues for builds of e.g.: UNRELEASED: https://salsa.debian.org/debian/sbuild/-/merge_requests/101 > "%r" => [ '--setup-hook=echo "deb http://deb.debian.org/debian %r main" > > "$1"/etc/apt/sources.list.d/%r.list' ], It tries to add repositories for UNRELEASED: > I: running --setup-hook in shell: sh -c 'echo "deb > http://deb.debian.org/debian UNRELEASED main" > "$1"/et Taking a step back and documenting the behavior I would like: * When building for UNRELEASED, the unstable chroot is chosen. * When building for $codename-backports, the $codename chroot is chosen and the backports repository and aptitude build-dep-resolver is chosen.* When building for $codename-security, the $codename chroot is chosen.* When building for experimenta, the unstable chroot is chosen. It does look like all of this can be achieved by a mix of chroot symlinks, user settings, and extra parameters when invoking sbuild (so that's feature parity with the schroot backend), I'm trying to understand if this can be achieved by default, without requiring any action on the user side. Cheers, -- Samuel Henrique <samueloph>Hello Jochen,
