Bug#841666: release-notes: recommend installing usrmerge on upgrade to stretch
Hi,
On Sat, 27 Feb 2021 at 22:38, Marco d'Itri <md@linux.it> wrote:
>
> On Feb 27, Paul Gevers <elbrus@debian.org> wrote:
>
> > > Due to systemd changes, currently usrmerge requires a reboot to complete.
> > > To lower support load on the community, as the usrmerge author I suggest
> > > that we wait to explicitly recommend users to install it until we will
> > > have implemented running it from the initramfs or some other workaround.
> > > Hence, for buster +1.
> > What's the current status on this? Should we recommend anything of this
> > kind already in the bullseye release notes? If so, can either of you
> > maybe propose some text?
> Actually this is not clear: me and other people attempted some more
> conversions and we have not been able to reproduce this anymore: the
> conversion just works as expected with no mid-conversion reboot needed.
> So we assumed that whatever the problem was with the systemd bind mounts
> it was "fixed" at some point.
>
> Cc'ing Dimitri John who did some related work on the Ubuntu side and
> maybe has more data.
Ubuntu has been installing systems usrmerged since Disco.
In the upcoming hirsute release, we also installing usrmerge package
as part of the upgrade.
But it means that one has to install bionic then upgrade to at least
focal, before upgrading to hirsute with this being performed.
It also means in Ubuntu during the upgrade people are booted with
245.4 systemd.
I have not managed to find any units that prevent ugprade to usrmerge so far.
Can you please advise which systemd unit options have broken the
upgrades in the past? And are they still in place, or have evolved to
be more specific / not problematic anymore?
--
Regards,
Dimitri.
Reply to: