X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 	tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <10711.1261594527@gemini.franz.com>
References: <10711 DOT 1261594527 AT gemini DOT franz DOT com>
Date: Wed, 30 Dec 2009 10:50:09 +1300
Message-ID: <db95995b0912291350y6e0bb513i99279a82fa604f50@mail.gmail.com>
Subject: Re: git stopped working with 1.7.1
From: David Antliff <david DOT antliff AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
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

On Thu, Dec 24, 2009 at 07:55, Kevin Layer <layer AT franz DOT com> wrote:
> =A0layer AT hobart128 /c/tmp
> =A0$ git clone git:/repo/git/acl acl.test
> =A0Initialized empty Git repository in /c/tmp/acl.test/.git/
> =A0remote: Counting objects: 9205, done.
> =A0remote: Compressing objects: 100% (3300/3300), done.
> =A0fatal: The remote end hung up unexpectedly
> =A0fatal: early EOFs: =A062% (5708/9205)
> =A0fatal: index-pack failed

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:

$ git clone git://localhost/repo/git/acl acl.test
or
$ git clone <some-path>/repo/git/acl acl.test

I.e. there's something about your command that *I* don't understand.
It's probably perfectly fine though, and the problem is with me.

Are you intending to clone a repository on the same machine but via
the git:// protocol? What if you just do this instead:

$ git clone <some-path>/repo/git/acl acl.test

Do you get the same error?

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.

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

-- David.

--
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