On Wed, 18 Oct 2023 at 18:36, Johannes Schauer Marin Rodrigues <jo...@debian.org> wrote: > > Hi Luca, > > Quoting Luca Boccassi (2023-10-18 19:17:40) > > On Wed, 18 Oct 2023 at 18:04, Johannes Schauer Marin Rodrigues > > <jo...@debian.org> wrote: > > > > > > Hi, > > > > > > Quoting Santiago Vila (2023-10-12 17:56:04) > > > > Johannes has asked the RMs in this thread: > > > > > > > > https://lists.debian.org/debian-release/2023/10/msg00425.html > > > > > > > > if they are ready to consider the bugs as RC. I believe it would be > > > > better > > > > if we can make the bugs "factually" RC by uploading the fixed > > > > debootstrap first. > > > > > > I do not have a strong opinion on what should happen first but in that > > > thread, > > > Holger and Sam also support the idea to first upload debootstrap. > > > > 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. Of course it will affect local > > builds, in case they are done via debootstrap, from testing/unstable > > users. > > Yes, I'm aware of that. But I think having this in unstable/testing already > will help because several maintainers replied to the bugs saying they are > unable to reproduce it. Having debootstrap with this change in > unstable/testing > will make this a) much easier and b) convince people that they need to include > this change or otherwise their package will really FTBFS on the buildds with > the trixie release. > > And this should probably go without saying but just to make sure: if this > change causes any weird bugs, please message me so that I can supply a fix.
Thanks - I'll merge and do an upload over the weekend then
