Initializing a distroseries when the parent has sources in the queues is refused

Bug #869277 reported by Julian Edwards
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Invalid
High
Raphaël Badin

Bug Description

bug 820452 was not quite fixed properly. When initialization checks the distroseries queues, it doesn't matter that the parent has sources there. I think binaries are checked properly, but sources get erroneously included too.

Tags: derivation
Changed in launchpad:
status: New → Triaged
importance: Undecided → High
tags: added: derivation
Revision history for this message
Ricardo Salveti (rsalveti) wrote :

This is quite important for Linaro, as it's almost impossible to create a Ubuntu derived series with current setup, as it requires both the New and Unapproved queue to be empty of source packages (and both Natty and Oneiric have quite a few packages at the Unapproved atm).

Raphaël Badin (rvb)
Changed in launchpad:
status: Triaged → In Progress
assignee: nobody → Raphaël Badin (rvb)
Revision history for this message
Raphaël Badin (rvb) wrote :

I tried to recreate this locally but in vain: it really seems that source packages are (as they should be) ignored by the check.
Can you please double check that no builds are present in the queue when you initialize the derived series and perhaps provide me with any additional information that could help me figure out where the problem is?

Raphaël Badin (rvb)
Changed in launchpad:
status: In Progress → Incomplete
Revision history for this message
Ricardo Salveti (rsalveti) wrote :

Just tried again and it worked just fine this time, so it could be that a binary package was hanging around, but I remember checking with bigjools at the time he created the bug.

The series is initializing now, guess I just have to wait :-)

Will close as Invalid for now, thanks for looking into this.

Changed in launchpad:
status: Incomplete → Invalid
Revision history for this message
Raphaël Badin (rvb) wrote :

Thanks for looking into this. My guess is that the queue was empty when you clicked the init button, but since the job takes a few minutes to start to run after that, there is time for a build to show up and make the init fail.

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.