SVN "not a working copy"
By Matthew Cannon
Ok ... so I wanted to upload something to an SVN server. How hard can that be? Well, turns out I've been using windumb for too long.
First I am supposed to "clone" the folder to my computer, using
svn co --username USERNAME URLAlright, so I
cd ~/.../0.SVN
svn co --username USERNAME URLand get an
svn: OPTIONS from URL: 200 OK.Next, I create a folder ~/.../,
put some files into that folder and want to add it so I can commit it.
svn add someFolderAnd now it's giving me an
"." is not a working copyAnd I have no idea what's going wrong because I'm basically doing exactly what the instructions I was given are saying.
1 Answer
Suppose that the URL was . Then svn co 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 commitUse 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 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).
