* Adrian Bunk <b...@debian.org> [170120 19:57]: > Control: reopen -1 > > On Fri, Jan 20, 2017 at 12:42:38AM +0100, Christian Hofstaedtler wrote: > > Hi, > > > > * Andreas Beckmann <a...@debian.org> [170119 23:40]: > > > Selecting previously unselected package setserial. > > > (Reading database ... > > > (Reading database ... 4394 files and directories currently installed.) > > > Preparing to unpack .../setserial_2.17-49.1_amd64.deb ... > > > Unpacking setserial (2.17-49.1) ... > > > Setting up setserial (2.17-49.1) ... > > > removing the old setserial entry in the rcn.d directories > > > Update complete. > > > update-rc.d: warning: start and stop actions are no longer supported; > > > falling back to defaults > > > update-rc.d: warning: start and stop actions are no longer supported; > > > falling back to defaults > > > update-rc.d: warning: start and stop actions are no longer supported; > > > falling back to defaults > > > update-rc.d: warning: start and stop actions are no longer supported; > > > falling back to defaults > > > /etc/init.d/setserial: 35: .: Can't open /lib/lsb/init-functions > > > > It is believed that this is fixed with the newer > > init-system-helpers - the invoke-rc.d call should now be ignored in > > chroots that miss an init system. > > (And, if sysvinit is present, the missing file is present, or if > > systemd is present, setserial.service is used instead.) > > You are looking at the wrong line. > The update-rc.d warnings are non-fatal warnings. > > The error is the "Can't open /lib/lsb/init-functions" in the last line.
I was refering to that line. > (lintian also gives an error for this bug.) A very misguided one though. I'll leave this for someone else to test, there may very well be additional issues hiding in postinst. Best, -- christian hofstaedtler <z...@debian.org>
