Death-row misbehave on binary collision
Bug #238826 reported by
Celso Providelo
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
When there is a binary checksum collision, cause by duplicated binary versions erroneously accepted (see bug 227184), the publisher correctlyrefuses to overwrite the file in disk.
However once the collision gets superseded or deleted, death-row misbehave and erroneously remove the disk file while marking the collision removed.
It's a major problem when the disk file is referenced by a released suite (the archive integrityis broken) and at this point the recovering process is very painfully (manually digging and restoring files from librarian), to not mention that the UI gets seriously screwed.
The only feasible solution is to extend death-row algorithm to verify the checksum of the file to be removed and skip disk removal on mismatches.
| Changed in soyuz: | |
| status: | New → Confirmed |
| Changed in soyuz: | |
| importance: | Undecided → Low |
| status: | Confirmed → Triaged |
To post a comment you must log in.
