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

Bo Berglund Bo.Berglund at system3r.se
Thu May 13 13:29:22 BST 2004


If this is indeed the case then we should ask Tony to make the lockserver
case *insensitive*. It is a PITA to enforce people to all use the same
case when they check out things since CVSNT accepts any case that the
user might have typed in while checking out.
I had great problems with ViewCvs (which is case sensitive) when I tried to
autocreate links to the files in CVSMailer. I had to put a lookup scheme
in place to clean up this. But it only involves one single server side
application and this is not the case with CVS.
Note that any root the user has in his CVS/*** files will be transferred
to the CVSNT server *and used by it* during its own operations even though
it should know by itself which case is correct for the repository roots.

Bo

-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf
Of Pat Galea
Sent: den 13 maj 2004 09:58
To: Flavio Medeiros Sales
Cc: cvsnt at cvsnt.org
Subject: Re: [cvsnt] Error FAIL Lock not within repository - How to
solve ?


Flavio Medeiros Sales wrote:
> The error occurs for one of our cvs users when he tries to commit or update
> a file, on any computer.
> Anyone know how to solve this ?
> 
> cvs -q commit -m "message" Servidor\ServidorK3.tlb
> Servidor\ServidorK3_TLB.pas (in directory D:\Usuarios\Heraldo\k3cvs\Source\)
> cvs [server aborted]: Failed to obtain lock on /k3/Source/Servidor: 001 FAIL
> Lock not within repository

If you're using cvsnt version 2.0.28 or newer, the lockserver is now 
case sensitive. I've had the same problem several times since upgrading 
from an older version.

In each case, I just asked the user to change his CVSROOT to be the 
right case, and the problem went away.

Pat Galea
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt



More information about the cvsnt mailing list