bug-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Mark D. Baushke
Subject: Re: "Dying gasps received from client." with CVS 1.12.11
Date: Tue, 18 Jan 2005 10:05:02 -0800

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

gnu-cvs@regnis.de writes:

> 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). 

No attachment was found in the message. This may be due to bug-cvs
stripping the attachment...

> 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?

The zlib library went from 1.1.4 to 1.2.1 on 2004-11-11. There has been
one other compression complaint, but I am not sure if Derek ever figured
out what was wrong or not.

> 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/
> ...

Yes.

> 
> 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/
> ...
> 

Hmmm... I don't have any good answers for you.

        -- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQFB7U/N3x41pRYZE/gRAiS4AJ9YowMmIdQFj3qXwNj2NAoyN+yDGQCgxf27
Mvh7oOZAOw31gOHpAyp/8sQ=
=rJIM
-----END PGP SIGNATURE-----



reply via email to

[Prev in Thread] Current Thread [Next in Thread]