On Mon, 2022-07-18 at 13:03 -0700, Tianon Gravi wrote: > On Sun, 17 Jul 2022 at 06:21, Luca Boccassi <bluca@debian.org> wrote: > > That's because we will do all builds on unmerged-usr, until we are > > sure > > everything is switched over (and the autopkgtest/piuparts can also > > be > > turned over) in Bookworm+1, then there's nowhere left that runs > > them in > > unmerged-usr systems, and thus we can happily forget about it and > > spend > > the time on other issues. > > > > Wouldn't this work? Am I missing something? > > Hopefully I'm not too OT (please feel free to tell me if so! [1] > would > be an appropriate place to continue with more discussion on the > topic) > but another angle to this is the container images. > > [1]: > https://github.com/debuerreotype/docker-debian-artifacts/issues/131#issuecomment-900591334 > > They're currently *not* merged-/usr specifically because their usage > is in a gray area between user and build and we didn't want to break > the latter -- I'm guessing this means that for Bookworm, they should > technically stay in the "unsupported" configuration for the lifetime > of the release? /o\ > > (They're not used for any "official" package builds, but definitely > used for unofficial builds where the same concerns apply such as > Salsa > CI, although hopefully to a lesser extent.) My understanding is, only *till* the release, then they should be switched. But Simon please correct me if I'm wrong. -- Kind regards, Luca Boccassi
Attachment:
signature.asc
Description: This is a digitally signed message part