On Wed, 26 Jun 2024 at 18:05:15 -0400, Reinhard Tartler wrote: > I imagine that one could whip up some kind of wrapper > that is building a container either from a tarball created via mmboostrap or > similar > using buildah, have it install all necessary build dependencies, and then use > podman to run the actual build
Yes, one could, and many have; but not (as far as I know) within the framework of sbuild, in a way that might be considered acceptable by the operators of our official buildds. > I also briefly started playing with debcraft, which I really like from a > usability perspective On Thu, 27 Jun 2024 at 10:52:27 +0200, Bastian Venthur wrote: > I had the idea to build my Debian packages in a clean docker container > instead of using cowbuilder etc for some time now. There are lots of options for doing this, some of which are listed in <https://wiki.debian.org/SystemBuildTools#Package_build_tools>. All of these have the same problem as cowbuilder, pbuilder, and any other solution that is not sbuild + schroot: it isn't (currently) what the production Debian buildds use, therefore it is entirely possible (perhaps even likely, depending on what packages you maintain) that your package will build successfully and pass tests in your own local builder, but then fail to build or fail tests on the buildds as a result of some quirk of how schroot sets up its chroots, which is a worse-than-RC bug making the package unreleasable. I'm sure that a better maintainer than me could avoid this source of stress by simply recognising situations that could cause a build failure before they happen, and ensuring that no mistakes are made; but unfortunately the only way I have found to be able to be somewhat confident that my packages will build successfully in the real Debian infrastructure, within my own limitations, is to replicate a real Debian buildd (to the best of my ability) and use that replica for my test-builds. smcv
