tags:

views:

7124

answers:

3

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

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.

+5  A: 

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.

gbjbaanb
weird. I ended up having to do a checkout of this folder. The folder existed before in the repository. I then deleted it without using the svn delete command. By checking it back out and committing, problem resolved. Then on another .css file that I did NOT rename, delete, and only have been editing it, it I had to do an svn update because I was getting some weird issue with that (different message).
CoffeeAddict
Good God, I was trying to commit based on a copy of this project that I had on my external drive, not the working copy from my local drive. Duh.
CoffeeAddict
This often happens if you move a directory from one place to another and don't use the SVN move command. The hidden .svn file is moved along with it but is not updated. Deleting the .svn files fixes the problem.
+1  A: 

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)

Colin Nicholls
+2  A: 

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.

Neil Trodden
That fixed it for me. Thanks!
Patrick