[cvsnt] Failed to obtain lock (version 2.0.34)

[Pat Galea]

Ariel Machado wrote:
 > Dears:
 >
 > I update the cvsnt server and clients from versions 2.0.24 to 2.0.34.
 >
 > Work fine except for a developer box.
 >
 > Executing edit command generate this error:
 >
 > cvs edit fArti.frm
 >
 > cvs [server aborted]: Failed to obtain lock on 
/Development/Gespos/Tables>
 > 001 FAIL Lock not withing repository.
 >
 > Strange... only 1 cvs user have this problem....
 >
 > If I rooll-back to 2.0.24 version this work fine....

I've just had a similar problem which I fixed. I've posted it elsewhere, 
but for your convenience here it is again.

In 2.0.28, a change was made to the lockserver; it is now case-sensitive.

By correcting the case of the repository in the CVSROOT (i.e. "Ixxxxxx" 
rather than "ixxxxxx"), cvs edits work again.

Basically, just be very careful with your case. I found this only when I 
inadvertently did a check out using the *correct* case; cvs edits then 
worked fine. I did a diff between that tree and a tree in which cvs 
edits weren't working, and the only difference I could find was that the 
case of the repository name in the CVSROOTs was different.

I don't know if the case of individual filenames will cause problems 
too. I generally use TortoiseCVS, so that's not an issue.

Hope that helps.

Regards
Pat Galea