Package: debhelper
Version: 13.4+nmu1
Followup-For: Bug #992469
I can confirm Samuel's analysis. When I tried debugging why building
e2fsprogs was causing a new lintian error:
E: e2fsprogs: systemd-service-file-outside-lib
usr/lib/systemd/system/e2scrub@.service
N:
E: systemd-service-file-outside-lib
N:
N: The package ships a systemd service file outside /lib/systemd/system/
N:
N: Systemd in Debian searches for unit files in /lib/systemd/system/ and
N: /etc/systemd/system. Notably, it does *not* look in
N: /usr/lib/systemd/system/ for service files.
N:
N: System administrators should have the possibility to overwrite a
N: service file (or parts of it, in newer systemd versions) by placing a
N: file in /etc/systemd/system, so the canonical location used for
N: service files is /lib/systemd/system/.
N:
N: Severity: error
N:
N: Check: systemd
N:
My service files were *originally* in debian/e2fsprogs/lib/systemd, as
they should have been:
<ty...@sid-chroot.cwcc> {/tmp/gbp/e2fsprogs-1.46.4}
1008% dh_install -v -pe2fsprogs
cp --reflink=auto -a debian/tmp/etc debian/e2fsprogs//
install -d debian/e2fsprogs//lib/systemd
cp --reflink=auto -a debian/tmp/lib/systemd/system
debian/e2fsprogs//lib/systemd/
...
But then dh_installsystemd is doing something cra-cra-crazy:
<ty...@sid-chroot.cwcc> {/tmp/gbp/e2fsprogs-1.46.4}
1009% dh_installsystemd -v
cp --reflink=auto -a debian/e2fsprogs/usr/lib/systemd/system
debian/e2fsprogs/lib/systemd
rm -fr debian/e2fsprogs/usr/lib/systemd
mv -f debian/e2fsprogs/lib/systemd debian/e2fsprogs/usr/lib/systemd
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
?!?
Please fix ASAP. This is going to block anyone from being able to build
and upload packages that contain systemd service files.
Many thanks,
- Ted
