El 2/1/23 a las 12:04, Bernhard Schmidt escribió:
Both the official buildds and schroots created using the documented sbuild-createchroot then apparently do not follow recommended procedure?
Yes, exactly. There is a bug in debootstrap asking for such required-but-not-build-essential packages not to be installed by default. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837060 Apparently, they have not agreed about the way to fix this. Some people suggest that debootstrap explicitly should not install those packages. Others suggest that debootstrap keeps installing all required packages not matter what, and instead we downgrade those packages to important. In the meantime, it's 2023 and I still have to explain that priority required does not imply build-essential. Believe me that this is also odd for me.
I have no problem fixing this up in unstable, but I think this does not warrant a stable update.
That would be unfortunate, as it means we will probably never have a stable release without FTBFS bugs. I have rebuilt the entire bullseye archive from scratch, and I'm reporting every FTBFS bug I find, because "packages in stable must build in stable". This is not only Policy but also Release Policy, i.e. something that our users should take for granted because we promised it as a release goal. The bugs I find are very diverse and in most cases they have been already reported in unstable and forgotten. There are also bugs which happen in bookworm but had not been reported yet, like this one. Since backporting those kind of bugs is completely trivial, I'm still aiming at having a stable distribution which is free from FTBFS bugs (of any kind). You are of course free not to help me in my goal, but it would help immensely if every maintainer ensured that their own packages are free from FTBFS bugs in stable. Thanks.
