Change logs for resolvconf source package in Experimental

resolvconf (1.51) experimental; urgency=low
  [ Thomas Hood ]  * Rename 'TRUNCATE_NAMESERVER_LIST_AFTER_127' to    'TRUNCATE_NAMESERVER_LIST_AFTER_LOOPBACK_ADDRESS' and make it    cause the nameserver list to be truncated also after an IPv6    loopback address. (Closes: #568820)  * Normalize contents of records -- i.e., strip out comments and    whitespace and shorten IPv6 nameserver addresses.  This makes    it easier to implement the change above.  * Add debian/test-normalization script to test the normalization    code.  * Update resolvconf/downup-interfaces template again.  Ready for    re-translation! -- Thomas Hood <email address hidden>  Tue, 03 May 2011 12:00:00 +0200

resolvconf (1.50) experimental; urgency=low
  [ Thomas Hood ]  * Also migrate non-symlinked directory /etc/resolvconf/run to    /run/resolvconf.  * Be interested in own trigger and enable updates only when triggered.    This could eliminate some superfluous updates on installation.    (Evidence that a package is allowed trigger itself:    http://lists.debian.org/debian-dpkg/2007/10/msg00175.html)  * Add section "Usage information for maintainers" to the README file    discussing the new trigger.  * Document the "original" file in resolvconf(8). (Closes: #414692)  * Improve markup of resolvconf(8). -- Thomas Hood <email address hidden>  Wed, 27 Apr 2011 12:00:00 +0200

resolvconf (1.49) experimental; urgency=low
  [ Thomas Hood ]  * Standardly keep run-time data in /run instead of /lib/init/rw;    migrate from /lib/init/rw to /run in the postinst. (Closes: #621503).    Thanks to Roger Leigh for his help.  * Create run-time data directories in the preinst instead of in the    postinst. (Closes: #551999, #563386).  (Do this in /run if that is    already already available, otherwise in /lib/init/rw, otherwise in    /etc/resolvconf.)  Now when other packages call resolvconf before    resolvconf's postinst runs, the data is not lost and no error     message is printed.  * If someone has run resolvconf while updates were disabled, update    when updates are enabled.  * Include the contents of the original resolv.conf file in the    database until the first reboot after installation.  The old behavior    was to omit these contents (unless link-tail-to-original was    selected) with the result that information was missing from    resolv.conf until ifdown-ifup cycles.  The new behavior is not     correct either, but should have less unpleasant consequences than    the old behavior.  * Update the debconf template that discusses the problem just described.    Whereas before it was recommended that the administrator down and up    network interfaces, it is now recommended that the administrator    reboot the system.  * Add da.po. (Closes: #623079)  Thanks to Joe Dalton.  * Run debconf-updatepo.  * Add Depends on initscripts >= 2.88dsf-13.3 which enables /run    in its postinst, ensuring that /run is available to our postinst.  * Activate the "resolvconf-event" trigger in postinst and in postrm    in order to trigger other packages to take notice of resolvconf    being installed (configured) or removed.  When resolvconf is installed    other packages possessing name server information should register it    with resolvconf. (Closes: #567059)  * Remove /etc/dhcp3/dhclient-enter-hooks.d/resolvconf which is obsolete;    remove it on purge and declare a Breaks: old versions of dhcp3-client    which used it. (Closes: #591022).  * Use dh_installifupdown to install ifupdown hook scripts and,    consequently, Build-Depend on newer debhelper.  * Update debian/compat to 8.  * Bump Standards-Version to 3.9.2.0.  * Tidy up all maintainer scripts.  [ Marco Nenciarini ]  * debian/control: updated Thomas Hood's email address. -- Marco Nenciarini <email address hidden>  Tue, 19 Apr 2011 22:30:30 +0200