I may have cuased this to happen. I was trying to checkout an older version of the code to compare lots of little things. Rather than do a diff, I just tried to check it out with cvs checkout -d <some_date> foo.

In any event, now that I'm ready to check back in (to the current tree), cvs is giving me:
cvs server: [11:38:33] waiting for leo's lock in /cvs/path/foo

so... uhh... what now? Leo hasn't worked with us since '02. The last time I checked in (commited) code for this project was a few months ago.

Locks in CVS are just files beginning with #cvs.rfl (read lock), #cvs.wfl (write lock) or #cvs.pfl (promotable read lock). So to remove a lock, simply go to the directory (in the repository) and remove such files which are owned by Leo (of course you need proper permissions to do so)

Just now getting back to this (and thanks for the response)...

so, in the repository (which, btw, was setup by leo), there are only two things that look like what you're talking about... #cvs.lock and #cvs.wfl.phil.307281. The former is an empty dir, the latter is an empty file. All other files in the directory are in the form filename,v - all owned by leo (as I would expect being that he setup CVS on that machine).

The exact message says:
cvs server: [15:57:16] waiting for leo's lock in /mnt/CVS/more_path/Vex

"Vex" is the directory which contains the files I'm trying to checkin. In the the directory that contains the "Vex" subdir, there's no #cvs... file.



other suggestions?