[MASS-NMU] rebuild with new debhelper 13.10 / changes to dh_installinit and dh_installsystemd

[Michael Biebl]

Hi,

if just did a bunch for NMUs containing the changelog entry
"No source change upload to rebuild with debhelper 13.10."

In case you are wondering what this is about, please read on.




This created its own set of problems.






Apologies if this caused any confusion or disruption.

Regards,
Michael


[1] https://salsa.debian.org/debian/debhelper/-/merge_requests/90/

There were some recent changes in debhelper [2], specifically in dh_installinit and dh_installsystemd in how we handle removed but not purged packages that ship a SysV init script and systemd unit file(s). As SysV init scripts are conffiles, they are not removed unless the package is purged. This can have undesired side effects, so in the past we tried to work around that by generating maintscripts code via dh_installsystemd that masks the systemd unit files on remove. So we came up with a different solution: We remove the x-bit of the SysV init script via dh_installinit when a package is removed, but not purged, which allows us to get rid of masking/unmasking code that is generated via dh_installsystemd. For that, a rebuild of the package is necessary. Since architecture all packages can't be binNMUed, I made no-change source uploads of those packages that build an arch all package shipping a systemd unit file. The reason for that is, that we still need to keep some compat code around in debhelper until all packages have been rebuilt with the new debhelper version. As we intend to drop this compat code in trixie, I wanted to assure that those uploads happen in time for the release and didn't want to wait for maintainer uploads. If you are the maintainer of one of those packages, there is no debdiff you need to apply to your package and for all intents and purposes, you can ignore this NMU.

OpenPGP_signature
Description: OpenPGP digital signature