Hello Luca. Thanks a lot for implementing this!
I'm going to answer to an old message of yours, because I think that things have changed a little bit since then. El 18/10/23 a las 19:17, Luca Boccassi escribió:
We can do an upload, but note that it won't have any effect on package builds, given the buildds use stable/oldstable - and this is not material for p-u, given the effect. [...]
That was the prudent thing to do, indeed, when the change affected all suites (oldstable, stable, testing, unstable, etc). However, I see that the latest git version has introduced a small change so that only trixie and above are affected: https://salsa.debian.org/installer-team/debootstrap/-/commit/3c71d6473f746cbe15a6fa1d1cf6950773c432ee which I agree that it makes sense to avoid breaking builds for bookworm and below. As a result, the new debootstrap behaviour currently in git would be no longer dangerous to have in bookworm (for chroots of trixie and above), and now I believe it would be not only suitable but highly beneficial for proposed-updates (to be included in a future point release). What would be required for that to happen? As Sebastian pointed out, this is the right time in the release cycle to do this kind of "potentially breaking changes", and compared to the usr-merge changes that have been already put in proposed-updates, I would say this one would be way less troublesome. Thanks.
