X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 	tests=AWL,BAYES_00
X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
Subject: Re: git stopped working with 1.7.1
In-reply-to: <db95995b0912291350y6e0bb513i99279a82fa604f50@mail.gmail.com>
References: <10711 DOT 1261594527 AT gemini DOT franz DOT com> <db95995b0912291350y6e0bb513i99279a82fa604f50 AT mail DOT gmail DOT com>
Comments: In-reply-to David Antliff <david DOT antliff AT gmail DOT com>    message dated "Wed, 30 Dec 2009 10:50:09 +1300."
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Date: Sun, 03 Jan 2010 18:06:14 -0800
Message-ID: <17853.1262570774@gemini.franz.com>
From: Kevin Layer <layer AT franz DOT com>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

David Antliff <david DOT antliff AT gmail DOT com> wrote:

>> On Thu, Dec 24, 2009 at 07:55, Kevin Layer <layer AT franz DOT com> wrote:
>> > =C2=A0layer AT hobart128 /c/tmp
>> > =C2=A0$ git clone git:/repo/git/acl acl.test
>> > =C2=A0Initialized empty Git repository in /c/tmp/acl.test/.git/
>> > =C2=A0remote: Counting objects: 9205, done.
>> > =C2=A0remote: Compressing objects: 100% (3300/3300), done.
>> > =C2=A0fatal: The remote end hung up unexpectedly
>> > =C2=A0fatal: early EOFs: =C2=A062% (5708/9205)
>> > =C2=A0fatal: index-pack failed
>>=20
>> I'm no git expert, but that looks to me like the remote side (where
>> the repository is stored) is experiencing the error while it's
>> preparing data for transfer, and your local git is simply reporting
>> the remote error. It also looks like the remote side is actually the
>> same machine but you're using the git:// protocol to access it without
>> specifying a remote server. I've never tried this and would have
>> expected instead to see something like:

I'm not using the git protocol.  Note the single slash.  The machine
is named `git', which is what is confusing you.  Anything of the form
"foo:/path" uses SSH, which is what this is using.

The server is hanging up, yes, but perhaps the client isn't sending
the right responses.

>> Since it looks like the remote is on the same machine as your shell,
>> do you have write access to the actual repository? If so, you could
>> run git-fsck on the repository to make sure it's intact.

No, it's on a different machine, but there is absolutely nothing wrong
with the repo.

I've tried *THREE* Windows machines now.  On all, git stops working
when cygwin is upgraded.  Works before.  Doesn't work after.  Period.

It is not a problem on the server.  There are 10+ of people using it
every minute of the day and no one has had a problem.  Ever.

>> What about other repositories, do they behave the same way, or is your
>> problem restricted to this one?

It's random (at what percentage) where it dies (with this repo).  It
randomly dies with other repos, too.

I did install 1.5.25 on the 64-bit Windows 7 machine and git works
fine.  I've sucked an enormous amount of data off the git server with
it, too, and not one problem.

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