On May 22, 2014, at 10:05 AM, Dan Ellis wrote: > In a recent thread I've been trying to figure out the best way to deal with > case sensitivity issues (in particular, finding out the clashing case > sensitive path). It doesn't appear that I'll be able to solve that one > readily, so I plan to convert all our existing mixed case entries to lower > case entries and really focus on the users to work this way. > > So I need to rename a bunch of directories and thought a script would handle > this well. I want to work in a WC vs directly on the repo so I can verify > other changes before I do a big commit (or series of commits). I ran into > something surprising though, svn move does not appear to handle absolute > working paths: > > c:\>svn mv "c:\project_files\sandbox\foo\Bar" > "C:\project_files\sandbox\foo\bar" > svn: E155004: Run 'svn cleanup' to remove locks (type 'svn help cleanup' for > details) > svn: E155004: Working copy 'C:\Project_files\sandbox\foo\Bar' locked. > svn: E155004: 'C:\Project_files\sandbox\foo\' is already locked. > > yet using relative paths does seem to work fine: > > c:\Project_files\sandbox>svn move ./foo/Bar ./foo/bar > <bunch of adds/deletes>
I didn't think doing case-only renames was possible when using a case-insensitive filesystem. But I see now that this became possible on Windows in Subversion 1.7: http://subversion.apache.org/faq.html#case-change Maybe the Windows-specific code that was added to handle this did not anticipate absolute paths being used.
