When trying to resume an interrupted checkout, bzr dies with:
bzr: ERROR: Not a branch: /home/jean/repos/bzr/code.launchpad.net/bzr-trunk/.bzr/branch/
Here's some discussion on how to fix it:
<jam-laptop> lifeless: I probably agree, but I would argue it is hard to
detect the "I want to resume a checkout" from "I'm
accidentally checking out into a different branch"
<jam-laptop> unless we store what operation is occurring and clean that
up when it finishes
<lifeless> jam-laptop: i think its fairly easy to tell :).
<jam-laptop> In which case we might as well have a 'bzr resume' command
<lifeless> jam-laptop: threre are three failure points' repo, branch,
tree
<lifeless> if you have repo, no branch, no tree, its a resuming checkout
trivially. (any dir that exists will be empty)
<lifeless> if you have repo, branch, no tree then its the same as
'checkout .' basically - easy to support and detect reliably
<jam-laptop> except for a shared repo at the root
<jam-laptop> which has a repo but no branch
<jam-laptop> and no tree
<jam-laptop> and you don't really want it to have either
<lifeless> why not?
<jam-laptop> Because I typed a command in the wrong directory
<jam-laptop> the point of not overwriting was because we didn't want to
break what you already had
<lifeless> 'bzr zap-tree'
<lifeless> or add a --force option to checkout and say 'there appears to
be bzr data here already, you can use --force to create a
checkout anyway'
<jam-laptop> --force is a decent answer
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jean Jordaan wrote:
> <jam-laptop> the point of not overwriting was because we didn't want to
> break what you already had
> <lifeless> 'bzr zap-tree'
Seems like an obvious extension of "bzr remove-tree".
Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://
iD8DBQFGk7dy0F+
adlionIQy5ZH5DI
=uafF
-----END PGP SIGNATURE-----