Executing bzr heads fails with central branch is unreachable?

[ckalisiak at attotech.com]

Hello all,

   I unintentionally overwrote some commits in the task branch in my local
shared repository with "bzr pull --overwrite", so I'm attempting to execute
a "bzr heads --dead-only" to determine the revision I need to revert to.
However, it appears that every branch that we've either moved from one
folder to another within the central repository, or removed from the
central repository, causes "heads" to fail with the emitted error "Central
branch [branch name] is unreachable." This error message is not related to
the contents of the branch.conf file; it appears that the repository
remembers that a branch by that name existed at some point, and because the
branch is no longer present, it won't complete the "heads" operation.

   It appears that all that is necessary to work around the error is "bzr
init [branch name]" in the correct folder. And, just like a bad linker from
the 90's, an error for the next unreachable branch is eventually emitted.
Lather, rinse, repeat. I've been at this for a couple hours, so I'm writing
this email to ask...

1) Is there a way to instruct "bzr heads" not to traverse all repositories,
and only traverse the local repository?
2) Is there a way to inform the Bazaar shared repository that a branch no
longer exists?
3) What are best practices for moving a branch from one folder to another
folder in the same shared repository such that the shared repository is
aware of the move?

Thanks,
Chris

--
Chris Kalisiak
Senior Embedded Systems Engineer
ATTO Technology, Inc.
Phone:  +1.716.691.1999 ext. 274
Fax +1.716.691.9353
"Powering the World's Networks & Storage"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/bazaar/attachments/20131113/909c6f10/attachment.html>