Source: debhelper Version: 13.24.2 Severity: serious Tags: trixie forky sid
Summary ----------- Neither of these dh_installsystemd --name=foo dh_installsystemduser --name=foo will fail the build when the expected filename doesn't exist; consequently, the Debian package silently does not include the expected systemd service. Test Case ------------ Let's use the debian-edu-install package since it is a simple package that builds quickly, Change the final line of debian/rules -dh_installsystemd -pdebian-edu-install --no-start --name=debian-edu-testsuite +dh_installsystemd -pdebian-edu-install --no-start --name=debian-edu-testsuite2 Build the package. The build completes successfully even though debian/debian-edu-install.debian-edu-testsuite2.service doesn't exist (debian/debian-edu-install.debian-edu-testsuite.service exists instead). The build log doesn't indicate a failure either, as these are the only 2 relevant lines emitted: dh_installsystemd -pdebian-edu-install --no-start --name=xdebian-edu-firstboot dh_installsystemd -pdebian-edu-install --no-start --name=debian-edu-testsuite2 What I Expect ------------------- I expect the build to fail because if a package has a rule to install a systemd service, that service needs to be installed. I am filing this bug as RC level initially. I noticed this issue with the lomiri-telephony-service package where the systemd user services were never installed and the package maintainer was unaware of this error. It meant the package did not work correctly, but that has been fixed with lomiri-telephony-service 0.6.2-4. If this bug fix causes one or more packages to FTBFS, that is a good thing since it exposes a bug (probably an RC bug) in that package's packaging. Other Info ------------- This bug might have been mentioned in https://bugs.debian.org/1051743 https://bugs.debian.org/974009 Thank you, Jeremy Bícha
