X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.8 required=5.0 tests=AWL,BAYES_20 X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com Subject: Re: git stopped working with 1.7.1 Date: Sun, 27 Dec 2009 17:13:39 -0800 Message-ID: <21394.1261962819@gemini.franz.com> From: Kevin Layer X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com I'm a little surprised there are *no* replies to this thread, other than mine. (It's not like there is no traffic on the mailing list.) Can someone tell me what I need to do to interest people in this? Let me summarize: "git clone" fails with this: remote: Compressing objects: 100% (3300/3300), done. fatal: The remote end hung up unexpectedly fatal: early EOFs: 62% (5708/9205) fatal: index-pack failed The clone is via ssh from a box on my local (10 Gig) network. This has happened on *two* machines. Both 64-bit. One XP. One Windows 7. Both have all recent Windows updates. The Windows 7 box is a new one. I installed Windows, the Windows 7 SDK and then cygwin. Git is the first thing I tried, and it failed. The XP box I have used for years. I had a working git until the other day when I upgraded to cygwin 1.7.1--it fails just like the Windows 7 box after the upgrade. This seems serious. Do people just not use cygwin git? It may be a 64-bit issue, so I'll try a 32-bit machine, if I can scrounge one up. Thanks. Kevin -- 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