Hi Mark, Quoting Mark Hindley (2026-03-27 20:49:05) > The conflicts was added to avoid interactions between systemd, initscripts > and insserv, however support for LSB initscripts in systemd has now been > removed and I find it unlikely that #1072562 or similar would still be issue > even if initscripts and insserv were installed on a systemd system. If I am > wrong in my analysis here, I would be happy to be pointed to a reproducer for > such an issue.
I asked Michael Biebl in #debian-devel again about this and the remaining problem seems to be that most packages still ship sysv init scripts alongside the systemd service files and that means that maintainer script code is generated which calls update-rc.d/innserv if present. I suggested to change the debhelper snippet which generates the relevant bit in maintainer scripts but Michael Biebl wasn't happy with that approach either. Jochen Sprickerhof brought up that update-rc.d/insserv could behave differently if DPKG_ROOT is set, but Michael Biebl replied that he has "no interest in touching this code and investigating all the corner cases". Remember, that this is just a convenience feature. I can use the $DPKG_ROOT method just fine from a clean chroot without systemd installed. I want to explore whether maybe this requirement can be dropped but I don't think too much energy and/or friction should be spent on that. I thought that just adding another small binary package would be the path of least resistance. Thanks! cheers, josch
signature.asc
Description: signature
