[Bug 1561829] [NEW] Sync apt-cacher-ng 0.9.1-1 (universe) from Debian unstable (main)

Launchpad Bug Tracker 1561829 at bugs.launchpad.net
Fri Mar 25 03:36:45 UTC 2016


You have been subscribed to a public bug by Unit 193 (unit193):

Please sync apt-cacher-ng 0.9.1-1 (universe) from Debian unstable (main)

Changelog entries since current xenial version 0.8.9-1:

apt-cacher-ng (0.9.1-1) unstable; urgency=low

  * New upstream version

 -- Eduard Bloch <blade at debian.org>  Sun, 28 Feb 2016 17:20:41 +0100

apt-cacher-ng (0.9.0-1) experimental; urgency=low

  * New upstream version

 -- Eduard Bloch <blade at debian.org>  Mon, 01 Feb 2016 19:50:49 +0100


Upstream changelog entries since current xenial version 0.8.9-1:

apt-cacher-ng (0.9.1) THE-DARK-NIGHT; urgency=low

  * FIX: correct human error message printing with recent glibc
  * FIX: corrected linking on systems that need additional libraries to be
    linked manually for socket IO while libwrap was not available
  * More file pattern changes for Ubuntu's do-release-upgrade tool
  * Better processing of filename sets in the "deletion" wizard (compressed
    parameter exchange for longer lists)
  * Database update

 -- Eduard Bloch <blade at debian.org>  Sun, 28 Feb 2016 17:17:43 +0100

apt-cacher-ng (0.9.0) MAXIMUM-OVERDRIVE; urgency=low

  * FIX: Ubuntu Installer's ReleaseNotes fetching was interpreted incorrectly
    forced redirection of ISP to its auth page. Now keeping the target page
    in doubt, just making sure it's reloaded next time.
  * More volatile regexp's to cover requests from Ubuntu Installer, including
    the link that it uses to examine state of the network connection
  * FIX: Replaced "unofficial" uint type with unsigned (should resolve build
    problems under FreeBSDs)

 -- Eduard Bloch <blade at debian.org>  Mon, 01 Feb 2016 19:48:10 +0100

** Affects: apt-cacher-ng (Ubuntu)
     Importance: Undecided
         Status: New

-- 
Sync apt-cacher-ng 0.9.1-1 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/1561829
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.



More information about the Ubuntu-sponsors mailing list