为什么 SVN 找不到修订版 0 的存储库位置
我最近升级了在我的工作站上安装的 SVN 和 TortoiseSVN 的版本，每当我在没有任何更改的情况下检查文件的差异时，都会收到以下错误。
Unable to find repository location for "<path>" in revision 0
我已经检查了我的一个项目的新副本（我已经尝试了几个），它仍然给了我相同的结果。
我尝试在我的工作站上升级 SVN，希望它能解决问题（我假设无法比较）- 没有骰子。
我还尝试完全重新安装 TortoiseSVN - 再次，没有骰子。
我所做的唯一有趣的事情是移动原始存储库的位置（存储在文件系统上，而不是数据库上）。但它的路径与错误消息相同，所以我相信它正在找到存储库。
还有什么原因呢？
I've recently upgraded the version of SVN and TortoiseSVN that I have installed on my workstation and whenever I check the diffs on a file without any changes, I get the following error.
Unable to find repository location for "<path>" in revision 0
I've checked out a fresh copy of one of my projects (I've tried it on a few), and it still gives me the same result.
I've tried upgrading SVN on my work station in hopes it would fix the problem (I assumed an incomparability) - no dice.
I also tried re-installing TortoiseSVN completely - again, no dice.
The only other funny thing I've done is move the location of the original repository (stored in on the file system, not a DB). But its path is the same as the error message, so I believe it's finding the repository.
What else could be the cause?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
这似乎是在没有任何更改的情况下检查文件差异的预期结果。我本来期望得到像“文件是最新的”这样的结果，但是在我确信仍在工作的不同工作站上返回到旧版本的 TortoiseSVN 给了我与未编辑的文件相同的结果。
This appears to be the expected result for checking the diffs on a file without any changes. I was expecting a result like "the file is up to date", but going back to an older version of TortoiseSVN on a different workstation that I was confident was still working gave me the same result for an unedited file.
您的第一个修订版（修订版 0）可能没有“trunk”、“branches”或“tags”目录。它们通常在初次签入（修订版 1）时添加。
因此，如果您将“svn switch”插入到这些目录之一（通常是对“trunk”目录执行此操作），那么在该目录上请求修订版 0 将正确地给出一条错误消息，指出路径“<在修订版 0 中找不到“;svnrepo>/trunk”，因此它无法拉取该修订版并仍然遵循之前的“svn switch”命令。
尝试“svn switch”到项目名称，而不进入任何子目录，我敢打赌你可以拉出修订版 0。
Your first revision (revision 0) probably doesn't have the "trunk", "branches", or "tags" directories. They are usually added in the initial check-in (revision 1).
As such, if you have "svn switch"-ed into one of those directories (typically one does this to the "trunk" directory), then asking for revision 0 on that directory would correctly give you an error message that the path "<svnrepo>/trunk" can't be found in revision 0, so it can't pull that revision and still honor the previous "svn switch" command.
Try "svn switch" to the project name, without going into any sub-directories, and I'll bet you can then pull up revision 0.
这将在目录 /path/to/repos 中创建一个新存储库。这个新的存储库从版本 0 开始，它被定义为除了顶级根 (/) 文件系统目录之外什么都不包含。最初，修订版 0 还具有单个修订版属性 svn:date，设置为创建存储库的时间。
This creates a new repository in the directory /path/to/repos. This new repository begins life at revision 0, which is defined to consist of nothing but the top-level root (/) filesystem directory. Initially, revision 0 also has a single revision property, svn:date, set to the time at which the repository was created.