BPPH.supersede shouldn't ever supersede obsolete or deleted publications
Bug #653395 reported by
William Grant
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
High
|
Unassigned |
Bug Description
IPublishing.
While the idea behind this exception is sane (arch-indep binaries supersede each other atomically, so calling supersede() on a Superseded publication needs to be OK), it should ensure that the publication is Superseded. As it stands, it will mark a Deleted or Obsolete publication as Superseded -- but such a situation can only arise due to a bug, so it should crash and burn.
Related branches
lp://qastaging/~stevenk/launchpad/bpph-supersede
On hold
for merging
into
lp://qastaging/launchpad
- Deryck Hodge (community): Abstain
-
Diff: 50 lines (+20/-11)2 files modifiedlib/lp/soyuz/model/publishing.py (+11/-11)
lib/lp/soyuz/tests/test_publishing_models.py (+9/-0)
Changed in soyuz: | |
status: | New → Triaged |
importance: | Undecided → Medium |
tags: | added: soyuz-publisher |
tags: |
added: soyuz-publish removed: soyuz-publisher |
Changed in launchpad: | |
importance: | Medium → High |
tags: | added: trivial |
tags: | added: boobytrap tech-debt |
To post a comment you must log in.