Hi Mark On Wed, 1 Jun 2005, Mark D. Baushke wrote:
> Tim Allen <[EMAIL PROTECTED]> writes: > > > I've been using CVS 1.11.17 clients (and earlier versions) on Windows > > machines with no problems. The CVS server runs on a Linux 2.4 box. Access is > > over SSH, using the Cygwin OpenSSH, using digital certificates. I've just > > tried the 1.12.11 and 1.12.10 clients, and get the following: <snip> > > > A great deal has changed between cvs 1.11.18 and 1.12.11, but I am not > able to reproduce your problem. I have been able to mix and match cvs > 1.11.17, cvs 1.11.18 and cvs 1.12.11 in combination as clients and > servers with no problems on a mixture of GNU/Linux, Solaris and FreeBSD > hosts. > > Note: I do not use any MS Windows clients for anything at all in my > environment (in fact, I do not have any such boxes available to me), so > it is possible that something in that regard is giving you problems. > > You may wish to tell us from whence you acquired the cvs.exe executable > you are using that is giving you problems. Does it still have problems > when you use a 'Command' window instead of a bash shell? Testing with SSH access on Linux clients gave no problems (i.e. 1.12.12 client, 1.11.18 server), so this does seem to be a specific problem with the 1.12.12 Win32 executable, which came from https://ccvs.cvshome.org/files/documents/19/884/cvs-1-12-12.zip This is being used from a command prompt. Thanks Tim _______________________________________________ Info-cvs mailing list [email protected] http://lists.gnu.org/mailman/listinfo/info-cvs
