* Samuel Henrique <samuel...@debian.org> [2024-12-01 10:37]:
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 consider chroots a temporary setup and no longer save them on disk. Given that mmdebstrap --variant=apt with apt-cacher-ng takes 6 seconds I configured sbuild, piuparts and autopkgtest to generate them on the fly. I think we should consider them completely internal to sbuild in future and generate a chroot with all build dependencies but without apt (unless specified) for every build. This would also simplify testing modified essential packages.

For the $unshare_mmdebstrap_keep_tarball case I think the question is how to name the file. I don't have a good proposal here and would leave it to those who want that option.

(yeah, cache invalidation and naming things)

Cheers Jochen

Attachment: signature.asc
Description: PGP signature

Reply via email to