[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

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

From: Karl Fogel <kfogel_at_red-bean.com>
Date: 2007-04-26 01:52:56 CEST

Barry Scott <barry@barrys-emacs.org> writes:
> On Apr 22, 2007, at 14:53, Barry Scott wrote:
>> 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
>> $
>> 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?
> I was hoping for some feedback for this problem.
> I am following the rules arn't I ask here before filling an issue?

You are, and thank you for that!

So, have you also looked at these two issues:


? I think it's possible that the bug you're seeing is a duplicate of
one of them... in fact, I think it is quite likely to be another
symptom of issue #667. If you could take a look at that issue in
detail, that would be great.

If you think it is a dup, go ahead and add a comment to the issue,
linking to your original mail in the archives (to save you time:

If you think it's not the same bug, go ahead and file a new issue, but
please mention issue #667 in your new issue, and vice versa, so that
there's a trail connecting them in case we later discover they are
both due to the same underlying problem.

If you have time to analyze the code and come up with a patch, that
would be even better, of course, but no problem if you can't.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Apr 26 01:53:06 2007

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.