Executing bzr heads fails with central branch is unreachable?

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

This is a very strange issue.  It describes behaviour that Bazaar and
Bzrtools do not appear to implement.

On 13-11-13 03:03 PM, ckalisiak at attotech.com wrote:
> 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."

I cannot find the word "Central" in either the bzr or bzrtools source
code.  Please run again with -Derror so that we can see where the
message is coming from.

> 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

No, shared repositories are very much designed around the idea that
the shared repository contains only revisions, and is oblivious to the
branches inside it.

> 1) Is there a way to instruct "bzr heads" not to traverse all 
> repositories, and only traverse the local repository?

No.  It should already be doing that.

> 2) Is there a way to inform the Bazaar shared repository that a
> branch no longer exists?

No, it doesn't know that it exists in the first place.

> 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?

It should be fine to just use "mv" or your preferred file manager.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlKD6d4ACgkQ0F+nu1YWqI1IQgCgic42MV2D1/nwNc7XGLD/m2j7
SZgAn0dmWzhTspCZRTOyrMTdhjy3NhQ8
=mbdg
-----END PGP SIGNATURE-----