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: warning: W160037: Lock token URI '
C:\Program Files (x86)\VisualSVN Server>exit 0
' has bad scheme; expected 'opaquelocktoken'
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.
The only reference to this I have found is here: http://mail-archives.apache.org/mod_mbox/subversion-dev/201107.mbox/%[email protected]%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
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.
