Launchpad itself

Auto-stacking fails on staging

Bug #486537 reported by Matt Nordhoff
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

Something is going wrong with auto-stacking of new branches on staging:

$ bzr init
$ bzr push lp://staging/~mnordhoff/bzr/test5/
Using default stacking branch /~bzr-pqm/bzr/bzr.dev at lp-63070544:///~mnordhoff/bzr
bzr: ERROR: Server sent an unexpected error: ('error', 'Not a branch: "lp-63070544:///~bzr-pqm/bzr/bzr.dev".')

I first noticed this a day or two ago, but it could've been happening longer; I rarely use staging.

See original description
Tags: lp-code
Matt Nordhoff (mnordhoff)
description: updated
Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

This is because most branches, including lp:bzr, don't exist on staging.

Maybe we can come up with some whacky fallback-to-production-data thing like the librarian does...

Revision history for this message
Tim Penhey (thumper) wrote :

I think this is something to take up with the LOSAs for the technology side of things.

Changed in launchpad-code:
importance: Undecided → Low
status: New → Triaged
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.