SVN 错误 - 不是工作副本 [英] SVN Error - Not a working copy

问题描述

最近我们的 svn 服务器发生了变化，我们做了一个 svn 切换.

Recently our svn server was changed and we did a svn switch.

由于工作副本有大量未版本化的资源，工作副本被锁定，我们开始为 svn 下的所有文件夹逐个文件夹切换，效果很好.

Since the working copy had a huge amount of unversioned resources, the working copy got locked and we started switching folder by folder for all folders under svn, which works perfectly fine.

但是在存储库的最顶层，当我尝试更新文件时，我得到 svn: Working copy '.'锁定错误和清理也无济于事.当我进行清理时，我会收到这样的错误 - svn: 'content' is not a working copy directory

But at the top most level of the repository, when I try to update files, I get the svn: Working copy '.' locked error and cleanup is not helping either. When I do cleanup, I get errors like these - svn: 'content' is not a working copy directory

新鲜结帐根本不是一种选择.有没有其他方法可以清除和释放锁并完全切换?

Fresh checkout is NOT an option at all. Are there any other ways to cleanup and release the locks and do the switch completely ?

JesperE 回答的最后一段

The last paragraph in JesperE's answer

如果您在以下情况下收到非工作副本"做一个递归的svn清理"我的猜测是你有一个目录这应该是一个工作副本(即顶层的 .svn 目录这么说)，但它缺少自己的.svn 目录.在这种情况下，你可以尝试删除/移动它目录，然后进行本地更新

If you get a "not a working copy" when doing a recursive "svn cleanup" my guess is that you have a directory which should be a working copy (i.e. the .svn directory at the toplevel says so), but it is missing its own .svn directory. In that case, you could try to just remove/move that directory and then do a local update

似乎是解决存储库中问题的方法.我已经确定了这些文件夹，并单独对这些特定文件夹进行了全新检查，哇，锁定在随后的清理中被释放！非常感谢 JesperE !!

seems to be the solution to the problem in the repository. I have identified those folders and did a fresh checkout of those specific folders alone and wow, the locks are released in the subsequent cleanup! Thanks a lot JesperE !!

但是，我仍然无法弄清楚现在读取的 svn switch 错误，

But, I still cannot figure out the svn switch error which now reads something like,

svn:存储库位于'svn://repourl/reponame/文件夹名'有 uuid 'm/reponame'，但 WC有'b5b39681-0ff6-784b-ad26-2846b9ea8e7d'

svn: The repository at 'svn://repourl/reponame/foldername' has uuid 'm/reponame', but the WC has 'b5b39681-0ff6-784b-ad26-2846b9ea8e7d'

有什么想法吗?

推荐答案

如果在执行递归 svn cleanup 时得到非工作副本"，我猜你有一个目录是一个工作副本(即顶层的 .svn 目录是这样说的)，但它缺少自己的 .svn 目录.在这种情况下，您可以尝试删除/移动该目录，然后进行本地更新(即 rm -rf content; svn checkout content).

If you get a "not a working copy" when doing a recursive svn cleanup my guess is that you have a directory which should be a working copy (i.e. the .svn directory at the top level says so), but it is missing its own .svn directory. In that case, you could try to just remove/move that directory and then do a local update (i.e. rm -rf content; svn checkout content).

如果你得到一个 not a working copy 错误，这意味着 Subversion 在那里找不到合适的 .svn 目录.查看contents

If you get a not a working copy error, it means that Subversion cannot find a proper .svn directory in there. Check to see if there is an .svn directory in contents

如果可能，理想的解决方案是重新结帐.

The ideal solution is a fresh checkout, if possible.

这篇关于SVN 错误 - 不是工作副本的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！