This bug was fixed in the package apt-cacher-ng - 0.7.2-1ubuntu2.1
---
apt-cacher-ng (0.7.2-1ubuntu2.1) precise-proposed; urgency=low
[ Eduard Bloch ]
* Prevents endless looping in certain situations (LP: #15)
-- Chris J Arges chris.j.ar...@canonical.com Mon, 15 Apr 2013
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/15
Title:
High CPU usage on broken request to apt-cacher-ng
To manage
Debdiff looks good, ACK.
I've uploaded it to precise-proposed with a slight version change for
processing by the SRU team. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/15
Title:
High
Hello JorSol, or anyone else affected,
Accepted apt-cacher-ng into precise-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/apt-cacher-
ng/0.7.2-1ubuntu2.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
** Branch linked: lp:ubuntu/precise-proposed/apt-cacher-ng
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/15
Title:
High CPU usage on broken request to apt-cacher-ng
To manage notifications
** Also affects: apt-cacher-ng (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: apt-cacher-ng (Ubuntu Precise)
Assignee: (unassigned) = Chris J Arges (arges)
** Changed in: apt-cacher-ng (Ubuntu Precise)
Importance: Undecided = High
** Changed in:
Debdiff attached for precise SRU, test build here:
http://people.canonical.com/~arges/lp15/
** Patch added: fix_lp15_precise.debdiff
https://bugs.launchpad.net/ubuntu/+source/apt-cacher-ng/+bug/15/+attachment/3644827/+files/fix_lp15_precise.debdiff
** Description changed:
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
This is fixed in in the new upstream release 0.7.4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/15
Title:
High CPU usage on broken request to apt-cacher-ng
To manage notifications about this
** Branch linked: lp:debian/apt-cacher-ng
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/15
Title:
High CPU usage on broken request to apt-cacher-ng
To manage notifications about this bug go
I confirm that the patch works correctly... this should be pushed
upsteam and downstream to precise.
Thanks for your quick response Eduard.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/15
** Changed in: apt-cacher-ng (Ubuntu)
Importance: Undecided = High
** Changed in: apt-cacher-ng (Ubuntu)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/15
** Attachment added: Debug log showing the infinite loop.
https://bugs.launchpad.net/bugs/15/+attachment/3148253/+files/apt-cacher-ng.err.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The attached patch should prevent your daemon from looping. Why it
actually happened in first place is hard to tell, but with this change
the error message should be returned to client ASAP and you can check
again.
** Patch added: stop_looping.diff
The attachment stop_looping.diff of this bug report has been
identified as being a patch. The ubuntu-reviewers team has been
subscribed to the bug report so that they can review the patch. In the
event that this is in fact not a patch you can resolve this situation by
removing the tag 'patch'
15 matches
Mail list logo
