SVN 锁定错误:锁定令牌 URI 的方案错误 [英] SVN Lock error: Lock token URI has bad scheme

问题描述

我最近尝试在我的 SVN 结帐中锁定文件，但出现以下错误:

I recently tried to lock a file in my SVN checkout, and I got the following error:

svn lock -m "a comment" File1.pas

svn lock -m "a comment" File1.pas

svn:警告:W160037:锁定令牌 URI '
C:\Program Files (x86)\VisualSVN Server>exit 0
' 有糟糕的计划；预期的 'opaquelocktoken'

svn: warning: W160037: Lock token URI '
C:\Program Files (x86)\VisualSVN Server>exit 0
' has bad scheme; expected 'opaquelocktoken'

其他人首先收到错误(Windows 7)，然后我在我的测试存储库(Windows 8)上复制了它，并在不同的文件上进行了新的结帐.我最初使用 Tortoise v1.8.9，然后使用命令行实用程序 v1.8.11 复制它.存储库是 VisualSVN Server 3.2，但我也尝试将测试存储库升级到 3.3 版.简而言之，它出现在我尝试使用 TortoiseSVN 和 SVN CLU 的所有文件中，用于 VisualSVN Server 3.2 和 3.3.

Someone else got the error first (Windows 7), then I replicated it on my test repo (Windows 8) with a fresh checkout on a different file. I originally used Tortoise v1.8.9, and then replicated it using the command line utility v1.8.11. The repository is VisualSVN Server 3.2, but I also tried upgrading the test repository to version 3.3. In short, it is showing up on all the files I have tried using TortoiseSVN and SVN CLU, for VisualSVN Server 3.2 and 3.3.

我发现的唯一参考是:http://mail-archives.apache.org/mod_mbox/subversion-dev/201107.mbox/[e-mail]%3E.它显示了用于生成错误的代码.似乎回购正在发回:

The only reference to this I have found is here: http://mail-archives.apache.org/mod_mbox/subversion-dev/201107.mbox/[e-mail]%3E. It shows the code being used to generate the error. It seems like the repo is sending back:

C:\Program Files (x86)\VisualSVN Server>exit 0

C:\Program Files (x86)\VisualSVN Server>exit 0

而不是 opaquelocktoken 信息.在这一点上，我认为这是 VisualSVN Server 中的错误，或者我们在 VisualSVN Server 上配置了错误，尽管我找不到任何相关设置.接受任何建议.

instead of the opaquelocktoken information. At this point I am thinking it is a bug in VisualSVN Server or we have something configured on VisualSVN Server incorrectly, although I could not find any pertinent settings. Open to any suggestions.

推荐答案

这不是 VisualSVN Server 中的错误，而是管理员配置的锁定后挂钩脚本中的错误.联系服务器管理员，让他修复钩子脚本.

This is not a bug in VisualSVN Server, but an error in post-lock hook script that was configured by an administrator. Contact the server administrator asking him to fix the hook script.

这篇关于SVN 锁定错误:锁定令牌 URI 的方案错误的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！