On Tue, Oct 5, 2021 at 3:30 PM Otto Kekäläinen <o...@kekalainen.net> wrote: > > Hello! > > I noticed that Lintian has recently started erroring on > https://lintian.debian.org/tags/systemd-service-in-odd-location > > I can't find this requirement anywhere in the Debian Policy, e.g. > https://www.debian.org/doc/debian-policy/ch-opersys.html#starting-system-services > does not mention anything about systemd paths. > > Seems dh_systemd_enable still installs files into /lib/systemd/system/ > and I find it confusing that apparently Lintian errors on what > debhelper does by default. Please enlighten me on what I have missed.
Thanks Otto, I think it is right to bring this to more attention as I've seen various people and builds stumble over it already. Not sure what the general discussion/status on this is, but for myself I have tracked it down starting from one of my builds failing to this commit [1] that has to land into debhelper to resolve it. [1]: https://salsa.debian.org/debian/debhelper/-/commit/d70caa69c64b > So, which one of these paths should be used and why? > - /lib/systemd/system/ > - /usr/lib/systemd/system/ > > Thanks! > -- Christian Ehrhardt Staff Engineer, Ubuntu Server Canonical Ltd