On Mon, 2023-11-27 at 02:24 +0100, Lorenz via Dng wrote:
> >
>
> Let me try to better explain this:
> Mitigation M2 in https://subdivi.de/~helmut/dep17.html
> means that *every deb package* is about to ship files directly in
> /usr/bin instead of /bin, or directly in /usr/lib instead of /lib and
> so on.. An unmerged system will end up *without* /bin/sh,
> /sbin/init, /lib64/ld-linux-x86-64.so.2 (on amd64) just to make few
> relevant examples. At the end of the process (expected around March
> 2024) an unmerged system will have /bin, /lib, /sbin directories
> empty: but I doubt the system will be able to perform upgrades to
> that point. This move is *mandatory* for every Debian package, so
> until some derivative starts to support unmerged layout by forking
> 500/1000 packages (or by some other means) the unmerged layout will
> be broken.

Are you really sure about this? I've seen no reports so far about a
system being broken by an upgrade. I'll try this on a small qemu image
when time permits.
>
> Hope this helps to better understand the situation,
> Lorenzo

Again, is runit forked by Devuan or not?