You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current issue arises because the debian helper version we are using doesn't properly handle systemd files in the /usr/lib/ directory. Instead, it looks for files in the outdated /lib/ directory. Fixing this might require a re-write of the debian/rules using a newer debian helper version.
Description of the bug
ubuntu-pro-client
ships systemd units to/lib
on all releases, which are then diverted to/usr/lib
on focal onward.Expected behavior
ubuntu-pro-client
should ship systemd units to the correct location per ubuntu release./lib
on bionic and earlier,/usr/lib
on focal and later.Current behavior
ubuntu-pro-client
ships systemd units to/lib
on all releases, which are then diverted to/usr/lib
on focal onward.To Reproduce
dpkg -L
will show the diversion on any ubuntu machine focal onwardSystem information:
Additional context
At least on xenial, the units need to be delivered to
/lib
- if they are put in/usr/lib
, then they won't be correctly enabled and started.The text was updated successfully, but these errors were encountered: