AssertionError: Duplicated ancestry

Bug #436453 reported by Loïc Minier
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
High
Unassigned

Bug Description

Hi

after uploading the cheetah package to karmic yesterday evening, where it went to Unapproved, it was accepted this morning into karmic and built on all arches. The ia64 build failed to upload:
https://launchpad.net/ubuntu/+source/cheetah/2.0.1-2ubuntu5/+build/1260567

and I got an email pointing that out and the traceback at http://launchpadlibrarian.net/32418658/p1MfAPijrn4Y5VGBnMoibBRd3SS.txt:
Traceback (most recent call last):
  File "/srv/launchpad.net/codelines/soyuz-production-rev-8513/lib/lp/archiveuploader/nascentupload.py", line 822, in do_accept
    self.storeObjectsInDatabase()
  File "/srv/launchpad.net/codelines/soyuz-production-rev-8513/lib/lp/archiveuploader/nascentupload.py", line 957, in storeObjectsInDatabase
    sourcepackagerelease = (
  File "/srv/launchpad.net/codelines/soyuz-production-rev-8513/lib/lp/archiveuploader/nascentuploadfile.py", line 737, in findSourcePackageRelease
    assert len(spphs) == 1, "Duplicated ancestry"
AssertionError: Duplicated ancestry

Cheers

Tags: lp-soyuz
Changed in soyuz:
status: New → Confirmed
status: Confirmed → Triaged
importance: Undecided → High
milestone: none → 3.1.10
Revision history for this message
Michael Bienia (geser) wrote :

This usually happens when a package gets promoted (or demoted) and a build happens at the same time (or more precisely before the next publisher run). From the look at the timestamps, I guess it's what happened here too.

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.