SV: [plcs-dex] RE: WinCVS checkout ....

You need admin access to modify the CVS repository – hence the support request to SF.

They have now responded and removed the lock.

Given that they are supporting over 100,000 projects and over 1Million users (https://sourceforge.net/docs/about) with no cost to the project, I reckon they provide an excellent service.

Regards
Rob

-------------------------------------------
Rob Bodington
Eurostep Limited
Web Page: http://www.eurostep.com http://www.share-a-space.com
Email: Rob.Bodington@eurostep.com
Phone: +44 (0)1452 810 960
Mobile: +44 (0)7796 176 401

-----Original Message-----
From: Tim Turner [mailto:tjt@lsc.co.uk]
Sent: 17 March 2006 19:16
To: 'rob.bodington@eurostep.com'; Tim Turner; 'plcs-dex@lists.oasis-open.org'
Subject: RE: [plcs-dex] RE: WinCVS checkout ....

Hi Rob, all

I got tired of waiting for sourceforge guys to address the issue (they seemed to have a lot of issues backed up already - so searched for a solution.

I found this on a help page re:wincvs etc..

Keep Getting Messages about Waiting for Locks? What's Going On?

If you see a message like this -

cvs update: [22:58:26] waiting for qsmith's lock in /usr/local/newrepos/myproj

- it means you're trying to access a subdirectory of the repository that is locked by some other CVS process at the moment. Because a process is running in that directory, it might not be in a consistent state for other CVS processes to use.

However, if this message persists for a long time, it probably means that a CVS process failed to clean up after itself, for whatever reason. It can happen when CVS dies suddenly and unexpectedly-for example, due to a power failure on the repository machine.

The solution is to remove the lock files by hand from the repository subdirectory in question. Go into that part of the repository and look for files named "#cvs.lock" or that begin with "#cvs.wfl" or "#cvs.rfl". Compare the file's timestamps with the start times of any currently running CVS processes. If the files could not possibly have been created by any of those processes, it's safe to delete them. The waiting CVS processes eventually notice when the lock files are gone-this should take about 15 seconds-and allow the requested operation to proceed.

See the node "Locks" in the Cederqvist manual for more details.

I spent an hour or two tying to do this but without success - has been too long since I set all this up - I think you need to start a remote session (telnet) & then change to the relevant directory on source forge etc.. however, I couldn't get a separate process to work for longer than a few seconds ;-(

regards,

Tim

From: Rob Bodington [mailto:rob.bodington@eurostep.com]
Sent: 17 March 2006 12:23
To: 'Tim Turner'; plcs-dex@lists.oasis-open.org
Subject: RE: [plcs-dex] RE: WinCVS checkout ....

I have asked SourceForge to remove the file lock:

https://sourceforge.net/tracker/index.php?func=detail&aid=1452532&group_id=1&atid=200001

Regards
Rob

-----Original Message-----
From: Tim Turner [mailto:tjt@lsc.co.uk]
Sent: 17 March 2006 17:14
To: 'rob.bodington@eurostep.com'; Tim Turner; 'plcs-dex@lists.oasis-open.org'
Subject: RE: [plcs-dex] RE: WinCVS checkout ....

Well, I had a problem the other day - but no error reported: it just hung there so I had to kill it.

The next time I checked it out, all seemed fine. But now it seems that I cannot do anything with it or any operations.

I've tried manually locking/unlocking, un-editing & so forth but nothing appears to work.

Most bizarre.

Maybe my network got a glitch in the middle of checking it in the other day & it's still waiting for some sort of completion signal - but I thought the process had been terminated. I have no other processes running on my machine.

I've killed & restarted pagent & wincvs, but still no change

Tim

From: Rob Bodington [mailto:rob.bodington@eurostep.com]
Sent: 17 March 2006 12:03
To: 'Tim Turner'; plcs-dex@lists.oasis-open.org
Subject: RE: [plcs-dex] RE: WinCVS checkout ....

Actually that is not the case.

CVS does not checkout anything. It allows concurrent editing. That's why you can get CVS conflicts.

When you check in changes to a file, CVS puts a lock on that file for the duration of the checkin. This is to prevent someone else checking out/in the file at the same time. As soon as it has successfully committed the changes, it removes the lock an allows others access to the file.

For some reason one of your files has been locked

Regards
Rob

-----Original Message-----
From: Tim Turner [mailto:tjt@lsc.co.uk]
Sent: 17 March 2006 16:57
To: 'rob.bodington@eurostep.com'; 'plcs-dex@lists.oasis-open.org'
Subject: RE: [plcs-dex] RE: WinCVS checkout ....

You cannot check out the file (for editing) when it is already being edited.

You should be able to check out a read-only version though.

For some reason it is failing to check in my latest version, so something's amiss here.

I will try again & send out an update shortly.

regards,

Tim

From: Rob Bodington [mailto:rob.bodington@eurostep.com]
Sent: 17 March 2006 11:48
To: plcs-dex@lists.oasis-open.org
Subject: [plcs-dex] RE: WinCVS checkout ....

I have raised this as an issue on SourceForge:

https://sourceforge.net/tracker/index.php?func=detail&aid=1452532&group_id=1&atid=200001

Regards
Rob

-----Original Message-----
From: Rob Bodington [mailto:rob.bodington@eurostep.com]
Sent: 17 March 2006 13:29
To: 'Mats Nilsson'; 'Arne'
Cc: Tim Turner (TJT@lsc.co.uk)
Subject: RE: WinCVS checkout ....
Importance: High

I don't know.

I get the same result.

It looks like we are trying to checkout the same dex at the same time that Tim is checking it out.

CVS is smart (?) enough to deal with concurrent access. Though in this case it seems to have failed.

Tim ...... could you stop your CVS checkout / checkin and try again?

Regards
Rob

-----Original Message-----
From: Mats Nilsson [mailto:mats.nilsson@rocketmail.com]
Sent: 17 March 2006 11:51
To: Rob Bodington; Arne
Subject: WinCVS checkout ....

Why does this happen?

cvs checkout: Updating dexlib/data/dex/work_package_definition

cvs checkout: [11:43:42] waiting for intrepidtim's lock in /cvsroot/dexlib/dexlib/data/dex/work_package_definition

cvs checkout: [11:44:12] waiting for intrepidtim's lock in /cvsroot/dexlib/dexlib/data/dex/work_package_definition

cvs checkout: [11:44:42] waiting for intrepidtim's lock in /cvsroot/dexlib/dexlib/data/dex/work_package_definition

cvs checkout: [11:45:12] waiting for intrepidtim's lock in /cvsroot/dexlib/dexlib/data/dex/work_package_definition

cvs checkout: [11:45:42] waiting for intrepidtim's lock in /cvsroot/dexlib/dexlib/data/dex/work_package_definition

cvs checkout: [11:46:12] waiting for intrepidtim's lock in /cvsroot/dexlib/dexlib/data/dex/work_package_definition

cvs checkout: [11:46:42] waiting for intrepidtim's lock in /cvsroot/dexlib/dexlib/data/dex/work_package_definition

cvs checkout: [11:47:12] waiting for intrepidtim's lock in /cvsroot/dexlib/dexlib/data/dex/work_package_definition

cvs checkout: [11:47:42] waiting for intrepidtim's lock in /cvsroot/dexlib/dexlib/data/dex/work_package_definition

cvs checkout: [11:48:12] waiting for intrepidtim's lock in /cvsroot/dexlib/dexlib/data/dex/work_package_definition

cvs checkout: [11:48:42] waiting for intrepidtim's lock in /cvsroot/dexlib/dexlib/data/dex/work_package_definition

Regards,

Mats

Yahoo! Mail
Use Photomail to share photos without annoying attachments.

DISCLAIMER: ***SECURITY LABEL: NOT PROTECTIVELY MARKED*** The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. This e-mail originates from LSC Group. Registered in England & Wales No 2275471 Registered Office: Devonport Royal Dockyard, Devonport, Plymouth, PL1 4SG

plcs-dex message