Convert bzr

[Patrick Mézard]

Le 16/12/12 21:30, Adrian Klaver a écrit :
> On 12/16/2012 06:08 AM, Giorgos Keramidas wrote:
>> On Sat, 15 Dec 2012 19:37:06 -0800, Adrian Klaver <adrian.klaver at gmail.com> wrote:
>>> On 12/15/2012 07:03 PM, Giorgos Keramidas wrote:
>>>> Στις 16/12/2012 12:58 πμ, ο/η Adrian Klaver έγραψε:
>>>>> I am trying to use the convert extension to create a hg repository
>>>>> from a bzr one. The convert runs and creates a new directory with
>>>>> the .hg subdirectory. There is no working directory though, even
>>>>> after doing hg update. Any suggestions.
>>>>
>>>> Does 'hg log' show any changesets at all?
>>>
>>> It shows changesets.
>>
>> So something _was_ converted. It's possible that the conversion script
>> was interrupted abruptly, and it left the dirstate of the working
>> directory in a messed up state.
>>
>> Can you try specifying the 'tip' version and updating with --clean to
>> that version?
>>
>>      cd aws_hg
>>      hg update --clean tip
>>
>> If that doesn't work, please post the output of 'hg parents' and the
>> output of 'hg debugcheckstate' too.
> 
> To answer this post and the previous one from Adrian.:
> 
> aklaver at panda:~/aws_hg> hg summary
> parent: 33:7a34cb90bd27 tip
>  update tags
> branch: default
> commit: (clean)
> update: (current)
> 
> aklaver at panda:~/aws_hg> hg status
> aklaver at panda:~/aws_hg>
> 
> aklaver at panda:~/aws_hg> hg parents
> changeset:   33:7a34cb90bd27
> tag:         tip
> parent:      -1:000000000000
> user:        convert-repo
> date:        Sun Dec 16 11:30:51 2012 +0000
> summary:     update tags
> 
> aklaver at panda:~/aws_hg> hg debugcheckstate
> aklaver at panda:~/aws_hg>
> 
> 
> 
> This might be a good time to ask what is supposed to happen?
> I am working under the assumption that using convert creates a new directory with a .hg subdirectory and the working files from the original repo(this case bzr) copied over. Is this what is intended or am I making a false assumption?

It creates a new repository but does not checkout anything. Here you may have an issue with a simple "hg update" because convert created a misplaced tag changeset (meaning you have two heads on default branch). Running:

  $ hg branches

should display converted branches. If the one you want is "default", run:

  $ hg heads default

this may display more than one changeset, including the tags one. Pick the one you want (not the tags one) and use it with "hg update".

Otherwise, "hg update -C BRANCH" should give you the branch you want.

Running a graph viewer on the repository may also help clarifying things.
--
Patrick Mézard