touch-packages team mailing list archive

[Launchpad Bug Tracker <1385010@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package resolvconf - 1.77ubuntu1

---------------
resolvconf (1.77ubuntu1) wily; urgency=medium

  * Merge with Debian unstable. Remaining Ubuntu changes:
    - debian/postinst: Make /etc/resolv.conf a relative symlink so that it
      works when setting up chroots.
    - 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.
  * Clean up some merge delta, thanks to Thomas Hood for reviewing!
    - Put back debian/triggers (should have been re-added as part of fixing
      LP #1453185)
    - Drop symlink check in dhclient-enter-hooks.d/resolvconf, to avoid
      dhclient overwriting /etc/resolv.conf when resolvconf is installed.
      (LP: #1385010)
    - resolvconf/link-tail-to-original debconf question again defaults to
      false; it's rather irrelevant as we install resolvconf by default.

resolvconf (1.77) unstable; urgency=low

  * [0781847] interface-order: match br ifaces at the same
    priority as eth ifaces (see LP#1446681)
  * Remove obsolete upgrade code
  * [00ad4bf] Override immutability attrib on /etc/resolv.conf
    if dnssec-trigger is installed. See #776778 for background.

 -- Martin Pitt <martin.pitt@xxxxxxxxxx>  Mon, 01 Jun 2015 08:42:43
+0200

** Changed in: resolvconf (Ubuntu)
       Status: Confirmed => Fix Released

-- 
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/1385010

Title:
  Unexpected behavior: make_resolv_conf is not undefined if
  /etc/resolv.conf is not a symlink

Status in resolvconf package in Ubuntu:
  Fix Released

Bug description:
  The resolvconf package comes with /etc/dhcp/dhclient-enter-
  hooks.d/resolvconf which, if /sbin/resolvconf is present, redefines
  the make_resolv_conf function (previously defined by dhclient-script)
  to send nameserver information to resolvconf instead of writing it
  directly to /etc/resolv.conf.

  However, the hook also checks if /etc/resolv.conf is a symlink. This
  is problematic because if /etc/resolv.conf is not a symlink then the
  script does not redefine make_resolv_conf() and so dhclient will
  overwrite /etc/resolv.conf when it configures an interface, even
  though the resolvconf package is installed.

  The behavior I would expect would be /etc/resolv.conf never changing
  if resolvconf is installed and /etc/resolv.conf is not a symlink.

  Debian implements the behavior I would expect.

  At the very least, I think that the different behavior in Ubuntu
  should be documented in the man pages for resolvconf.

  As far as I can tell, there's no reason to check for /etc/resolv.conf
  being a symlink when resolvconf itself already does that.

  The patch was introduced by: http://bazaar.launchpad.net/~ubuntu-
  branches/ubuntu/trusty/resolvconf/trusty/revision/32/etc/dhcp
  /dhclient-enter-hooks.d/resolvconf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1385010/+subscriptions