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"
svn: E155004: Run 'svn cleanup' to remove locks (type 'svn help cleanup'
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 couldn't find any documentation that stated svn move only accepts
WC-relative paths as most other SVN commands happily take absolute paths.
Either way, it appears this error message might not be the most accurate.
Thanks for all the help and support.
Received on 2014-05-22 17:06:27 CEST