Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-apps-owner AT cygwin DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT cygwin DOT com>
List-Help: <mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT cygwin DOT com
To: cygwin-apps AT cygwin DOT com
Subject: CVS with pserver: Binary files get corrupted
From: Holger Spielmann <holger AT spielmann DOT net>
Date: 12 Feb 2002 20:04:10 +0100
Message-ID: <87wuxiikt1.fsf@shambler.spielmann.net>
Lines: 38
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Common Lisp)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Sender: 520012522232-0001 AT t-dialin DOT net

Hello,

due to company policy, I have to use Windows in my current project, so
I started using Cygwin to get a halfway decent environment.

I successfully managed to set up a CVS pserver on Cygwin. In our
project, we want to add some JAR files to the CVS, so the frameworks
API (here: Cocoon) can be assured to be on the same revision for all
developers.

But the jars arrive garbled in the repository, despite I added them
with the -kb option. First I thought it might be related to the text
mode I used for mounting the file systems, but transferring the
repository didn't change anything, I even tried to import a new
project from scratch.
For all binary files, linefeed is replaced by CR/LF, and yes, it
already happens when the files arrive in the repository.
As I read in an older posting by Corinna Vinschen concerning ash,
dated from April 2001, this might be related to the cvs pserver
process opening its socket with O_TEXT. Alas, grepping thru the
sources of cvs and inetutils showed me no place where I might try to
patch.

Using rsh is no opportunity because we get dynamic IPs, using ssh
with client certificates would involve additional software and
procedures, to which some of my collegues are not used to, and putting
the repository on a Windows share is too damn slow and lacks any
security.
Ah, and did I mention the policy keeps me from just putting Debian on
one of the boxes... :(

Any ideas regarding this problem? A patch would be quite handy!

TIA
-- 
Holger Spielmann
Germany
phone/fax: +49-700-SPIELMANN