On Thu, 2022-03-24 at 15:06 +0100, Ansgar wrote: > On Thu, 2022-03-24 at 14:49 +0100, Helmut Grohne wrote: > > On Thu, Mar 24, 2022 at 09:12:14AM +0100, Ansgar wrote: > > > Maybe it should be changed into a warning that non-merged-/usr > > > systems > > > will not be supported in the future. The `dpkg-fsys-usrunmess` > > > program > > > should probably also include a warning that it will convert the > > > system > > > into a state no longer supported by Debian in the future. > > > > What is supported is a bit subjective I fear. > > No, Helmut, it is not. We had that discussion often enough and in this > bug report you will find the following: > > +--- > > There are currently Debian 11 installations with both the merged-/usr > > and non-merged-/usr filesystem layouts. All of these installations > > should successfully upgrade via normal upgrade paths to a merged-/usr > > Debian 12. Only after the release of Debian 12 can packages assume > > that all installations will be merged-/usr. > +--- > > I'm not motivated to pretend the last years did not happen. > > Feel free to start a GR to override the tech ctte if you think that is > necessary. > > > > Either way, given related questions were already before the tech > > > ctte > > > several times it would be nice if this could be decided quickly to > > > avoid this becoming yet another energy drain (we had several > > > sufficiently long enough threads about this topic already). > > > > As much as I'd like to see this resolved quickly, I fear it is > > blocked on the lack of patches supporting merged-/usr. > > Given all new installations have been merged-/usr for years, it seems > to work sufficiently well for real-world use. And on top of new installations, old installations of Ubuntu upgrading to 21.10 and/or the soon-to-be-released 22.04 have been forcifully migrated too. They are not blocked, unsupported, or broken. -- Kind regards, Luca Boccassi
Attachment:
signature.asc
Description: This is a digitally signed message part