RE: CVS Feature Branch - version - cannot write to stdout

[Conrad T. Pino]

Hi Mark,

> From: Mark D. Baushke
> 
> Hi Conrad,
> 
> Could you provide a bit more information? 

Yes I'd be glad to do so.

> Which client/server protocol are you using? 
> 
>   * :ext: over ssh
>   * :ext: over rsh
>   * :pserver: tunneled over ssh
>   * :pserver:

Simple ":pserver:" to a host on my LAN.

> I presume that the client is a Windows cvs top-of-tree and that the
> server is a vanilla cvs 1.11.17 cvs distribution.

Client: Yes, top of tree it is.

Server: Yes, it the vanilla cvs 1.11.17 distribution built from source
on the target platform (Solaris 8 Intel Edition).

> Do you happen to know the OS of the server?

Solaris 8 Intel Edition.

> For myself, using FreeBSD 4.2-RELEASE as the server OS and FreeBSD
> 4.2-RELEASE as the client OS, :ext: over ssh, I get the following:
> 
> bash$ ./cvs version
> Client: Concurrent Versions System (CVS) 1.12.9.1 (client/server)
> Server: Concurrent Versions System (CVS) 1.11.17 (client/server)
> bash$ 

My first example was with my local server via plain ":pserver:".

> Using FreeBSD 4.2-RELEASE as the client OS, and cvshome.org as the
> server, :pserver: tunneled over ssh, I get the following:
> 
> bash$ ./cvs version
> Client: Concurrent Versions System (CVS) 1.12.9.1 (client/server)
> Server: Concurrent Versions System (CVS) 1.11.15-scast-vc-1.5.2 
> (client/server)
> bash$

Here's the example with cvshome.org via ":pserver:" SSH tunnel:

        H:\cvs-1.12>WinDebug\cvs version
        Client: Concurrent Versions System (CVS) 1.12.9.1 (client)
        Server: cannot write to stdout: No error
        Concurrent Versions System (CVS) 1.11.15-scast-vc-1.5.2 (client/server)

        H:\cvs-1.12>

> I do not happen to have any Windows clients to use for testing...

Could you make constructive use of Windows 2000 Server platform accessible
remotely via SSH tunneled telnet?

>       -- Mark

Conrad