Database constraints do not prevent existence of two file references with the same name and difference sha1 for a single archive
Bug #804212 reported by
Stuart Bishop
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
High
|
Unassigned | ||
Bug Description
We apparently have lots of checks to ensure a file with the same name and different contents does not end up in an archive, conflicting with previously copied files.
We can enforce this in the database. This seems important given the care required with soyuz development at the moment to avoid making archives explode horribly.
| Changed in launchpad: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| summary: |
- Database constraint should block copy of a file with same name same - archive different sha1 + Database constraints do not prevent existence of two file references + with the same name and difference sha1 for a single archive |
| tags: | added: boobytrap |
To post a comment you must log in.
