Am 17.08.2018 um 15:24 schrieb Michael Biebl: > The problem is, that dh_installsystemd enables the service *after* a > start attempt has been made and > systemctl is-enabled checks for the state of the native service unit. > > With dh_systemd_enable/start, the enable part was before the start. > It's a bit like https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887904 > > The old code worked, as it checked the status of the SysV init script, > not the enabled state of the native service file.
We discussed this a couple of times already. I think dh_installsystemd is only fixable by making invoke-rc.d a nop (using --skip-native-systemd) and always generating start/stop/restart code in dh_installsystemd for service with a sysv+systemd service file. The sysv/systemd entanglement is imho not fixable if we have a single dh helper. With dh_systemd_enable+dh_systemd_start we could dodge that be moving the dh_systemd_enable part before the dh_installinit part. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
