Package: resolvconf
Version: 1.76.1
Severity: normal
Control: found -1 1.76
Control: found -1 1.75
Versions 1.75 through 1.76.1 of resolvconf assume the use of a recent
version of sysv-rc update-rc.d which does the right thing when "update-rc.d
resolvconf defaults" is run. The right thing is to create only the
following symlinks as instructed by the LSB header in the initscript.
/etc/rc0.d/K??resolvconf /etc/rc6.d/K??resolvconf
/etc/rcS.d/S??resolvconf
The wrong thing is to create the traditional default field of symlinks in
runlevels 1 through 5.
/etc/rc1.d/S??resolvconf /etc/rc2.d/S??resolvconf etc.
The wrong thing is bad because it causes "/etc/init.d/resolvconf start" to
be done late in the boot process (at entry to the multi-user runlevel).
That command clears resolvconf's database whereas the database should be
cleared only *before* any network interfaces are brought up.
I suspect that the dependency should be on sysv-rc 2.88dsf-42 or later.
Presumably that means having a Breaks sysv-rc (<< 2.88dsf-42).
Unfortunately, no dependency was declared on sysv-rc. So there is at the
very least a formal bug.
Although Jessie includes 2.88dsf-59, Wheezy includes only 2.88dsf-41+deb7u1
which allows for a scenario where resolvconf gets upgraded first and its
postinst runs the old update-rc.d. Whether or not this results in the Wrong
Thing being done requires investigation.
--
Thomas Hood
