This bug was fixed in the package apt-cacher-ng - 0.7.4-1ubuntu1
---------------
apt-cacher-ng (0.7.4-1ubuntu1) quantal; urgency=low
* Merge from Debian unstable. Remaining changes:
- debian/apt-cacher-ng.logrotate:
Comment out the "su" lines as this requires logrotate 3.8.1 which isn't
in Ubuntu yet.
- drop conflict on logrotate < 3.8.1
apt-cacher-ng (0.7.4-1) unstable; urgency=medium
* New upstream release
+ prevents endless looping in certain situations (LP: #999915)
+ more tolerance to unstable connections and behavior fix for conflicting
downloads in maintenance mode (closes: #672801)
* added a bug-script to present some instructions
apt-cacher-ng (0.7.3-1) unstable; urgency=low
* New upstream release
+ Fixes FTBFS (missing unistd.h include, closes: #667100)
+ option to disable Range/If-Range for volatile files (LP: #983128)
+ Fixes storage of HTTP header data in cached files under certain
circumstances (now really closes: #644959)
* Conflict with older logrotate not understanding "su" (closes: #662760)
* Process user/group is configurable via default file now (closes: #668421)
-- Julian Taylor <jtay...@ubuntu.com> Fri, 25 May 2012 23:41:35 +0200
** Changed in: apt-cacher-ng (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/999915
Title:
High CPU usage on broken request to apt-cacher-ng
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt-cacher-ng/+bug/999915/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
