This client is too old to work with working copy

我linux平台的svn client版本（1.5.1)和windows平台的乌龟版本(v1.6.6)不一致，在工作经常出现用乌龟升级了在windows下linux的samba共享目录，导致返回linux平台无法升级的错误：
“This client is too old to work with working copy ”
原因就是高版本升级写入了一些低版本不认识的信息在本地的.svn目录中， 现在可以使用subversion提供的工具恢复本地的Work folder到任意版本的脚本。
下载地址：

下载后在你的本地 work folder下运行（我的是linux）

---

python ./change-svn-wc-format.py ./ 1.5

---

然后在我的linux平台上就可用1.5.1的svn client来直接更新了。

[转载]

---

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 , 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:

Run that script with the "--help" option to see how to use it. As future versions of Subversion are released, we will try to keep this FAQ entry up-to-date with potential downgrade scenarios and their implications.

---