[cvsnt] Error FAIL Lock not within repository - How to solve ?

[Pat Galea]

Tony Hoyle wrote:
> All communication with the lockserver is automatically translated to
> the correct case before transmission.  There are no outstanding issues
> on this in 2.0.41 - this is easy to check.. checkout 'cvsroot',
> 'CVSROOT' and 'CvsRoot' and they'll all work just fine.
> 
> The only issue is when people try to bypass the repository prefixes by
> using a path relative to the current drive.  This is hard to fix
> (since 'current drive' means different things at different times) but
> is fixed in 2.0.42 by forcing it to mean whatever drive the cvs.exe is
> on.

I don't understand what you mean by "people try to bypass the repository 
prefixes". In every case where we've had the error, people have just 
been using the repository prefix in their CVSROOT. They've not been 
trying to bypass anything.

It's just that their old CVSROOT contained a repository prefix that had 
the wrong case. When we upgraded the cvsnt server, it no longer worked.

So, for example, my old CVSROOT was:

:sspi:jimmy:/i123456

When we upgraded to 2.0.34, I got the "FAIL Lock not within repository" 
error when trying to do a cvs edit. So I had to change my CVSROOT to:

:sspi:jimmy:/I123456

And then it worked.

Regards, pg