Launchpad will not do initial mirror of a branch that's the development focus of a project

Bug #297448 reported by Jonathan Lange
4
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Jonathan Lange

Bug Description

If a branch is the development focus of a project and hasn't been mirrored yet, then the puller will erroneously try to stack it on itself. When it finds that the branch isn't there, it will defer the mirroring, anticipating that the development focus will eventually appear.

There are a couple of problems here, but the main one can be solved by not trying to stack branches on themselves.

Jonathan Lange (jml)
Changed in launchpad-bazaar:
importance: Undecided → Critical
milestone: none → 2.1.11
status: New → Triaged
Revision history for this message
Diogo Matsubara (matsubara) wrote :

Discussed today in the production meeting. Paul Hummer is going to bring this up during the Code stand up and assess if it's really critical. If it is, an assignee will be set and a IncidentLog reported.

Revision history for this message
Jonathan Lange (jml) wrote :

I should have indicated that I've already started work on this.

Changed in launchpad-bazaar:
assignee: nobody → jml
status: Triaged → In Progress
Revision history for this message
Jonathan Lange (jml) wrote :

There's a workaround, so it's not critical.

The workaround is to make the branch not the dev focus, request a mirror using Launchpad APIs, then make the branch the dev focus again once the branch is mirrored.

Changed in launchpad-bazaar:
importance: Critical → High
Jonathan Lange (jml)
Changed in launchpad-bazaar:
status: In Progress → Fix Committed
Tim Penhey (thumper)
Changed in launchpad-bazaar:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

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