On Thu, 28 Dec 2023 06:27:44 +0100, Arnt wrote in message
<20231228062744.7c9c9f43@dvn>:

> On Wed, 27 Dec 2023 12:17:48 -0800, Syeed wrote in message
> <20231227121748.000031b0@???>:
>
> > On Mon, 18 Dec 2023 10:23:07 +0100
> > Martin Steigerwald <martin@???> wrote:
> >

> > > Martin Steigerwald - 18.12.23, 10:19:50 CET:    
> > > > dpkg: See
> > > > <https://wiki.debian.org/Teams/Dpkg/FAQ#broken-usrmerge>.   

> > >

> > > That FAQ entry is crazy: First (some) dpkg maintainers recommend
> > > undoing the usr-merge in case it has been done already...    

> >
> > What I find funny is that more thought and effort has probably been
> > put into creating an undo program than the actual merge itself:
> >
> > https://manpages.debian.org/bookworm/dpkg/dpkg-fsys-usrunmess.8.en.html
> >
>
>
> ..looks like something we should keep a fork of, and
> chk all packages with, e.g. alongside amprolla.
>
> ..remember, Debian is still run by the SystemD-Bois and
> has init, /usrmerge, /homeD etc plans that differ from
> our ideas of init etc freedoms.
>
>

..after I posted the above response, I ran these 3 amusing chks: ...
d44:~# whohas dpkg-fsys-usrunmess
d44:~# apt-cache search dpkg-fsys-usrunmess
...and got the expected responses, then I tried this: ;oD
dvn:~# man dpkg-fsys-usrunmess

--
..med vennlig hilsen = with Kind Regards from Arnt Karlsen
...with a number of polar bear hunters in his ancestry...
Scenarios always come in sets of three:
best case, worst case, and just in case.