On Wed, Jul 19, 2017 at 3:59 PM, Holger Levsen <hol...@layer-acht.org> wrote: > I dont even see how there would > be much delay, if we had the policy of say requiring a debian-cd upload > (to sid) with the changes made to create the stable upload.
Sid likely won't work here because both sid and testing may get ahead of the version used to build stable image. And even if sources match, packages won't because of the build environment. The backports repo looks more suitable, but again at some point you may want to see a backported testing version of utilities there, not patched stable. > And maybe (probably?) there is a case for the Stretch images where one tool wasnt uploaded yet. Seems like a bug to me too (if thats the case), but not really a reason for a flamewar nor calling out trolling. In the compilers development a failure to build itself is normally considered a critical compiler bug that blocks the release. Even though bootstrapping is not the main purpose of compiler existence. Similarly, a failure to produce an install image of debian on a system running the same version of debian sounds like a perfectly valid ground the delay the release. I guess when the next release approaches someone may want to set up nightly image builds of testing using clean testing environment and report bugs in the building process (if any) as RC. I know the debian-cd team already have weekly builds of testing, but I assume they run the patched toolchain from alioth repo. I'll see if I can arrange a self-build testing framework for x86 and amd64, but I'll definitely won't be able to cover all archs.
