Ok, so at some point in time, somebody checked in some files with names that require a case sensitive file system into the trunk of a repository that I constantly check out. This of course leads to my local working copy locking up when I try to check it out (on my Windows computer). Is there any way that I can set my local subversion copy so that it will ignore any files whose names differ only in case?
+2
A:
You can use the repository browser to remove/rename the offending file then update your working copy as per normal, fix up any references to the file you renamed that may need fixing up, and commit the fixes.
Then drag up a shotgun and shoot whoever did this in the first place. Case sensitivity abuse is one of the few bad smells that I have trouble forgiving.
(edit: This assumes TortoiseSVN, but the solutions work for any SVN implementation. You just don't get to use a pretty browser.)
Edit:
The other option is to rename the local version of the file, then use the repository browser to check out the second version of the clashing files, move things around, sort out references as above, then commit the changes.
This has the advantage of only requiring one commit, and not messing around with other people unnecessarily who may or may not be working with the two files.
Matthew Scharley
2008-10-15 04:23:25
Well, the problem there is that I usually don't realize that it's broken until I've already tried updating my repository and had it lock down. :(
Jason Baker
2008-10-15 04:32:37
If this happens often, I'd either: A) have a serious talk with the person responsible. This really shouldn't be happening in the first place. b) look for an implementation of SVN that doesn't lock up with this issue. It will always error though, there's simply no way of handling this nicely on NTFS.
Matthew Scharley
2008-10-15 04:35:40
A:
Recompile svn using Interix's compiler. Now it handles case correctly on NTFS.
Joshua
2008-10-15 04:26:13
How would it do that? NTFS doesn't allow files that only differ by case. (The current administrative area design makes matters worse, but that part should mostly be resolved in Subversion 1.6)
Bert Huijben
2008-10-19 00:39:55
Oh yes it does. You just have a hard time getting at it from the Win32 subsystem.
Joshua
2008-12-09 05:12:12
+2
A:
++monoxide
I would personally clean up the repository and then put the safeguards in place to prevent it in the future. Even though it is a little more work.
Here is a link to go through the process of fixing the repository and then you can add the hook they describe in the instructions.
Chris Roland
2008-10-15 04:40:02