renaming a stacked-on branch causes problems

[Javier Collado]

I'm the owner of a bazaar branch hosted in launchpad that I cannot branch and to/from which I cannot push/pull:
lp:~javier.collado/checkbox-editor/branch-push-pull-failure

When pushing the failure is:
bzr: ERROR: Server sent an unexpected error: ('error', "Cannot lock LockDir(lp-102856016:///~javier.collado/checkbox-editor/branch-push-pull-failure/.bzr/branchlock): File exists: u'/srv/bazaar.launchpad.net/mirrors/00/05/b8/97/.bzr/branch/lock': [Errno 17] File exists: '/srv/bazaar.launchpad.net/mirrors/00/05/b8/97/.bzr/branch/lock'")

and when branching/pulling the failure is:
bzr: ERROR: Not a branch: "bzr+ssh://bazaar.launchpad.net/~oem-community-qa/checkbox-editor/trunk/"

The branching/pulling message is more informative since the problem is that a branch that is needed isn't available. That branch, indeed, no longer exists since I decided to change the owner from oem-community-qa to javier.collado so now it has a different name. My guess is that when some branch is stacked onto another and the original branch is modified, those changes aren't propagated to the branches that depend on it, and their repositories remain incomplete as they need the repository in the original branch to get the whole history.

Please let me know if you need more information.

[Martin Pool (mbp)]

As a workaround, if you are able to write to the stacked branches, you can use 'bzr reconfigure --stacked-on NEW_URL -d STACKED_BRANCH_URL'

[Javier Collado (javier.collado)]

Thanks for the advice. Since I had a local copy of the branch I pushed it to a different location, but it's good to know the reconfigure command.