[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
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 -----Original
Message-----
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] Hi 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 -----Original
Message-----
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 -----Original
Message-----
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 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 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 |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]