bzr init bug

[John A Meinel]

Nir Soffer wrote:
> If you run bzr init twice in the same directory you get this:
> 
> First run:
> $ bzr init
>     -> no output, quite confusing isn't it?
> 
> Second run:
> $ bzr init
> bzr: ERROR: File exists:
> u'/Volumes/Home/nir/Projects/codewrap/src/.bzr': [Errno 17] File exists:
> '/Volumes/Home/nir/Projects/codewrap/src/.bzr'
> 
> Instead of:
> This directory is already versioned. Try bzr help init for more info.
> 

Yes, this should be a better error.

> 
> I wonder what happen if you do something like this:
> 
> mkdir foo
> cd foo
> bzr init
> mkdir bar
> cd bar
> bzr init
> 
> Do you get a versioned directory inside a versioned directory?
> 
> 
> Best Regards,
> 
> Nir Soffer
> 

Yes, you do get a versioned directory inside another. Which is very
useful. It can allow you to have a project which uses a library, and
both of them can be independently versioned. In the future, bzr will
actually support it even better, such that it can track the sub-trees,
and tell what revision they were at.

But yes, I agree that 'bzr init' should probably say something. Perhaps
prompting you to use 'bzr add'.

And the error for 'bzr init' when there already is a control directory
should give a better error.

John
=:->



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 249 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060204/daf5ee7c/attachment.pgp