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.
>>Works fine locally, and even remotely most of the time - My test sandbox
>>has a couple of different repositories in it. I can cause something
>>similar in client/server by mucking around with the tree and causing it
>>to leave by the wrong directory, but that's a different error ('there is
>>no version here') which is fixable quite easily.
>>
>I think I saw this message too, have to check when I get to work
>(where the problem is visible). What is the easy fix?
>
>The strange thing is the error message that comes up because it really
>uses very funny wording. I will repeat at work and post the complete
>response.
Now at work with a restarted WinCvs and trying to repeat the operations
that failed yesterday. But now for some strange reason it all works as
I would like it to....
I wonder why.
My operations yesterday were:
- Go to an existing sandbox
- Do a checkout of a module from another repository into this sandbox
- Issue a cvs update command
This failed to work as I described previously.
Then I did:
- go into the checked out extra module folder
- run a cvs update - worked OK
Could the cvs update in the checked out folder help restore the general
functionality?
Note that the checkout operations were done on the command line outside
WinCvs, but the updates I did from withing WinCvs.
Is this possibly a WinCvs issue, for example confusing the cvsroot settings?
Versions:
WinCvs = 1.3.21.2
Client: Concurrent Versions System (CVSNT) 2.0.41a (client/server)
Server: Concurrent Versions System (CVSNT) 2.0.41 (client/server)
(Can't upgrade the server until I *know* it's safe, we have *all* of our
company sources in this server....)