SVN "not a working copy"

Solution 1:

Suppose that the URL was http://svn.example.com/somewhere/somerepo. Then svn co http://svn.example.com/somewhere/somerepo creates a subdirectory of the current directory called somerepo. That's where the svn checkout is located.

If you want to add more files to the svn repository, you need to put them under that somerepo directory.

cd somerepo
# create someFolder and put your new stuff there
svn add someFolder
svn commit

Use the command ls to see what files exist in a directory. Use ls -A to also see hidden files like the .svn subdirectory.

Use svn info to see what svn thinks about the current directory.

All this is assuming that the checkout was successful. If you ever see this message from svn:

svn: OPTIONS from http://svn.example.com/somewhere/somerepo: 200 OK

(or some other HTTP code: 403, 403, etc.) that's subversion's way of telling you that it did not understand the response from the server. Common causes are:

• This is the wrong URL, the server at that URL is not a subversion server. Fix: type the correct URL.
• You did not authenticate successfully. Usually you get a 403 HTTP status in that case, but some servers reply with 404 or even 200 (which is supposed to mean success, but some servers are funny that way).