DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:content-type:content-transfer-encoding; q=dns; s=default; b=lfu
	BVvB0azHPGweUgickKlSfO6jl8Z+SqHMBUZxWFxW5bu7/Q0j77biiqTtfu9iQN4i
	gg8d2E0QuJjHO6bNid8nZ1pTSkHrHUTx9LEzy8Za/o1JMAG7KlJenTg0TorzcJ8I
	WJR9bMylvlWCdD2cdLbMdn7whQaSZte20n1shirA=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <5502264B.3050803@lysator.liu.se>
Date: Fri, 13 Mar 2015 00:50:35 +0100
From: Peter Rosin <peda AT lysator DOT liu DOT se>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: git fails to push
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Hi!

For a long time, I have been suffering from git problems when I
push to our server. I have been hoping that it should just
magically go away with some update or something, but I guess not.
Basically, I have to push several times for it to "take".
Like this:

$ git push origin
Counting objects: 23, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (23/23), done.
Writing objects: 100% (23/23), 2.43 KiB | 0 bytes/s, done.
Total 23 (delta 18), reused 0 (delta 0)
remote: error: failed to read delta-pack base object d453336d3439f7eccafc5a3ff2a09b397b8df026
error: unpack failed: unpack-objects abnormal exit
To file:///cygdrive/x/some path/with spaces/repo.git
 ! [remote rejected] master -> master (unpacker error)
error: failed to push some refs to 'file:///cygdrive/x/some path/with spaces/repo.git'

$ git push origin
Counting objects: 23, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (23/23), done.
Writing objects: 100% (23/23), 2.43 KiB | 0 bytes/s, done.
Total 23 (delta 18), reused 0 (delta 0)
remote: error: failed to read delta-pack base object c36a8985dca3440c50727b70e47011e8feaea37a
error: unpack failed: unpack-objects abnormal exit
To file:///cygdrive/x/some path/with spaces/repo.git
 ! [remote rejected] master -> master (unpacker error)
error: failed to push some refs to 'file:///cygdrive/x/some path/with spaces/repo.git'

$ git push origin
Counting objects: 23, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (23/23), done.
Writing objects: 100% (23/23), 2.43 KiB | 0 bytes/s, done.
Total 23 (delta 18), reused 0 (delta 0)
To file:///cygdrive/x/some path/with spaces/repo.git
   c67a7ac..584c601  master -> master

In this instance, it took three attempts, but that's of course not
always the case. Sometimes it works without retries. I have the
feeling that it depends on what is pushed; if I push the same
changes to two different repos, the failures are on the same packs.

What is not seen in the above capture is the progress reports during
the push. When a failed push is retried, it progresses pretty quickly
up to *and including* the failed pack. Then it slows down to the normal
pace (sluggish link).

This tells me that the failed pack hasn't really failed, it's just
some check that has a false positive for some mysterious reason.

It happens on two quite different machines. It might be some issue
with the remote server (/cygdrive/x) though, since that is a common
denominator?

Happens on both 32- and 64-bit Cygwin.

I don't think the "some path/with spaces"-part is affecting things,
since it sort-of works.

Any suggestions?

Cheers,
Peter

who has grown the habit of doing "while ! git push origin; do :; done"...

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