AssertionError when copying packages ("Found more than one build candidate")

Bug #381239 reported by Ursula Junque
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Celso Providelo

Bug Description

As seen on OOPS-1243EC321:

  AssertionError: Found more than one build candidate: [1046233, 772896]. It possibly means we have a serious problem in out DB model, further investigation is required.

More in: OOPS-1243EC330, OOPS-1243ED329

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

Reproduced in OOPS-1249ED114 and

1. Copy only a source (from any archive) to a PPA (and optionally wait it to build)
2. Delete it
3. Repeat the copy procedure, this time including binaries

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

r8526 (devel)

Changed in soyuz:
status: In Progress → Fix Committed
Revision history for this message
Chris Clearwater (chrisclearwater) wrote :

Following this fix, instead of an OOPS, I now get a different error.

"The following source cannot be copied: boost1.35 1.35.0-8ubuntu1~pgquiles1 in hardy (binaries conflicting with the existing ones)"

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

Chris,

Cool! QA done, thank you very much.

Do you think it's clearer (and correct) now ?

Revision history for this message
Chris Clearwater (chrisclearwater) wrote :

I don't have any binary package "boost1.35" in my repository for it to conflict with, except something that previously failed to build. It is certainly clearer, but it is still problematic in that I can't import boost1.35 into my repository, which I need for another package.

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

Chris,

You did have binaries for boost1.35 in you repository once:

https://edge.launchpad.net/~spring/+archive/ppa?field.name_filter=boost&field.status_filter=any&field.series_filter=any

Copies will conflict with deleted versions as well, similar to what we do for uploads.

To solve you problem you can re-package the source with a new version, slower than the next mainline one, and wait for reconcile the versions in the next opportunity.

Revision history for this message
Chris Clearwater (chrisclearwater) wrote :

The problem is that I need debhelper7 to build boost1.35 and when I import debhelper7, it never gets published for some reason (I am told it is another known bug).

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

Exactly the same problem, you have already rebuilt the debhelper7 in your PPA:

https://edge.launchpad.net/~spring/+archive/ppa?field.name_filter=debhelper&field.status_filter=any&field.series_filter=any

It's not a bug anymore, it's design, you can only build source X once in your PPA and can only have one single instance of binary Y.

There is a clear issue with that, it does allow mistakes, once you've used a version, it's blacklisted forever. It requires a transitional upload with a version higher than the blacklisted one and lower than the next official package candidate.

Feel free to discuss this futher on lp-users ML.

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.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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