X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.8 required=5.0 tests=AWL,BAYES_00
X-Spam-Check-By:	sourceware.org
Message-ID:	<4C94C76F.70904@bopp.net>
Date:	Sat, 18 Sep 2010 09:06:39 -0500
From:	Jeremy Bopp <jeremy AT bopp DOT net>
User-Agent:	Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.12) Gecko/20100915 Thunderbird/3.0.8
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: git and ssh issue
References:	<AANLkTimUQD73UodFdGSVQ27LUYcdZux6tf0emsmTF_B5 AT mail DOT gmail DOT com>
In-Reply-To:	<AANLkTimUQD73UodFdGSVQ27LUYcdZux6tf0emsmTF_B5@mail.gmail.com>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

On 09/18/2010 12:23 AM, Frédéric Bron wrote:
> using cygwin 1.7.7(0.230/5/3) 2010-08-31 09:58 i686
> 
> I have right now an example where I cannot fetch with the following
> error message:
> 
> remote: Counting objects: 534, done.
> remote: Compressing objects: 100% (210/210), done.
> fatal: The remote end hung up unexpectedly
> fatal: early EOFs:  39% (141/359)
> fatal: index-pack failed
> 
> The repository contains proprietary data so that it cannot be accessed
> from somebody else but is there still anything I could do that would
> help to debug this now long standing issue? I am still using 1.5 for
> production because of this and I would be very much pleased to switch
> entirely to 1.7!

We have actually found a publicly available repository and a simple
scenario which reliably reproduces this problem:

http://cygwin.com/ml/cygwin/2010-07/msg00505.html

Unfortunately, it doesn't look like anyone has the time to dig deep into
this yet.  As you'll see in that thread, you can use Putty's plink
instead of ssh to handle the remote connections while you wait for a
fix.  At least you'll be able to take advantage of all the other Cygwin
improvements in the meantime.

-Jeremy

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -