No disconnect initiated from server side
Bug #608418 reported by
Eduard Bloch
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| apt-cacher-ng (Debian) |
Fix Released
|
Unknown
|
|||
| apt-cacher-ng (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: apt-cacher-ng
Here comes a hint from apt-cacher-ng upstream... because of a programming mistake, the versions 0.4.8 and 0.4.9 fail to disconnect the client when the peer has set Connection:close flag but waits for server to do the first step.
The problem became exposed with the maintenance script, i.e. this problem blocks the execution of cron.daily. Therefore, it should be fixed ASAP.
Feel free to take latest Debian version (0.5*) or use the attached patch.
Sorry for inconvenience,
Eduard.
Revision history for this message
| Eduard Bloch (edi-gmx) wrote | #1 |
| tags: | added: patch |
Revision history for this message
| Rolf Leggewie (r0lf) wrote | #2 |
| Changed in apt-cacher-ng (Ubuntu): | |
| status: | New → Fix Released |
| Changed in apt-cacher-ng (Debian): | |
| status: | Unknown → Fix Released |
To post a comment you must log in.
Thank you for letting us know. lucid uses upstream 0.4.6 and Maverick has 0.5.x by now. Closing as fixed in Maverick. Lucid seems to be unaffected.