svn is not a working copy 怎么解决

如题所述

SVN:This client is too old to work with working copy…解决方法[OK]

这两天项目提交时候,虚拟机用SVN提交的时候,总是报如下提示:
svn: This client is too old to work with working copy ‘/opt/gforge/www/account’. You need
to get a newer Subversion client, or to downgrade this working copy.
See http://subversion.tigris.org/faq.html#working-copy-format-change
for details.
其实有时候仔细看下报错提示还是很有用的,开始没有仔细看,试着升级SVN,其实是一个错误的方向。
正确的解决办法就是按照提示中的地址有FAQ的解释,可以解决这个问题。

访问地址:
http://subversion.tigris.org/faq.html#working-copy-format-change
官网已经明确说明地址转移了:
http://subversion.apache.org/faq.html#working-copy-format-change

原文如下:
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:
http://svn.collab.net/repos/svn/trunk/tools/client-side/change-svn-wc-format.py
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.
举例,在/home/mysvn文件夹下建立好change-svn-wc-format.py文件,然后在该目录下执行:
./change-svn-wc-format.py –help
可以看到命令格式:
usage: change-svn-wc-format.py WC_PATH SVN_VERSION [--verbose] [--force] [--skip-unknown-format]
change-svn-wc-format.py –help
执行命令:
./change-svn-wc-format.py /mulu 1.x –skip-unknown-format

说明:

上面的/mulu为文件路径,1.x为SVN当前版本号,只写2位版本号即可。
如版本为1.5.4,那么这里就写1.5就可以了。至此svn up可以正常执行了。
温馨提示:答案为网友推荐,仅供参考
第1个回答  2017-11-05
那是因为你后面的参数没有跟对,svn log 和 svn status后面如果不跟上SVN库的url时,默认是查当前文件夹的svn日志和状态,如果你当前文件夹不是一个checkout出来的SVN客户端文件夹,自然就会报这个错了。

“.”代表的是当前文件夹,那句报错意思是说当前文件夹不是一个工作副本(即SVN客户端文件夹)。

所以,你要么是checkout出来一个工作副本,然后cd命令将当前文件夹切到工作副本,然后svn log;要么是svn log 后面加上url参数本回答被提问者采纳
第2个回答  2019-06-26
估计你是在版本库中操作了,版本库的操作要对应添加对应的URL,也就是feil:///,或者svn://localhost/XXX 等才能显示

相关了解……

你可能感兴趣的内容

本站内容来自于网友发表,不代表本站立场,仅表示其个人看法,不对其真实性、正确性、有效性作任何的担保
相关事宜请发邮件给我们
© 非常风气网