Convert bzr

[Giorgos Keramidas]

On Tue, 18 Dec 2012 11:23:26 -0800, Adrian Klaver <adrian.klaver at gmail.com> wrote:
>On Sun, Dec 16, 2012 at 5:14 PM, Adrian Klaver <adrian.klaver at gmail.com>wrote:
>>On 12/16/2012 02:31 PM, Giorgos Keramidas wrote:
>>> That is the strange part, they all have only a default branch on the bzr
>>> side. Though in the cases that worked on the first try the branch names in
>>> the hg repositories where equal to the root directory name of the bzr
>>> repository, if that helps. In other words the conversion I had issues with
>>> was the only one that ended up with a default branch in the hg repository.
>>> The bzr format versions are the same for all also. Well a problem for
>>> another day.
>
> Figured it out. The aws bzr repository had a tag in it where the other bzr
> repositories did not. Convert created a .hgtags file to track that and that
> created a new branch. Also solved the mystery of why the default branch in
> bzr is renamed to another name by Convert. Convert uses the bzr branch nick
> which by default is set to the repository directory name. To make the
> convert run with out incident for the aws project I created a branchmap
> file:
>
> aws default
>
> then did:
>
> hg convert --branchmap aws_branchmap software_projects/aws/
>
> Then in aws-hg did:
>
> hg update
>
> The result was:
>
> aklaver at ford:~/aws-hg$ hg branch
> default
>
> and the working directory in place.

Thanks for retrying this, verifying that indeed using a branch map fixed
the original problem, and also documenting it in the Wiki! :-)