Launchpad itself

[PPA] if a superseeding package is deleted the superseeded package is not reshown

Bug #192511 reported by reacocard
2
Affects Status Importance Assigned to Milestone
Launchpad itself
Won't Fix
Low
Celso Providelo

Bug Description

In my PPA, I noticed that if I upload a package that superseeds a previous package, and then remove that superseeding package from the PPA (for example, because it failed to build), the previous package is not re-shown under 'Published', which it should be since after removal of the superseeding package it is no longer superseeded. This also makes it harder for users to tell what packages the PPA actually offers.

Revision history for this message
Celso Providelo (cprov) wrote :

Sorry, but 'archive-deletion' does not work like you suggest. It simply removes the published version from the archive.

Re-publishing (recovering) the last published version is feasible but not yet implemented.

Personally I doubt if such feature is necessary at all, because both the superseded source and the last published binaries would remain in the archive until a new version is able to succesfully build new binaries.

Changed in launchpad:
assignee: nobody → cprov
importance: Undecided → Wishlist
milestone: none → 1.2.3
status: New → Incomplete
milestone: 1.2.3 → none
Celso Providelo (cprov)
Changed in soyuz:
milestone: none → 1.2.3
Revision history for this message
reacocard (reacocard) wrote :

While the packages do remain in the archive, that fact is not displayed on the PPA page unless you explicitly tell it to show superseeded packages. That is what I think needs to be fixed, though I admit this is a very minor bug.

Celso Providelo (cprov)
Changed in soyuz:
milestone: 1.2.3 → none
Revision history for this message
Celso Providelo (cprov) wrote :

Aren, superseded packages don't remain in the archive permanently, their deletion is scheduled and once all the references for the files are gone (which happens pretty quickly if you are nore using orig tarballs, for instance) the files will be purged from the repository pool.

So the PPA ui default filter (published sources) reflects exactly what is listed in the repository indexes. nothing more, nothing less.

You can resurrect a superseded source manually by using the 'copy packages' feature, simply copy the old source back to the same series in the same PPA.

I really don't thing re-publishing old versions automatically is a good thing to do.

Changed in soyuz:
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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