Hi Paul, Sorry for the belated response. Reply follows in-line: Paul Boddie <paul@boddie.org.uk> writes:
sbuild-debian-developer-setup is the easiest way that I know to get a clean chroot:
https://manpages.debian.org/bookworm/sbuild-debian-developer-setup/sbuild-d ebian-developer-setup.1.en.html
Using sbuild will also do some minor fuzzing (eg: packages must declare all needed dependencies and must only write to safe locations during the package build)
Yes, I currently use gbp as follows:
gbp buildpackage --git-debian-branch=debian/master \ --git-upstream-tag='upstream/%(version)s' \ --git-builder=sbuild
I overlooked that sbuild might provide tools that are usable enough for more general activities, and I might even try this out myself!
:) Well, you figured it out enough to get work done, which is something that some people have complained is too hard! Yes, by default sbuild uses "schroot", which takes care of the creation and destruction of clean chroots, with session management, since 2005. If you prefer real containers or a fully virtualised build machine (with LXC), gbp can also uses these. I prefer schroots, because they don't eat into the RAM as much as real containers of VMs ;)
Thanks once again for the suggestions!
You're welcome! I wish you success, Nicholas