[ubuntu/raring-proposed] resolvconf 1.69ubuntu1 (Accepted)
Stephane Graber
stgraber at ubuntu.com
Fri Jan 18 16:55:33 UTC 2013
resolvconf (1.69ubuntu1) raring; urgency=low
* Merge from Debian. Remaining changes: (LP: #1085756)
- Make /etc/resolv.conf a relative symlink so that it works when
setting up chroots.
- Instead of throwing an error that aborts the upgrade when
/etc/resolv.conf is immutable, pop a debconf error message to let the
user know what's happening, then clear the immutable flag and continue
with the installation. LP: #989585.
- debian/config, debian/templates, debian/postinst: if we don't know that
/etc/resolv.conf was being dynamically managed before install (in at
least some cases), link the original contents of /etc/resolv.conf to
/etc/resolvconf/resolv.conf.d/tail so that any statically configured
nameservers aren't lost. LP: #923685.
- Use an upstart job instead of sysvinit script.
- Pre-Depend on the /run-providing version of initscripts instead of
depending, so that the preinst does the right thing when creating
/run/resolvconf/interfaces instead of getting clobbered later by a bind
mount on initscripts upgrade. LP: #922491.
- Completely drop the standard_run_subdirs_created helper function from
debian/postinst, since it serves no purpose here.
- postinst: Set resolvconf/linkify-resolvconf to false after initial
conversion, ensuring upgrades won't convert /etc/resolv.conf to
a symlink if the user manually converted it back to plain text.
(LP: #922677)
- Move the #DEBHELPER# token in debian/postinst to after the resolv.conf
symlink is set, so the init script can actually start (since it expects
/etc/resolv.conf to be a symlink).
- Eliminate all references to /etc/resolvconf/run. This should all be done
directly in /run, there is no reason to support making any of this
configurable with a symlink since we already have a versioned dependency
on the version of initscripts that introduces the /run transition.
- Also remove debian/triggers to avoid needlessly calling resolvconf's
postinst. (LP: #931335)
* Fix previous mis-merge of debian/postinst as well as the few other comments
from the bug report. (LP: #1085862)
resolvconf (1.69) unstable; urgency=low
* [276fc24] Bump Standards-Version; no changes required
* [6982da6] README: Name packages that clobber /etc/resolv.conf
* [4cb082a] README: Update
* [044e9a3] ip-up.d/000resolvconf: Do nothing if USEPEERDNS not set
* [d988a9e] if-up.d/000resolvconf: Silently (for now) accept option
name 'dns-nameserver' as a synonym for 'dns-nameservers' in
anticipation of support in ifupdown (no sooner than wheezy+1) for
duplicate options in a stanza, after which it will make sense to
specify multiple nameserver addresses on equally many
"dns-nameserver" lines
* [e0db2cb] Deal with obsolete conf files (Closes: #687507, #681623)
Date: Fri, 18 Jan 2013 11:52:10 -0500
Changed-By: Stéphane Graber <stgraber at ubuntu.com>
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
https://launchpad.net/ubuntu/raring/+source/resolvconf/1.69ubuntu1
-------------- next part --------------
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Fri, 18 Jan 2013 11:52:10 -0500
Source: resolvconf
Binary: resolvconf
Architecture: source
Version: 1.69ubuntu1
Distribution: raring
Urgency: low
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
Changed-By: Stéphane Graber <stgraber at ubuntu.com>
Description:
resolvconf - name server information handler
Closes: 681623 687507
Launchpad-Bugs-Fixed: 922491 922677 923685 931335 989585 1085756 1085862
Changes:
resolvconf (1.69ubuntu1) raring; urgency=low
.
* Merge from Debian. Remaining changes: (LP: #1085756)
- Make /etc/resolv.conf a relative symlink so that it works when
setting up chroots.
- Instead of throwing an error that aborts the upgrade when
/etc/resolv.conf is immutable, pop a debconf error message to let the
user know what's happening, then clear the immutable flag and continue
with the installation. LP: #989585.
- debian/config, debian/templates, debian/postinst: if we don't know that
/etc/resolv.conf was being dynamically managed before install (in at
least some cases), link the original contents of /etc/resolv.conf to
/etc/resolvconf/resolv.conf.d/tail so that any statically configured
nameservers aren't lost. LP: #923685.
- Use an upstart job instead of sysvinit script.
- Pre-Depend on the /run-providing version of initscripts instead of
depending, so that the preinst does the right thing when creating
/run/resolvconf/interfaces instead of getting clobbered later by a bind
mount on initscripts upgrade. LP: #922491.
- Completely drop the standard_run_subdirs_created helper function from
debian/postinst, since it serves no purpose here.
- postinst: Set resolvconf/linkify-resolvconf to false after initial
conversion, ensuring upgrades won't convert /etc/resolv.conf to
a symlink if the user manually converted it back to plain text.
(LP: #922677)
- Move the #DEBHELPER# token in debian/postinst to after the resolv.conf
symlink is set, so the init script can actually start (since it expects
/etc/resolv.conf to be a symlink).
- Eliminate all references to /etc/resolvconf/run. This should all be done
directly in /run, there is no reason to support making any of this
configurable with a symlink since we already have a versioned dependency
on the version of initscripts that introduces the /run transition.
- Also remove debian/triggers to avoid needlessly calling resolvconf's
postinst. (LP: #931335)
* Fix previous mis-merge of debian/postinst as well as the few other comments
from the bug report. (LP: #1085862)
.
resolvconf (1.69) unstable; urgency=low
.
* [276fc24] Bump Standards-Version; no changes required
* [6982da6] README: Name packages that clobber /etc/resolv.conf
* [4cb082a] README: Update
* [044e9a3] ip-up.d/000resolvconf: Do nothing if USEPEERDNS not set
* [d988a9e] if-up.d/000resolvconf: Silently (for now) accept option
name 'dns-nameserver' as a synonym for 'dns-nameservers' in
anticipation of support in ifupdown (no sooner than wheezy+1) for
duplicate options in a stanza, after which it will make sense to
specify multiple nameserver addresses on equally many
"dns-nameserver" lines
* [e0db2cb] Deal with obsolete conf files (Closes: #687507, #681623)
Checksums-Sha1:
67710ed4f42f8c4da28f8fc0177d2285416d8848 1825 resolvconf_1.69ubuntu1.dsc
667b45e6cfe832699d429e9a6a5ce696253a017a 84839 resolvconf_1.69ubuntu1.tar.gz
Checksums-Sha256:
20a9028a7256a3407bdcfcabf1e72d4b2cd3ce53d1561e92dfa1d94082e89e7d 1825 resolvconf_1.69ubuntu1.dsc
188ca2ebcf3ed286a8a6a4ba3abccea6a81ea43c8361e069195fdc54ead5f7f5 84839 resolvconf_1.69ubuntu1.tar.gz
Files:
ed55d734566cd57881ce67b370e4940f 1825 net optional resolvconf_1.69ubuntu1.dsc
66c16d2fe8651038b2d51c3d6b968746 84839 net optional resolvconf_1.69ubuntu1.tar.gz
Original-Maintainer: resolvconf maintainers <resolvconf-devel at lists.alioth.debian.org>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBCgAGBQJQ+X4LAAoJEMY4l01keS1n1gwP/13FnXS9XRJ+fCWbLmeS1GSw
8eW/MhNsmDrQnN++TIKN8uWU/JBpL9mfxysm8oRtC20fZz6SCr2moDI8qSBbRRUU
FsvqrEDd3O2d3ZgZhcsV/wtiLXP5KrPNFcTRIFCb84P21XHw662GVCmDQmc049tE
WitTC6hvgDsB0bBpCxYYya859UlVIW1bVa8FXMPhcrbSr+vQAKtzl1hN8ttxZ/Qm
Y/LNDh2u7nrkD82zFXyvAaWVjhLxIj6aiyVmxtnuvTmnIQ9ET/g5KG7JAVOe+E6O
4LuBsg/w7Z7NhYj6FiQ9EFMU4ILBfX/44495xwTvSc0MUeATgaeALo0TSEjSCuMO
WHHcog+Pet3be9LSN+p2zKlnDTBMB6WT2W2dolOjXLKVJKWDelcOoHFRF+qY6CjR
qwYqiz2m/pY3c233v95He3/2w2KxozY1s+Xh7Pm2nFiwT9U4bcjptnBq2hqzpKYs
BjAqHWyZb4bOdKXZxh2+jP3KIPiYeGf+Cofv8D1I6Mu1jINBYFel2hR4wolj8Mef
TzvDv7yJQNxFgrorK5q3q3/KTZ39WvTg4IEhIgMAsUtxjmZ9J+OejwE2so2jggFp
Jh6AGVtC1VKkrJnQpyPuCztaxY/kaFn9QqwnEvsjCSCcdHGgzmSKfGRQTHJeslI5
sdTmjCNAhKiXB9LB707p
=xqRn
-----END PGP SIGNATURE-----
More information about the Raring-changes
mailing list