Easy to trigger 404/416 errors after recent security update
Bug #1382401 reported by
Michael Vogt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apt (Debian) |
Fix Released
|
Unknown
|
|||
apt (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Lucid |
Won't Fix
|
High
|
Unassigned | ||
Precise |
Fix Released
|
High
|
Unassigned |
Bug Description
[Impact]
The recent security update make it easy to trigger Debian bug https:/
[Test Case]
1 install latest apt from security
2 run sudo apt-get update
3 run sudo apt-get update again and ctrl somewhere in the middle
4 run sudo apt-get update again
5 verify that you get either 404 or 416 errors
6 install the updated version from prospoed
7 verify that sudo apt-get update works now
8 verify that steps 2-4 do not lead to a failure
Changed in apt (Ubuntu Lucid): | |
status: | New → In Progress |
importance: | Undecided → High |
Changed in apt (Ubuntu): | |
importance: | Undecided → High |
status: | New → Fix Released |
Changed in apt (Ubuntu Precise): | |
status: | New → In Progress |
importance: | Undecided → High |
tags: |
added: verification-needed-lucid removed: verification-needed |
description: | updated |
Changed in apt (Debian): | |
status: | Unknown → Fix Released |
description: | updated |
tags: | removed: removal-candidate |
To post a comment you must log in.
Hello Michael, or anyone else affected,
Accepted apt into precise-proposed. The package will build now and be available at http:// launchpad. net/ubuntu/ +source/ apt/0.8. 16~exp12ubuntu1 0.22 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed. In either case, details of your testing will help us make a better decision.
Further information regarding the verification process can be found at https:/ /wiki.ubuntu. com/QATeam/ PerformingSRUVe rification . Thank you in advance!