[Resolvconf-devel] Bug#651827: resolvconf: initscript of resolvconf 1.62 breaks setups using manual configuration

[Michael Prokop]

Package: resolvconf
Version: 1.62
Severity: important


Situation:

# cat /etc/resolvconf/resolv.conf.d/base
nameserver 192.168.51.2

With resolvconf 1.62:

# /etc/init.d/resolvconf restart
 * Restarting resolvconf... done.
# cat /etc/resolv.conf
cat: /etc/resolv.conf: No such file or directory
# ls -la /etc/resolv.conf
lrwxrwxrwx 1 root root 31 Dec 12 12:34 /etc/resolv.conf -> /etc/resolvconf/run/resolv.conf
# ls -la /etc/resolvconf/run/resolv.conf
ls: cannot access /etc/resolvconf/run/resolv.conf: No such file or directory

But it works via reload:

# /etc/init.d/resolvconf reload
# cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.51.2


Same situation with resolvconf 1.61:

# /etc/init.d/resolvconf restart
 * Restarting resolvconf... done.
# cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.51.2


Manually invoking "resolvconf -u" with v1.62 fixes the issue.
initscript's restart action just does "resolvconf --enable-updates",
but the reload does "resolvconf -u".

resolvconf 1.61 seems to work as expected, looks like git commit
7cdfa73 broke this behaviour.

IMHO this qualifies as RC bug, but leaving the decision to the
maintainer.

regards,
-mika-