[Bug 999337] Re: resolvconf(8): misleading description of dns-* options

[Launchpad Bug Tracker]

This bug was fixed in the package resolvconf - 1.67ubuntu1

---------------
resolvconf (1.67ubuntu1) quantal; urgency=low

  * Merge from Debian. Remaining changes:
    (LP: #994575, LP: #999337, LP: #1012355)
    - 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)
 -- Stephane Graber <stgraber at ubuntu.com>   Fri, 22 Jun 2012 17:29:50 -0400

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

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/999337

Title:
  resolvconf(8): misleading description of dns-* options

Status in “resolvconf” package in Ubuntu:
  Fix Released
Status in “resolvconf” source package in Quantal:
  Fix Released
Status in “resolvconf” package in Debian:
  Fix Released

Bug description:
  I noticed a minor discrepancy between the resolvconf documentation and
  "reality".

  On the one hand, the resolvconf(8) man page's discussion about the
  /etc/network/interfaces file says:

     For each other valid resolv.conf(5) configuration option,  you  can  include,
     in  the stanza, one line beginning with that option name with a dns- prefix.

  , and the resolv.conf(5) page lists the following configuration
  options: "nameserver", "domain", "search", "sortlist", and "options".

  On the other hand, the /etc/network/if-up.d/000resolvconf file
  actually only includes support for the first four of those
  configuration options -- that is, support for the "options" option is
  not included.

  (The resolvconf(8) and 000resolvconf files I'm looking at come from
  resolvconf 1.63ubuntu11 (Precise).)

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