Neil Martinsen-Burrell пишет:
> I won't have time for a week or so to look into this, but the steps used
> by colo-ify should be reproducible using simple bzr commands and moving
> directories. Try replacing step 3 by:
>
> 3a. mkdir .bzr/branches
I think this step actually should be
bzr init-repo .bzr/branches --no-trees
> 3b. bzr branch . .bzr/branches/trunk
> 3c. bzr reconfigure --lightweight-checkout --bind-to=.bzr/branches/trunk
>
> and see what happens. If that doesn't reproduce the bug, then there's a
> bug in colo-ify.
IIUC, you're using bzrlib API for this. So the problem in API usage.
I'm really doubt there is any bugs in colo-ify.
Neil Martinsen-Burrell пишет:
> I won't have time for a week or so to look into this, but the steps used
> by colo-ify should be reproducible using simple bzr commands and moving
> directories. Try replacing step 3 by:
>
> 3a. mkdir .bzr/branches
I think this step actually should be
bzr init-repo .bzr/branches --no-trees
> 3b. bzr branch . .bzr/branches/trunk checkout --bind- to=.bzr/ branches/ trunk
> 3c. bzr reconfigure --lightweight-
>
> and see what happens. If that doesn't reproduce the bug, then there's a
> bug in colo-ify.
IIUC, you're using bzrlib API for this. So the problem in API usage.
I'm really doubt there is any bugs in colo-ify.