Package "resolvconf"

Name: resolvconf


name server information handler

Latest version: 1.63ubuntu11
Release: precise (12.04)
Level: base
Repository: main
Homepage: http://alioth.debian.org/projects/resolvconf/


Save this URL for the latest version of "resolvconf": https://www.ubuntuupdates.org/resolvconf

Download "resolvconf"

Other versions of "resolvconf" in Precise

Repository Area Version
updates main 1.63ubuntu16


Version: 1.63ubuntu11 2012-03-29 23:06:51 UTC

resolvconf (1.63ubuntu11) precise; urgency=low

  * debian/config: Update regexp toallow multiple DNS servers on a single
    dns-nameservers line.

 -- Stéphane Graber Thu, 29 Mar 2012 16:38:31 -0400

Source diff to previous version

Version: 1.63ubuntu10 2012-03-17 22:10:51 UTC

resolvconf (1.63ubuntu10) precise; urgency=low

  * debian/config: handle 'inet6 dhcp' interfaces the same as 'inet dhcp'
    ones for detecting dynamic DNS information.
  * bin/list-records, etc/resolvconf/interface-order: cherry-pick upstream
    support for biosdevname-style interface names. Thanks, Thomas!
    LP: #949473.
  * man/resolvconf.8: point to the right directory for dhcp hooks.
    LP: #953257.

 -- Steve Langasek Sat, 17 Mar 2012 12:13:34 -0700

Source diff to previous version
949473 resolvconf is unaware of biosdevname NIC names
953257 resolvconf.8 manpage points to /etc/dhcp3 instead o...

Version: 1.63ubuntu9 2012-02-25 01:03:43 UTC

resolvconf (1.63ubuntu9) precise; urgency=low

  * debian/config: dns-nameservers lines are only valid if they take an ipv4
    or ipv6 value, and earlier bugs in netcfg may spit out lines with garbage
    values instead. If we find one of these on initial configuration, don't
    consider it an example of valid dynamically-provided DNS information.
    LP: #932275.

 -- Steve Langasek Fri, 24 Feb 2012 13:01:08 -0800

Source diff to previous version
932275 Bogus or no nameserver information written to /etc/network/interfaces

Version: 1.63ubuntu8 2012-02-20 20:03:45 UTC

resolvconf (1.63ubuntu8) precise; urgency=low

  * Use a post-stop script for disabling resolvconf, not a pre-stop script,
    since upstart seems to be silently ignoring pre-stop when there's no
    main process. LP: #933566.
  * debian/postinst: mkdir -p /run/resolvconf/interface again, just in case
    there's been a reboot between the preinst and postinst which would wipe
    out /run. May or may not address LP 933035.
  * 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.
  * when called with --enable-updates, ignore failures from the hooks.
    LP: #933723.

 -- Steve Langasek Mon, 20 Feb 2012 19:17:32 +0000

Source diff to previous version
933566 Stopping resolvconf doesn't disable updates
923685 Installing resolvconf causes loss of manually entered nameserver information in resolv.conf
933723 resolvconf creating bogus resolv.conf file

Version: 1.63ubuntu7 2012-02-02 21:03:17 UTC

resolvconf (1.63ubuntu7) precise; urgency=low

  [ Stéphane Graber ]
  * Revert change from 1.63ubuntu5 where /etc/resolv.conf would be linkified
    by the upstart/sysvinit job. This wasn't working as / wasn't necessarily
    writable at the time.
    Instead, make the link at package install time but make it a relative
    link which should take care of the chroot usecase where you want
    to copy /etc/resolv.conf from outside the chroot into the chroot.
    Detect old flag file (/var/lib/resolvconf/convert) and re-run the
    conversion code if it's present (to try and fix broken systems).
    Use readlink -m when checking the link's destination.
    (LP: #924836)

  [ Steve Langasek ]
  * Use readlink -m also in the postrm, to account for our relative links

 -- Stéphane Graber Thu, 02 Feb 2012 14:28:45 -0500

924836 network-manager does not tell plymouth it has started

About   -   Send Feedback to @ubuntu_updates