SVN upgrade working copy
Solution 1
You have to upgrade your subversion client to at least 1.7.
With the command line client, you have to manually upgrade your working copy format by issuing the command svn upgrade
:
Upgrading the Working Copy
Subversion 1.7 introduces substantial changes to the working copy format. In previous releases of Subversion, Subversion would automatically update the working copy to the new format when a write operation was performed. Subversion 1.7, however, will make this a manual step. Before using Subversion 1.7 with their working copies, users will be required to run a new command,
svn upgrade
to update the metadata to the new format. This command may take a while, and for some users, it may be more practical to simply checkout a new working copy.
— Subversion 1.7 Release Notes
TortoiseSVN will perform the working copy upgrade with the next write operation:
Upgrading the Working Copy
Subversion 1.7 introduces substantial changes to the working copy format. In previous releases, Subversion would automatically update the working copy to the new format when a write operation was performed. Subversion 1.7, however, will make this a manual step.
Before you can use an existing working copy with TortoiseSVN 1.7, you have to upgrade the format first. If you right-click on an old working copy, TortoiseSVN only shows you one command in the context menu: Upgrade working copy.
— TortoiseSVN 1.7 Release notes
Solution 2
from eclipse, you can select on the project, right click->team->upgrade
Solution 3
On MacOS:
- Get the latest compiled SVN client binaries from here.
- Install.
- Add binaries to path (the last installation screen explains how).
- Open terminal and run the following command on your project directory:
svn upgrade
Solution 4
If you have just upgraded to SVN 1.7 on your machine (like I just did), and have a lot of projects in your Eclipse workspace which need to be upgraded, you can do the following in a terminal window on Unix-baesd systems:
cd [eclipse/workspace] # <- you supply the actual path here
for file in `find . -depth 2 -name "*.svn"`; do svn upgrade `dirname $file` ; done;
After Googling a bit, I found what seems to be the equivalent for Windows users:
http://www.rqna.net/qna/mnrmqn-how-to-find-all-svn-working-copies-on-win-xp.html
See the answer by Alexey Shcherbak halfway down the page.
Solution 5
This problem due to that you try to compile project that has the files of OLder SVN than you currently use.
You have two solutions to resolve this problem
- to install the version 1.6 SVN to be compatible with project SVN files
- try to upgrade the project ..( not always working ).
user810430
Updated on March 18, 2020Comments
-
user810430 about 4 years
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?
-
geneorama over 10 yearsWhen I issue the command
svn upgrade
Ubuntu tells me "command not found" -
knittl over 10 years@geneorama: do you have
svn
installed? (sudo apt-get install svn
) -
geneorama over 10 yearsThanks for the reply! I did have svn installed (subversion), but it was version 1.6, which does not have the
upgrade
command. Ubuntu 12.04 wouldn't install 1.7 without adding a new ppa. askubuntu.com/questions/65468/… -
Mike Eng over 10 years@genorama Here are instructions to upgrade svn for Mac OS that will work if starting from 1.6 redfinsolutions.com/blog/update-subversion-mac-os-x . For Linux, I imagine it's similar.
-
rabidmachine9 about 10 years"This command may take a while, and for some users, it may be more practical to simply checkout a new working copy." I'm running the command don't knowing what to expect, after 2 seconds the console replies upgraded '.' :P
-
Robert Casey over 9 yearsThis is also a helpful URL for those using Subclipse in Eclipse: http://benohead.com/use-svn-1-8-eclipse/.
-
Amit Thaper almost 9 yearsUnable to find upgrade option
-
Lucio Menci over 5 yearsPerforming an upgrade for my working copy, what will do server side? Will other users using an old version be able to continue to use their dated version?
-
knittl over 5 years@LucioMenci: other users will not be affected by your local settings