Either inconsistency in "bzr add" vs "bzr mv" or repository on Linux became case-insensitive

[Marius Kruger]

2009/10/8 Yegor Bryukhov <ybryukhov at gmail.com>:
> Hello,
>
> I have a repository (Linux, ext3) to which at some point I added a
> bunch of files that only differ in case (so I have Foo, foo, FOO and
> may be other combinations).
> "bzr info" says that this repository is: Standalone tree (format: pack-0.92)
>
> Later I wanted to change the naming convention of those files with
> "bzr mv" (I would still have Foo and FOO and foo) but it won't let me
> on some files, saying that that target file name is already versioned.
> So when I did "bzr add" it behaved case-sensitively but now "bzr mv"
> is not case-sensitive.

I tried it, with the following setup
bzr init /tmp/branch; cd /tmp/branch ; echo x > x; bzr add; bzr ci -m x

$ mv x X
$ bzr st
removed:
  x
unknown:
  X
$ bzr mv x X
x => X

which works fine.

$ bzr ci -m "x->X"
Committing to: /tmp/branch/
renamed x => X
Committed revision 2.

Then I tried to reproduce your case:
$ mv X x
$ bzr st
removed:
  X
unknown:
  x
$ bzr mv x X
bzr: ERROR: Could not move X => X: X is already versioned.

in this case I think you need to $ mv x X because X used to exist an
you just want x to be X.


Can you post a sample status (bzr st), the mv command you run and the output,
so I can better understand your problem.


-- 
<| regards
U| Marius
H| <><