On 2022-09-13 18:55 +0100, Tim Woodall wrote:
> On Tue, 13 Sep 2022, Greg Wooledge wrote:
>
>> On Tue, Sep 13, 2022 at 04:45:40PM +0100, Tim Woodall wrote:
>>> There's a package usr-is-merged that will stop usrmerge being installed
>>> with init-system-helpers (and so avoids bringing in its dependencies)
>>> but I don't see that available in bullseye.
>>>
>>> Most of my systems are already merged /usr and I'd prefer to avoid
>>> bringing in unnecessary packages when I upgrade to bookworm (which will
>>> be after bookworm becomes stable). Will the usr-is-merged package be
>>> added to bullseye before then?
>>
>> Added to bullseye? That sounds unlikely. New packages are almost never
>> *added* to a stable release.
>>
>> I can only guess that once we're in the bookworm freeze, some instructions
>> will start to appear for how users are expected to manage the transition.
>
> I might be misunderstanding but I was expecting bookworm to get the
> dependency init-system-helpers -> usrmerge imminently. Sid gets it, I
> think, on Thursday.
That is true.
> That's why I want usr-is-merged on my bullseye systems. I'll backport
> from bookworm.
You could, but why?
> Yes, on a migration you can add bookworm sources, apt-get install
> usr-is-merged, and then do the upgrade, but I'll probably forget, I've
> still got a couple of machines on buster to deal with first.
There seems to be some confusion here. To actually convert your system
to a merged /usr you need to install the usrmerge package which does the
work, and is already available in bullseye and buster. The
usr-is-merged package is just for convenience, and to ensure that the
system actually has a merged /usr (it will fail to install otherwise, so
if you have an unmerged /usr you need to install usrmerge first).
Cheers,
Sven
