Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-Id:	<5.1.1.5.2.20020628135027.00b799e8@www.marble.be>
X-Sender:	gerrit AT www DOT marble DOT be
Date:	Fri, 28 Jun 2002 13:54:50 +0200
To:	cygwin AT cygwin DOT com
From:	Gerrit Cap <Gerrit DOT Cap AT marble DOT be>
Subject:	Re: Latest version of SSH and WinCVS Problems
Mime-Version:	1.0

Hi Corinna,

I really don't know exactly what characters are expected by WinCVS but I 
just tried CYGWIN=binmode and CYGWIN=nobinmode and as a result: with 
regarding to WinCVS no difference, still the same error with cygwin-1.3.11 
dll. When reverting back to cygwin-1.3.10 the problem disappears.

Gerrit.


>On Fri, Jun 28, 2002 at 09:00:28AM +0200, Gerrit Cap wrote:
> > Hello Cygwin users,
> >
> >
> > I have exactly the same problem. After upgrading to cygwin-1.3.11-3 from
> > cygwin-1.3.10 WinCVS chokes on using the cygwin ssh. The problem is
> > carriage return linefeed stuff related. Apparently if wincvs connects to a
> > cvs server using ssh with the "old" cygwin dll everything works fine, but
> > with the new cygwin dll, Wincvs gets an extra character after the ok
> > response from the cvs server before the expected newline which resolves in
> > the cvs program included with wincvs not recognizing the ok.
> >
> > I guess something like this is happening
> >
> > cvs server sends ok\n -> ssh protocol -> ssh.exe client of cygwin using
> > 1.3.10 dll -> ok\n to WinCVS
> > cvs server sends ok\n -> ssh protocol -> ssh.exe client of cygwin using
> > 1.3.11 dll -> ok\r\n to WinCVS which then says:
> > "cvs: update: unrecognized response: `ok
> > ` received" as an error message
> >
> > I also tried to remove cygwin and change the initial choice of "DOS" files
> > to "UNIX" files or vice versa without result
> >
> > Was there a specific reason why the cygwin-1.3.11 dll was changed for 
> this ?
>
>In theory it should be the other way around since 1.3.11 tries to
>do everything in UNIX mode if the user doesn't say different.
>
>Could you play with the CYGWIN setting 'binmode', please?
>
>Corinna



-------------------- Marble Consulting ----------------------
Gerrit Cap                      http://www.marble.be/
OO Solutions Engineer           mailto:Gerrit DOT Cap AT marble DOT be
Marble Consulting
Blauwe Gaanweg, 53              tel : +32 475  72.94.36
B-9150 Kruibeke-Bazel           fax : +32 3   744.19.17
Belgium
-------------------- Marble Consulting ----------------------
There is only one thing in the world worse than being witty,
and thats not being witty.          (Monthy Python)



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -