问题描述
我们使用 Subversion 来跟踪我们的代码.作为构建过程的一部分，一些 AssemblyInfo.cs 文件被构建脚本临时编辑，当构建完成时，它们将被恢复(也由构建脚本).但是，我们的一位开发人员在尝试还原时收到此消息:
We are using Subversion to keep track of our code. As part of the build process, some AssemblyInfo.cs files gets temporarily edited by the build script, and when the build is done they are reverted (also by the build script). However, one of our developers get this message when the revert is attempted:
客户年龄太大，无法合作工作副本路径".你需要获取更新的 Subversion 客户端，或降级此工作副本.
我们都在运行相同版本的 Subversion (1.5.1).开发人员设置之间的唯一区别是，遇到问题的用户使用的是更高版本的 TortoiseSVN(1.6.0，而不是其他版本的 1.5.x)，并且我们一直在运行 Subversion 1.5.1存储库已存在.
We are all running the same version of Subversion (1.5.1). The only difference between the developer setups is that the user having the problem is using a later version of TortoiseSVN (1.6.0, as opposed to 1.5.x for the others), and we have been running Subversion 1.5.1 the whole time the repository has existed.
您对可能的问题有什么暗示吗?
Do you have any hint on what the problem might be?
推荐答案
每当任何 Subversion 客户端接触到一个工作副本时，它所做的第一件事就是默默地将该工作副本更新到它的版本.
Whenever any subversion client touches a working copy, the first thing it does is to silently update that working copy to its version.
TortoiseSVN 会这样做，让其他 Subversion 客户端无法可靠地读取工作副本.
TortoiseSVN will have done this, leaving the other subversion clients unable to reliably read the working copy.
这适用于所有版本的所有 Subversion 客户端(到目前为止).Commandline、Tortoise、subclipse、ankh、rapidsvn - 都表现相同.
This is true for all subversion clients in all versions (so far). Commandline, Tortoise, subclipse, ankh, rapidsvn - all behave the same.
有一个 Python 脚本可以降级工作副本，或者您可以将其废弃并重新开始新的结帐.请参阅发行说明的兼容性部分.
There is a python script to downgrade a working copy, or you can just scrap it and start again with a new checkout.See the compatibility section of the release notes.
Tortoise 通常遵循它使用的 Subversion 客户端的主要版本号.
Tortoise generally follows the major release number of the subversion client it uses.
在您的情况下，您使用 2 个客户端 - 乌龟和构建脚本中的命令行.在更新到最新版本之前，构建脚本将无法工作.
In your case you're using 2 clients - tortoise and the commandline in the build script. The build script won't be able to work until it's updated to the latest version.
我们自己也有这个问题.
We have this problem ourselves.
这篇关于Subversion:获取“客户端太旧"即使所有开发人员都运行相同的 svn 版本的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！