touch-packages team mailing list archive

[Alan <asbraithwaite+launchpad@xxxxxxxxx>]

Public bug reported:

The resolvconf package comes with /etc/dhcp/dhclient-enter-
hooks.d/resolvconf which convieniently undefines make_resolve_conf
(previously defined by dhclient-script) and calls resolvconf.

However, the hook checks if /etc/resolv.conf is a symlink even though
/sbin/resolvconf already handles this.

This is problematic because it never undefines the make_resolv_conf
function which dhclient-script defines itself.

For me, the expect behavior would be /etc/resolv.conf never changing if
resolvconf is installed and the file is not a symlink.

At the very least, I think this behavior should be documented in the man
pages for resolvconf.  Furthermore, debian does not implement this patch
and it exists starting in 12.04 until current.

As far as I can tell, there's absolutely no reason to check it twice if
resolvconf already implements it.

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

** Affects: resolvconf (Ubuntu)
     Importance: Undecided
         Status: New

-- 
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 not undefined

Status in “resolvconf” package in Ubuntu:
  New

Bug description:
  The resolvconf package comes with /etc/dhcp/dhclient-enter-
  hooks.d/resolvconf which convieniently undefines make_resolve_conf
  (previously defined by dhclient-script) and calls resolvconf.

  However, the hook checks if /etc/resolv.conf is a symlink even though
  /sbin/resolvconf already handles this.

  This is problematic because it never undefines the make_resolv_conf
  function which dhclient-script defines itself.

  For me, the expect behavior would be /etc/resolv.conf never changing
  if resolvconf is installed and the file is not a symlink.

  At the very least, I think this behavior should be documented in the
  man pages for resolvconf.  Furthermore, debian does not implement this
  patch and it exists starting in 12.04 until current.

  As far as I can tell, there's absolutely no reason to check it twice
  if resolvconf already implements it.

  It 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