svn: warning: '.' is not a working copy

svn working-copy
Mark picture Mark · May 3, 2011 · Viewed 70k times · Source

On a server, I used the svn import command to put files into SVN.

I checked the files out to my local machine, made some changes and then committed back.

Now I want to update the server copy of the files, but using svn update, it shows "skipped '.'" and svn status shows "svn: warning: '.' is not a working copy".

Answer

Eelke picture Eelke · May 3, 2011

Importing into svn doesn't make what you import a working copy. You have to check it out on the server just as you did locally. From then on it will be a working copy and you can use update.

Related questions

SVN upgrade working copy

I cannot do a SVN commit. I get this error: org.apache.subversion.javahl.ClientException: The working copy needs to be upgraded svn: Working copy 'C:\.... is too old (format 10, created by Subversion 1.6) How can it be fixed?

Read More
SVN - Change working copy to point at new svn path

I've got a SVN Repository that has moved to a new address/path. However, I've got a working copy with uncommitted source code still pointing to the old (now invalid) repository path. How do you change a working copy to …

Read More
SVN - Not a working copy error

I'm pulling my hair out on this one. I have a site which is version controlled using Subversion. I use aptana (eclipse, subclipse) to do the svn. I have been checking in and out files, updating etc and everything is …

Read More