On Jul 1, 2008, at 16:38, kmradke_at_rockwellcollins.com wrote:
> Ryan Schmidt wrote on 07/01/2008 04:02:24 PM:
>> I see from your paths that you're on Windows, which usually uses a
>> case-insensitive filesystem.
>> Do you maybe have two files in that directory whose names differ only
>> in case? That can cause this error. Two files whose names differ only
>> in case can coexist in the same directory with no problems in a
>> Subversion repository, or on a case-sensitive filesystem, but not on
>> a case-insensitive filesystem. You can use "svn ls URL" to look in
>> the repository URL directly to see if my hunch is correct. If so, you
>> can use "svn cat URL" to see the contents of the two files. If they
>> are identical, you can use "svn rm URL" to remove the file that you
>> don't want to keep, or "svn mv URL1 URL2" to move it to a different
>> name so that you can check it out.
>> This problem comes up so often on the list. It should be turned into
>> a FAQ entry. And then, Subversion should be modified to detect the
>> situation and issue a better error message, for example: "Error:
>> Cannot check out directory SnapShots on a case-insensitive filesystem
>> because ssf27f0.html.z and ssf27f0.html.Z differ only in case". This
>> bug says no Subversion developers use case-insensitive filesystems,
>> as an explanation for why the error message has not been improved:
>> Is that still the case? No Subversion developers use Mac OS X or
> NTFS can actually work in a case sensitive manner (originally for
> POSIX support). Most of the Win32 Object Manager APIs do have a case
> sensitivity option.
> However, even if SVN was modified to support this option (I believe
> it would most likely be in APR), users would still be confused when
> they can't use normal win32 applications to open their files that
> differ by CaSe only...
> I assume we would still want SVN to support FAT32 as well, which
> means we can't do much except spit out a better error message.
That's all I'm asking for: a comprehensible error message which
clearly states that there is a case conflict, what files are causing
it, and maybe even prints out the URL to the (thus far nonexistent)
FAQ entry that explains how to resolve the problem (rename or remove
one of the files e.g. by using repository URLs) and how to prevent it
in the future (pre-commit hook to prevent commits of case collisions).
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-07-01 23:49:27 CEST