Unsuperseded binaries can't be deleted from PPAs

Bug #191892 reported by Celso Providelo
4
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Celso Providelo

Bug Description

Due to the source-driven approach adopted used in +delete-packages the users can't delete un-superseded binaries. A example is:

 * source foo_1.0 produces foo-bin_1.0 and foo-doc_1.0
 * source foo_1.1 produces foo-bin_1.1 and foo-extra_1.1

The PPA will end up in the following scenario:

 * source_1.0 SUPERSEDED
   * foo-bin_1.0 SUPERSEDED
   * foo-doc_1.0 PUBLISHED
 * source_1.1 PUBLISHED
   * foo-bin_1.1 PUBLISHED
   * foo-extra_1.1 PUBLISHED

So, foo-doc_1.0 binary will remain published and will hold all files related with foo_1.0 source.

Tags: lp-soyuz ppa ui
Revision history for this message
Celso Providelo (cprov) wrote :

The simplest solution is to allow deletions of every source not yet removed (or scheduled for removal) instead of only PUBLISHED ones.

Changed in soyuz:
assignee: nobody → cprov
importance: Undecided → High
milestone: none → 1.2.3
status: New → Triaged
Revision history for this message
Peter Antoniac (pan1nx) wrote :

Hi,
It is good that you put it as importance: High as it has an waterfall/domino effect in other links. For example, I ended up with a source package listed that was not existing...

Thanks,
Peter

Celso Providelo (cprov)
Changed in soyuz:
status: Triaged → In Progress
Revision history for this message
Celso Providelo (cprov) wrote :

RF 5795

Changed in soyuz:
status: In Progress → Fix Committed
Celso Providelo (cprov)
Changed in soyuz:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.