Change of file case confuses svn status on case insensitive file systems

My pysvn WorkBench Windows users want a workaround for a problem
that I'd assume should be solved in svn. The problem affects any WC that
is checked out on a file system that is case insensitive, e.g.
Windows and
Macintosh default file systems. I understand that TSVN has already added
code to work around this problem.

Here is a transcript showing the problem on the Mac:

  $ svn --version
svn, version 1.4.3 (r23084)
    compiled Jan 27 2007, 14:00:57
...
$ svn st -v
              1461 1435 barry .
              1461 1435 barry 2.txt
              1461 1435 barry 13.txt

$ rm 2.txt
$ echo NEW TXT >2.TXT
$ svn st -v
? 2.TXT
              1461 1435 barry .
! 1461 1435 barry 2.txt
              1461 1435 barry 13.txt
$ cat 2.txt
NEW TXT
$

As you can see the OS can find 2.txt but subversion thinks it missing
and
that there is a new unversion file 2.TXT.

Its common for MS Visual Studio to change the case of files
apparently that
has raised this issue.

 From reading the issue tracker I found these two issues that and case
of file isuues but not this problem.

1854 - loss of data is case of file changed
1495 - two file in repos differ by case only

Can I file a issue for this problem or does one I missed already exist?

Barry

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Apr 22 15:54:08 2007