如题所述
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å¯ä»¥æ£å¸¸æ§è¡äºã
è¿ä¸¤å¤©é¡¹ç®æ交æ¶åï¼èææºç¨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参数本回答被提问者采纳
“.”代表的是当前文件夹,那句报错意思是说当前文件夹不是一个工作副本(即SVN客户端文件夹)。
所以,你要么是checkout出来一个工作副本,然后cd命令将当前文件夹切到工作副本,然后svn log;要么是svn log 后面加上url参数本回答被提问者采纳
第2个回答 2019-06-26
估计你是在版本库中操作了,版本库的操作要对应添加对应的URL,也就是feil:///,或者svn://localhost/XXX 等才能显示