[cvsnt] CVS Checkout "-d ." Bug
hytham.alihassan at emerson.com
Wed May 14 04:30:10 BST 2008
Thanks for the quick response. It would be preferable from a security
standpoint to use a lock server and cvs remote access protocols only, but we
would need to first resolve the bug that we are experiencing.
The older pserver is using CVS v1.10.7, but as I mentioned I don't know of
anyone who is currently using it. I have used CVS clients up to v1.11.22
and CVSNT v2.5.03.2382. My tests usually constitute connecting to the
pserver with these clients and also connecting through multiple build
servers using the "ssh" access method. For testing CVSNT, I have only
tested it using the "ssh" access method thus far, with the repository nfs
mounted on the target machine. The target machine has CVSNT installed, and
I have tried checking out code using both CVS and CVSNT.
We currently have many past and present projects that are utilizing this
modules method of checking out individual files to a current directory, and
at this point we would like to avoid having to change the structure of the
repository to accommodate for this bug.
BTW, the plan would be to replace the older pserver with CVSNT if I can
demonstrate that it resolves these issues. I will send a formal request to
the support e-mail address tomorrow. When is the anticipated release of CVS
Suite 2008? Do you anticipate that this bug could be addressed by the final
On 5/13/08 9:07 PM, "Arthur Barrett" <arthur.barrett at march-hare.com> wrote:
> Always be sure to send some info about EXACTLY what version of CVS/CVSNT
> is on the server and the client and what OS your client and server are.
>> Until recently, we have primarily accessed the CVS repository
>> from local
>> servers only, all of which have an nfs mount of the
>> repository that all
>> users have access to. We are using file-based locking and, although a
>> pserver is available, I am not aware of anyone who uses it regularly.
> THIS WILL CORRUPT YOUR REPOSITORY - STOP THIS IMMEDIATELY.
> I am not kidding. Using :local: mode is for the developers of cvs/cvsnt
> only and multiple users accessing a repository this way will cause
> problems, but doing it via smb or nfs will corrupt your repository.
> This post from Mark Baushke (one of the original developers of 'old cvs'
> over 20 years ago) exlains why:
>> existing code modules the checkout fails to retreive certain files due
>> to the way that CVS handles "co -d ." when commands are
>> received using a
>> remote access protocol vs. a locally mounted repository.
> I vaguely remember this being asked some time in the not too distant
> What is it about your process that insists you much checkout to the
> current directory and not another, eg:
> cvs co -d temp module
>> I convinced my manager to purchase the CVS Suite so that I could find
>> out if CVSNT would fix the above issues, but unfortunately it
>> does not.
> Please contact CVS Suite support (the e-mail address to use is at the
> front of the eBook).
> If you put in a formal request then the feature can be considered for
> the next release. Be quick though - we are finishing off CVS Suite 2008
> right now.
> Note: I also don't know if it would be possible to fix without upgrading
> the server, and I don't know which server and client you are using
> Arthur Barrett
More information about the cvsnt