Thanks for your update Artur! Flagging status correctly so that it is clear this can be fixed with a merge and what can be considered for an SRU later on.
** Also affects: init-system-helpers (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848861 Importance: Unknown Status: Unknown ** No longer affects: init-system-helpers (Debian) ** Also affects: ipmiutil (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848861 Importance: Unknown Status: Unknown ** Changed in: ipmiutil (Ubuntu) Status: Confirmed => Triaged ** Changed in: ipmiutil (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1651111 Title: invoke-rc.d starts disabled systemd service if there are init scripts Status in init-system-helpers package in Ubuntu: Confirmed Status in ipmiutil package in Ubuntu: Fix Committed Status in ipmiutil package in Debian: Unknown Bug description: ipmi-util failed to install on Ubuntu 16.10. https://bugs.launchpad.net/ubuntu/+source/ipmiutil/+bug/1639823 invoke-rc.d from init-system-helpers 1.29ubuntu3 performs check services is not disabled. ipmi_port.service is disabled and as a result invoke-rc.d doesn't try to start it and installation completed successfully. invoke-rc.d from init-system-helpers 1.45 has more complicated check. If systemd service (ipmi_port.service) is not enabled but there are init.d scripts with the same name (/etc/rc2.d/S01ipmi_port /etc/rc3.d/S01ipmi_port /etc/rc4.d/S01ipmi_port /etc/rc5.d/S01ipmi_port) then invoke-rc.d starts service. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1651111/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
