Hey THomas, Thomas Hood [2015-06-01 8:35 -0000]: > Is there something we should do to silence those insserv warnings? > insserv: warning: current start runlevel(s) (2 3 4 5) of script `resolvconf' > overrides LSB defaults (S). > insserv: warning: current stop runlevel(s) (0 1 6) of script `resolvconf' > overrides LSB defaults (0 6).
It looks like your installation still has rc[2-5].d/ start symlinks for resolvconf? insserv won't override them on upgrade. So perhaps an older version of insserv used to call update-rc.d with specific runlevels and priorities, that was cleaned up later to use LSB headers, but they didn't match? For that case you need a postinst snippet to correct the links before the (debhelper generated) update-rc.d call, if you care. However, this is of course a bit brittle to get right in all corner cases.. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1453185 Title: resolvconf: updates are not enabled right after installation Status in resolvconf package in Ubuntu: Fix Released Bug description: Previously, updates were enabled in postinst script, but this enablement was removed in a favour of upstart service (https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/931335). This worked fine till the switch to systemd - no postinst action to activate resolvconf.service right after installation, one needs to reboot node in order to get updates enabled. Description: Ubuntu 15.04 Release: 15.04 resolvconf 1.76ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1453185/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
