Obstructed folders in Subversion

Viewed 95878

What the heck does "obstructed" mean when you try to check into Subversion? I see two folders in red with text status of "obstructed." I don't see what this means anywhere in the docs.

When I try the cleanup command, I get "folder name is not a working directory." This is a folder I just created in VS, and when I try to add it to Subversion it gives me that error. All other folders are fine.

17 Answers

it occurs when you have deleted or moved the .svn subdirectories (without going through SVN commands), so SVN has a corrupted view of the working copy.

Try a cleanup first, and if that doesn't solve it, revert (or update) the directory to restore the subdirectory .svn folders.

Without knowing what causes this, the solution can be to export the working copy (the entire checkout you have locally) to somewhere else.

If you are using tortoisesvn, you get the option to "export un-versioned files", but I think if doing it from the command line it only exports versioned files so you might have a bit of a laborious task copying un-versioned files manually.

Once done, check out a clean working copy and then drop the exported backup you have over the top of it. It's very important that the backup has no .svn folders in it.

I've seen these errors before when people have checked out working copies inside other working copies or anything else that corrupts the .svn entries.

This means that, for some reason, a conflict has occurred during the operation. Check to see if there is an existing unversioned file or folder with the same name as a versioned one.

(Paraphrased from the Tortoise SVN client help file)

I ran into this in Eclipse where some files were marked with a red exclamation point. The problem was a stray .svn folder in the source directory. I deleted the .svn folder, refreshed eclipse, and was able to check in the files.

I deleted .svn in obstructed directories and update it from outside. Then outside svn command will recognize these files.

Related