bzr checkout . in a lightweight checkout creates a checkout in the branch

[John A Meinel]

I was testing the behaviour of "bzr checkout ." when you already have a checkout, and I was rather surprised. Specifically if you do:

bzr init-repo test
cd test
bzr branch $SOURCE branch --no-tree
bzr co --lightweight branch tree
cd tree
bzr co .

I expected it to either fail, or give some sort of info about what was going on in the current directory.
Instead, it ended up creating a checkout at "branch".

[Gareth White (gwhite-deactivatedaccount)]

Using "bzr checkout" with no arguments produces the same behaviour - i.e. it converts the tree-less branch into a branch with a tree, while apparently doing nothing to the actual checkout.

Running the command a second time produces an error "Cannot create a file when that file already exists", whether you run it from the checkout or from the branch.

The documentation for "checkout" says "If BRANCH_LOCATION is omitted, checkout will reconstitute a working tree for the branch found in '.'." I'm a little confused by what this means - if you want to convert a tree-less branch into a branch with a working tree, shouldn't you use "bzr reconfigure --tree"?

[Gareth White (gwhite-deactivatedaccount)]

Also, if you try the same command when using a smart server you get an error like "bzr://localhost/testrepo/branch/.bzr/ is not a local path". So it does look like it's misinterpreting the arguments somehow. Very strange...