SVN: A directory version with the same name already exists

Question

Our CVSDude account was migrated this week. After the end of the week, unable to access our repo, it supported a slightly different URL ("'-' changed to '.' Basically). We used the TortoiseSVN move command to switch working copies, and it worked throughout the day quite smoothly.

But today I started getting an error in the header when doing updates. I deleted the folder in question because it was small and updated again. This folder was recreated in my working copy, but the same error appeared in another folder.

I have Googled, and here are two common answers:

• you changed the directory name case
• you mistakenly marked your .svn files

We did not change any folders at all - the first folder to start the complaint was not affected for weekks - and I also double-checked the .svn thing. Other people on the team do not report the same problem, and they also use Windows + TortoiseSVN.

Ideas / inspiration?

Answer 1

This happens to me all the time with version 1.6.17, even though the existing directory has the expected URL. I am working on this by moving the directory to the side, updating or checking, and moving it backward, knocking down what I just got. Stupid, but it works.

mv dir dir2 svn co blah . rm -rf dir mv dir2 dir 

Answer 2

This is very similar to the old case sensitivity case. If you run svn log, you will see in which case the repo thinks your directory should be. Compare with your local. I believe that his unheard-of recovery of the repo from the backup and everything has changed.

Another alternative is that the IDE or the hs tool changed the case of your directory / file. This happens to me sometimes with Visual Studio. The turtle usually tells you the exact problem, and allows you to fix it.

You can still try to clean up, which can repair the damaged .svn directory.

If you need svn binaries for Windows, I just grab them from the VisualSvn Server installation.

Answer 3

I think I would do a new check instead of updates. Can you make svn log -v in the appropriate directory?

Answer 4

This can also happen if you have a file or directory opened in another application (or on the command line). For example, if svn is trying to update the directory foo containing a line with files, and you have foo active in cmd or cygwin, or foo / bar opened in the editor. Textpad is especially bad with this, and sometimes you may need to close it completely.

A good Windows utility for determining which applications have open locks in a directory / file is an “unlock”.