Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
For the record, I was able to (sort of) figure out this problem. It
probably had little to do with the -d option. Apparently, any branch based
upon a certain tag in my repository (v8000) will have problems if its tag
name is more than four characters. With other tags (v8002, e.g.), there
doesn't seem to be a problem, so I can only assume that there is some
corruption in the RCS files. I created a branch with a 3-character tag name
and the problem disappeared.
The v8000 tag was created with Eclipse 1.0 (actually Websphere app dev)
while the other tags were created with the latest stable build of Eclipse
(2.0.xxx). So I assume that this is a problem with the eclipse CVS client
that they have resolved.
If Tony or anyone else is interested in reproducing this problem, let me
know and I'll send you a chunk of my repository.
-----Original Message-----
From: OMALLEY, JOHN C (SBCSI)
Sent: Tuesday, February 26, 2002 4:18 PM
To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
Subject: Problems with checkout -d
Configuration
Server: NT Server 4.0 SP6. CVSNT 1.11.1.2 (Build 41).
Only "pserver protocol" is checked in control panel.
Client: Win 2K SP2. CVSNT 1.11.1.2 (Build 41)
The command:
cvs checkout -d modulename_branch -r branch_tag modulename
will appear to work fine. The folder is created, and all files are added.
If, however, I do a cvs status, I get something like this:
cvs server: X.java is no longer in the repository
=================================================================
File: X.java Status: Entry Invalid
Working revision: 1.1.1.1
Repository revision: No revision control file
Sticky Tag: v800 _branch_1 - MISSING from RCS file!
Sticky Date: (none)
Sticky Options: (none)
In the above example, the Sticky Tag should have been v8000_branch_1.
The update, commit, log, etc. commands will give the same "cvs server:
X.java is no longer in the repository" message.
In attempting to diagnose this problem, I noticed the following:
1. If a branch is checked out using the default module name, it will work
as far as update and commit are concerned, however, the output from cvs
status will be similar to the above (v800 _branch_1 - MISSING from RCS
file!).
2. If I copy the repository to my local hard drive (c:\localcvsroot) and
simply use a CVSROOT of c:\localcvsroot everything works fine. The cvs
status output is correct, and I can update and commit on the branch that was
checked out with the -d option.
3. I tried turning on "pserver impersonation" (which I confess I don't
quite understand) and restarting the service. I then checked out a fresh
copy, using the -d and -r options as above. There was no change in
behavior.
Thanks in advance for any help with this problem.
John O'Malley
Technical Architect - ETM
SBC Communications, Inc.
_______________________________________________
Cvsnt mailing list
Cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs