resolvconf (1.79ubuntu10) bionic; urgency=medium

  * Fix race of not injecting resolved config into resolvconf on LXD
    container boot. LP: #1763108

 -- Dimitri John Ledkov <xnox@ubuntu.com>  Thu, 12 Apr 2018 12:46:24 +0100

resolvconf (1.79ubuntu9) bionic; urgency=medium

  * Move resolvconf & resolved integration system units from src:systemd
    to src:resolvconf. Also use a different unit name, to avoid
    breaks/replaces.

 -- Dimitri John Ledkov <xnox@ubuntu.com>  Tue, 30 Jan 2018 14:17:27 +0000

resolvconf (1.79ubuntu8) artful; urgency=medium

  * Dereference /etc/resolf.conf when creating runtime configuration when
    migrating to resolvconf managed /etc/resolv.conf. The contents of
    /etc/resolv.conf (rather than the symlink target information) is
    needed in /run/resolvconf/resolv.conf and
    /run/resolvconf/interface/original.resolvconf during migration until
    resolvconf updates the config next. LP: #1713149

 -- Dimitri John Ledkov <xnox@ubuntu.com>  Tue, 29 Aug 2017 14:04:33 +0100

resolvconf (1.79ubuntu7) artful; urgency=medium

  * Drop ifupdown dependency.

 -- Dimitri John Ledkov <xnox@ubuntu.com>  Sat, 19 Aug 2017 20:19:26 +0100

resolvconf (1.79ubuntu6) artful; urgency=medium

  * Drop upstart system job.

 -- Dimitri John Ledkov <xnox@ubuntu.com>  Tue, 15 Aug 2017 04:05:05 +0100

resolvconf (1.79ubuntu5) artful; urgency=medium

  * debian/postrm debian/postinst: resurrect using readlink -m when
    checking if /etc/resolv.conf is managed by resolvconf or not. Change
    from 1.63ubuntu7 precise got lost somwhere along the way. Thus
    uninstalling resolvconf has been broken for a while.
  * debian/postrm: if resolved managed stub config is available, migrate
    to it upon resolvconf removal.

 -- Dimitri John Ledkov <xnox@ubuntu.com>  Fri, 21 Jul 2017 11:47:26 +0100

resolvconf (1.79ubuntu4) zesty; urgency=medium

  * debian/resolvconf.service: Add missing Wants=network-pre.target.

 -- Martin Pitt <martin.pitt@ubuntu.com>  Thu, 08 Dec 2016 10:21:12 +0100

resolvconf (1.79ubuntu3) zesty; urgency=medium

  * debian/resolvconf.service: resolvconf service must run before any of the
  possible network configuration services (ifupdown, networkd, NetworkManager)
  so use network-pre.target instead of service names. (LP: #1636912)

 -- Ryan Harper <ryan.harper@canonical.com>  Wed, 07 Dec 2016 03:30:55 -0600

resolvconf (1.79ubuntu2) zesty; urgency=medium

  * etc/resolvconf/resolv.conf.d/head: add comment about
    'systemd-resolve --status', since systemd-resolved is now in use in all
    but the most unusual configurations, and expert users should be given
    guidance where to find the actual nameservers for debugging purposes.
    LP: #1638836.

 -- Steve Langasek <steve.langasek@ubuntu.com>  Mon, 28 Nov 2016 15:39:18 -0800

resolvconf (1.79ubuntu1) yakkety; 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.

 -- Martin Pitt <martin.pitt@ubuntu.com>  Wed, 08 Jun 2016 12:08:23 +0200

# For older changelog entries, run 'apt-get changelog resolvconf'
