This post is for my benefit. Sometimes when working with SVN, I will use a tool like Eclipse/SVN or some fancy GUI svn, but then decide to ditch it and do things through the command-line. And as things have it, the command-line version is an older version than my fancy GUI SVN. The SVN client will complain: “This client is too old to work with working copy ‘…’ “. And I end up googling for the fix (because I know there is one and I’ve used it in the past) and have a hard time coming up with the keywords to find it.
Here it is for quick reference:
More to the point, here’s the script to fix it: Working Copy Format Script
From the FAQ:
I got an error saying “This client is too old to work with working copy ‘…’ “. How can I fix it without upgrading Subversion?
Sometimes the working copy metadata format changes incompatibly between minor releases. For example, say you have a working copy created with Subversion 1.4.4, but one day you decide to try out Subversion 1.5.0. Afterwards, you attempt to switch back to 1.4.4, but it doesn’t work — it just gives the above error.
This is because 1.5.0 upgraded your working copy format to support some new features (in this case, changelists, the keep-local flag, and variable-depth directories). Although 1.4.4 doesn’t know anything about these new features, it can at least recognize that the working copy format has been upgraded to something higher than it can handle.
1.5.0 upgraded the working copy for a good reason: it realizes that 1.4.4 does not know about these new features, and that if 1.4.4 were to meddle with the working copy metadata now, important information might be lost, possibly causing corruption (see issue #2961, for example).
But this automatic upgrade behavior can be annoying, if you just want to try out a new release of Subversion without installing it permanently. For this reason, we distribute a script that can downgrade working copies when doing so is safe: