I'm having the following error message (when I try to upload a change to a file):

In F:\My Documents\23. Drupal\contributions: "F:\Program Files\TortoiseCVS\cvs.exe" "-q" "commit" "-m" "Various corrections." "translations/pt-pt/path-module.po"
CVSROOT=:pserver:mcduarte@cvs.drupal.org:/cvs/drupal-contrib

cvs server: [11:56:17] waiting for drupal's lock in /cvs/drupal-contrib/contributions/translations/pt-pt
cvs server: [11:56:47] waiting for drupal's lock in /cvs/drupal-contrib/contributions/translations/pt-pt

--//--

I looked all over the internet and I found this is a common problem in CVS and sometimes happens... Check, for example:

http://lists.ximian.com/archives/public/mono-list/2004-August/022541.html
http://blast.lns.mit.edu/BlastTalk/archive/1410.html
http://www.linuxmafia.com/faq/Devtools/cvs-lecture.html

--//--

This is happening only inside pt-pt... I tested in another area and everything works fine for me...

contributions\translations\pt-pt

Regards,

Miguel Duarte

Comments

mcduarte2000’s picture

mcduarte2000 commented

Solution (I just don't know how to do it or if I have permissions for doing it):

Caroline Meeks asks:

Somehow I managed to create a lock in CVS

cvs commit -m "deleteing a community now causes it to be disapproved"
cvs commit: Examining .
cvs server: [22:08:48] waiting for caroline's lock in
/usr/local/cvsroot/aces/packages/education/admin-www

any clue what I did and how to undo it?

If you see messages like this, it means you're trying to access a subdirectory of the repository that is locked by some other CVS process at the moment. A process is being run in that directory so it may not be in a consistent state for other CVS processes to use. If the wait message persists for a long time, it probably means that a CVS process failed to clean up after itself. This can happen when CVS dies suddenly and unexpectedly.

The solution is to remove the lock files by hand. Go into that part of the repository and look for files named "#cvs.lock" or that begin with "#cvs.wfl" or "#cvs.rfl". The waiting CVS processes eventually notice that the lock files are gone and allow the requested operation to proceed.

mcduarte2000’s picture

mcduarte2000 commented

Done.

JamesK’s picture

JamesK commented
Title: CVS error » drupal-cvs stale lock
Project: Drupal.org site moderators » Drupal.org infrastructure
Component: other » CVS
Priority: Critical » Normal
Status: Closed (fixed) » Active

I am attempting to update my contrib module (geo_filter) in CVS, but I am getting a similar message to above when I try to commit:
(In WinCVS)

cvs commit -m "documentation updates; #706008 change module name to project name"
cvs commit: Examining .
cvs commit: [03:21:15] waiting for drupal-cvs's lock in /cvs/drupal-contrib/contributions/modules/geo_filter

It appears to be an issue with the repo. I tried making the commit from a different local directory with the same result.

dww’s picture

dww
we/he/they
commented
Status: Active » Closed (fixed)

I confirmed the locks were pointing to a process that no longer existed on the server, so I removed them.

@JamesK: Thanks for searching for duplicates first! However, in this case, a 5+ year old infra issue is probably better left closed, just because you hit a similar problem. ;)

Cheers,
-Derek

Component: CVS » Other