Re: "Dying gasps received from client." with CVS 1.12.11

[gnu-cvs]

Hi Mark,

Thanks for the follow-up.

Attached you'll find the logs, which SmartCVS sends to the GNU CVS
1.12.9 server as well as to the GNU CVS 1.12.11 server. Both files
(connection-log.out) are identical. For some reason GNU CVS 1.12.11
returns the mentioned error message (see
connection-logs-1.12.11/connection-log.in). The strange thing is, that
it seems to be directory-dependent. Maybe the most important is: when I
deactivate gzip-compression, it works fine (except the relative paths
issue). Did you changed the gzip-stuff between 1.12.9 and 1.12.11?

CVS 1.12.11 returns paths relative to the repository root:
...
Clear-static-directory ./
smartcvs/build/
...
where as CVS 1.12.9 returns the path fully:
...
Clear-static-directory ./
/misc/repository/smartcvs/build/
...

How do you think, the client should detect, whether the paths are
relative? Please note, that CVSNT might return absolute paths without a 
leading slash, e.g.
...
Clear-static-directory ./
c:\repository/test/
...
or
Clear-static-directory ./
c:/repository/test/
...

--
Best regards,
Thomas Singer
_____________
smartcvs.com



Mark D. Baushke wrote:
> Hi Thomas,
>
> Initial setup using a cvs-1.11.x client and a cvs-1.11.x server:
>
>   ssh mdb-lnx /bin/rm -fr /tmp/mdb-repos
>   cvs -d mdb-lnx:/tmp/mdb-repos init
>
> Using a cvs-1.11.x client and cvs-1.11.x server with the following commands:
>
>   cvs -d mdb-lnx:/tmp/mdb-repos co -A -P CVSROOT
>
> yeilds the files:
>   mdb.cvs.client.in-cvs-1.11.x
>   mdb.cvs.client.out-cvs-1.11.x
>
> Using a cvs-1.11.x client and a cvs-1.12.11 server with the following
> commands from the same repository above
>
>   exprt CVS_SERVER=cvs-1.12.11
>   cvs -d mdb-lnx:/tmp/mdb-repos co -A -P CVSROOT
>
> yeilds the files:
>   mdb.cvs.client.in-cvs-1.11.x-1.12.11
>   mdb.cvs.client.out-cvs-1.11.x-1.12.11
>
> These files were captured using the environment variable CVS_CLIENT_LOG
> with the cvs 1.11.x client chatting with the various servers.
>
> The biggest difference is that instead of sending /tmp/mdb-repos/CVSROOT/
> you will see CVSROOT/ sent as the directory.
>
> By the way, I did try to use SmartCVS 3.0.6, but the security for
> Public/Private_key is really silly. The file browser is unable to locate
> the .ssh directory by itself and why should I type the pass phrase into
> a SmartCVS window when you could better contact my ssh-agent using the
> SSH_AUTH_SOCK environment variable to have it give you the key for the
> connection, or even better, let me use my default SSH_ASKPASS program to
> prompt me for a pass phrase at need...
>
>         -- Mark