Your message dated Sat, 17 Dec 2011 23:17:45 +0000
with message-id <[email protected]>
and subject line Bug#651827: fixed in resolvconf 1.63
has caused the Debian Bug report #651827,
regarding resolvconf: initscript of resolvconf 1.62 breaks setups using manual
configuration
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
651827: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651827
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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-
--- End Message ---
--- Begin Message ---
Source: resolvconf
Source-Version: 1.63
We believe that the bug you reported is fixed in the latest version of
resolvconf, which is due to be installed in the Debian FTP archive:
resolvconf_1.63.dsc
to main/r/resolvconf/resolvconf_1.63.dsc
resolvconf_1.63.tar.gz
to main/r/resolvconf/resolvconf_1.63.tar.gz
resolvconf_1.63_all.deb
to main/r/resolvconf/resolvconf_1.63_all.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Marco Nenciarini <[email protected]> (supplier of updated resolvconf package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Sat, 17 Dec 2011 23:25:04 +0100
Source: resolvconf
Binary: resolvconf
Architecture: source all
Version: 1.63
Distribution: unstable
Urgency: low
Maintainer: resolvconf maintainers <[email protected]>
Changed-By: Marco Nenciarini <[email protected]>
Description:
resolvconf - name server information handler
Closes: 651801 651803 651827
Changes:
resolvconf (1.63) unstable; urgency=low
.
[ Thomas Hood ]
* [a83fce3] Depend on a later version of the initscripts package
* [cfc8349] Use variable instead of hard-coded path for old run dir
in maintainer scripts, to help shrink the Ubuntu diff.
* [9921902] Update and improve resolvconf(8)
* [719dc9b] Run update on boot (Closes: #651801, #651827)
* [5fc985c] Don't trigger on reconfigure (Closes: #651803)
Checksums-Sha1:
60a3f2588c329a02092174a531f767845d16769b 1076 resolvconf_1.63.dsc
0fc6e9f33e14c890acb5d59b5bf2351158562976 77206 resolvconf_1.63.tar.gz
a397a07fbad4b63d423ad16fc0fda9217f85c5cd 67540 resolvconf_1.63_all.deb
Checksums-Sha256:
d75f1bd635c02a3f3cf5dfb3e6ef1f1ae02f5e45e08478b398efeda406e3cde6 1076
resolvconf_1.63.dsc
5299a5d7a44b8e09fca31fe246aa199cd6938195e597762c1cc97c1f9d93ad38 77206
resolvconf_1.63.tar.gz
e4be55ef6088649280fb5f12fe483c7d7d01796768f3dd1d4362c74f8b00ac0a 67540
resolvconf_1.63_all.deb
Files:
9a4363a0898b4ad8975904461a845535 1076 net optional resolvconf_1.63.dsc
4a62b7ce617518a5567c9e8c47fa7a41 77206 net optional resolvconf_1.63.tar.gz
c7814849083f8d6dc2ce7bd7def24813 67540 net optional resolvconf_1.63_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iEYEARECAAYFAk7tIFMACgkQaGRzDfCV5eQr4QCfRIZCNOlUZLDGvQdEDLSsJI9X
LesAoITv0CrMVxVh1WgmTlJIq7USLMuQ
=Slll
-----END PGP SIGNATURE-----
--- End Message ---
