Re: Bug#992554: WARNING: dh_installsystemd is moving unit files to /usr/lib/systemd/system
On Fri, 20 Aug 2021 at 19:01:00 +0100, Luca Boccassi wrote:
> I can confirm that if you build in split-usr mode then the generators
> are looked for only in /lib:
>
> https://github.com/systemd/systemd/blob/v247/meson.build#L156
>
> (the systemgeneratordir meson variable is set from rootlibexecdir which
> is /lib/systemd/ in this case, this applies to other paths too)
>
> At this point this is very very unlikely to change upstream, given the
> legacy split mode is about to be dropped.
>
> However it would be trivial to patch it downstream, basically add the
> path here:
>
> https://github.com/systemd/systemd/blob/v247/src/basic/path-lookup.c#L800
Note that if we patch this downstream during the bookworm cycle, then
debhelper will have to add a version constraint to the affected packages,
to make sure partial upgrades pull in a suitable version of systemd.
Moving /lib/systemd/system/* to /usr/lib/systemd/system/ was only OK
because it was already supported by bullseye's systemd and
init-system-helpers, and we don't support skipping a release.
I said ${misc:Depends} before, but now I realise it would have to be a
new ${misc:Breaks} instead, otherwise packages like tor would pull in
systemd on systems that previously booted with sysvinit, and we'd have
a whole new flamewar.
Honestly, I'm not sure it's worth the bug risk of doing that - if
merged-/usr becomes required (as per the TC resolution) then everything
is going to end up physically located in /usr anyway, even if it's
canonically in /lib according to the dpkg database (and then we can move
everything into /usr at our leisure, during the bookworm+1 cycle).
smcv
Reply to: