Launchpad itself

PPA package not cleared out after delete

Bug #310517 reported by Robie Basak
2
Affects Status Importance Assigned to Milestone
Launchpad itself
Won't Fix
High
Unassigned
Launchpad itself 2.2.1

Bug Description

See https://launchpad.net/~racb/+archive?field.name_filter=&field.status_filter=any

The deleted package in Intrepid is not being cleared out. Possibly related is that the recreated package is showing a failed build even though it is effectively built as it shares the binary with Gutsy and Hardy.

How I got to this point (to the best of my memory):

1. Uploaded pulseaudio to Intrepid
2. Renamed username
3. Bug #87326 bit me
4. Copied pulseaudio to Jaunty to try to trigger recreation of PPA archive (sources.list URL 404'd otherwise)
5. Deleted pulseaudio from Jaunty
6. Uploaded irda-mcp2150-dkms to Intrepid
7. Copied irda-mcp2150-dkms to Hardy (with build)
8. Found that although PPA archive URL exists, dists/intrepid/.../Packages didn't; dists/hardy/.../Packages did
9. Deleted irda-mcp2150-dkms from Intrepid (in order to copy it back to try and trigger creation again)
10. Copied irda-mcp2150-dkms to Gutsy (from Hardy)
11. Copied irda-mcp2150-dkms to Intrepid (from Hardy)

So now two instances of irda-mcp2150-dkms exist in Intrepid with the same version, it says that the version that is there has failed to build, and the deleted one is still there.

What I'm expecting: the deleted one should disappear and the build status for everything should say built OK.

Tags: lp-soyuz
Celso Providelo (cprov)
Changed in soyuz:
assignee: nobody → cprov
importance: Undecided → Critical
milestone: none → 2.2.1
status: New → In Progress
importance: Critical → High
status: In Progress → Triaged
Revision history for this message
Celso Providelo (cprov) wrote :

Robie,

It's a weird race condition, I admit.

PPA page is trying to communicate that irda-mcp2150-dkms_1.2 source (which is exactly the same upload across series) failed to build on intrepid, despite of the fact it had succeed in hardy and then was copied over.

It's odd, but we can't change the fact that you tried to build it in intrepid and it failed, then you copied the source to hardy (where it had satisfied dependencies) and it built, and a source version can only be built once within a archive.

I do understand that the UI is misleading, but the binaries from hardy are published in intrepid and gutsy, making the package installable. Everything will be clearer when you upload another version and wait it to build in the original targeted series before copying the results over.

Changed in soyuz:
status: Triaged → Incomplete
Revision history for this message
Robie Basak (racb) wrote :

Celso,

Thanks for looking at this for me.

I think the build for Intrepid failed because the build seemed to try to "apt-get update" my PPA, and that step failed because it couldn't find the Intrepid Release file (or Packages; I don't recall which). The build would have succeeded for Intrepid otherwise. The build log has been overwritten since when I retried the build later, so sorry I didn't make this clear.

That is - the build failed not because the package was broken when building against Intrepid, but because the PPA was broken.

Is this what you meant, or were you considering the package to be broken?

If you still consider this not to be a bug after reading this, then no problem.

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

Robie,

Right, I see your point, the original build failed due to the PPA renaming. That's fine, but it doesn't change the fact that at that point, you've copied it down to hardy and built it there. The first build wins, since a source can only be built once.

I'm inclined to think that if it wasn't the renaming issue, you wouldn't have had any problem. However that's not entirely true, a source could legitimately fail to build in series X, get copied to X+1 and build fine and then get copied back and work.

Summing up, the UI is odd but states the reality, source irda-mcp2150-dkms_1.2 wasn't built in intrepid, although one can install the binaries from hardy in intrepid (and it should work).

Changed in soyuz:
status: Incomplete → Won't Fix
Julian Edwards (julian-edwards)
Changed in soyuz:
assignee: cprov → nobody
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.