Jason Hines | 2 Jun 2003 02:24

cvs lock on tigris


during a large commit, i am now getting this error:

cvs server: [17:15:36] waiting for tigrisc's lock in 
/cvs/binarycloud/r2/binarycloud/ext/phing/classes/phing/tasks

while looking for a fix on google, i found this remark on a random 
mailing list  (i'm assuming it applies..)

I'll try again in an hour..

<quote>
 >Is there any reasonable way to prevent anoncvs from locking the
 >repository for prolonged periods of time?  I've just committed a small
 >change, and now I'm sitting before the terminal for 30 minutes staring at
 >``waiting for anoncvs's lock'' messages.  And it's not over yet.

If you were stuck for this long, it almost certainly means a CVS process 
has
died and left a stale lock in the repository.  Someone needs to go in and
delete it manually.

Gmane