PPA does not delete old packages after new build

Bug #528459 reported by Christoph Reiter
24
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
High
Unassigned

Bug Description

A source package contains multiple packages, leading to multiple debs per upload/build.

If you remove a package from the control file, the new deb files overwrite the old ones, but the old ones that are not in the control file anymore don't get deleted.

They show up in the apt cache and there is no way to remove them in Launchpad.

Tags: lp-soyuz ppa
Christoph Reiter (lazka)
description: updated
Revision history for this message
Julian Edwards (julian-edwards) wrote :

Can you give an example of there this has happened please?

Changed in soyuz:
status: New → Incomplete
Revision history for this message
Christoph Reiter (lazka) wrote :

https://launchpad.net/~lazka/+archive/dumpingplace

Source: quodlibet, Removed package: quodlibet-ext
(only the karmic/lucid builds)

Changed in soyuz:
status: Incomplete → Confirmed
importance: Undecided → Medium
status: Confirmed → Triaged
Revision history for this message
Julian Edwards (julian-edwards) wrote :

Right - we have a way of deleting these in the Ubuntu archive but PPAs don't get processed. Thanks for confirming.

tags: added: ppa
Revision history for this message
Julian Edwards (julian-edwards) wrote :

Until this is fixed, a way to delete that binary is to upload a dummy source that supersedes it, then delete the source.

Changed in launchpad:
importance: Medium → High
Revision history for this message
William Grant (wgrant) wrote :

Nowadays you can also use the binary_package_publishing_history.requestDeletion API method to dispose of them.

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.