On Fri, 9 Jun 2023 at 10:53, Raphael Hertzog <hert...@debian.org> wrote: > > On Fri, 09 Jun 2023, Marco d'Itri wrote: > > On Jun 08, Raphael Hertzog <hert...@debian.org> wrote: > > > > > In the same spirit, I'd like to throw an idea... could we decide that > > > base-files is the first package to be configured as part of the bootstrap > > > protocol and change base-files maintainer's scripts into statically linked > > > executables so that they can work even if we don't have the library loader > > > on the ABI-compliant path? > > It could be even easier: base-files could be unpacked once without > > running the maintainer scripts and then "reinstalled" again later as > > usual. > > I think you are missing the point here, that only works if the package is > shipping the symlinks. And the idea is to not do this immediately because > it breaks debootstrap: if I understood correctly unpacking base-files > with the symlinks would fail if debootstrap had already pre-created those > symlinks (due to a -k option that we should get rid of in > /usr/share/debootstrap/scripts/debian-common). > > Hence the special maintainer script to create the required symlinks > without relying on /bin/sh or any dynamically linked executable.
Yes I think this will necessarily require another round of debootstrap changes once we've locked in on what we want to do, and go via the various -p-u queues. I'm pretty sure some buildds will still be stuck on Buster for example. I've done this last year and I'm happy to do it again once we have a plan. Kind regards, Luca Boccassi
