git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Torsten Bögershausen" <tboegi@web.de>
To: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
Cc: "Douglas Mencken" <dougmencken@gmail.com>,
	git@vger.kernel.org, "Torsten Bögershausen" <tboegi@web.de>
Subject: Re: [regression] Newer gits cannot clone any remote repos
Date: Tue, 13 Nov 2012 21:51:43 +0100	[thread overview]
Message-ID: <50A2B2DF.1080704@web.de> (raw)
In-Reply-To: <50A2978D.6080805@ramsay1.demon.co.uk>

On 13.11.12 19:55, Ramsay Jones wrote:
> Douglas Mencken wrote:
>> *Any* git clone fails with:
>>
>> fatal: premature end of pack file, 106 bytes missing
>> fatal: index-pack failed
>>
>> At first, I tried 1.8.0, and it failed. Then I tried to build 1.7.10.5
>> then, and it worked. Then I tried 1.7.12.2, but it fails the same way
>> as 1.8.0.
>> So I decided to git bisect.
>>
>> b8a2486f1524947f232f657e9f2ebf44e3e7a243 is the first bad commit
>> ``index-pack: support multithreaded delta resolving''
> 
> This looks like the same problem I had on cygwin, which lead to
> commit c0f86547c ("index-pack: Disable threading on cygwin", 26-06-2012).
> 
> I didn't notice which platform you are on, but maybe you also have a
> thread-unsafe pread()? Could you try re-building git with the
> NO_THREAD_SAFE_PREAD build variable set?
> 
> HTH.
> 
> ATB,
> Ramsay Jones

This is interesting.
I had the same problem on a PowerPC 
(Old PowerBook G4 running Linux).

Using NO_THREAD_SAFE_PREAD helped, thanks for the hint.
(After recompiling without NO_THREAD_SAFE_PREAD I could clone
from this machine again, so the problem is not really reproducable)

Are there more people running PowerPC (on the server side) ?
/Torsten

 

  parent reply	other threads:[~2012-11-13 20:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-12 16:32 [regression] Newer gits cannot clone any remote repos Douglas Mencken
2012-11-12 17:12 ` Kevin
2012-11-12 19:35   ` Douglas Mencken
     [not found] ` <CAO54GHA=r8WUK3okm2imVkoB=SuZ=3o+wwdwLr_rmPXhdFzG_g@mail.gmail.com>
2012-11-12 17:13   ` Douglas Mencken
2012-11-13 18:55 ` Ramsay Jones
2012-11-13 19:55   ` Douglas Mencken
2012-11-13 20:33     ` Douglas Mencken
2012-11-15 12:51     ` Nguyen Thai Ngoc Duy
2012-11-15 18:55     ` Ramsay Jones
2012-11-13 20:51   ` Torsten Bögershausen [this message]
2012-11-13 22:36     ` Andreas Schwab
2012-11-14 16:19       ` Douglas Mencken
2012-11-14 16:32         ` Andreas Schwab
2012-11-14 18:01           ` Douglas Mencken
2012-11-14 23:15             ` Andreas Schwab
2012-11-15 19:17     ` Ramsay Jones
2012-11-21 19:20       ` Douglas Mencken

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50A2B2DF.1080704@web.de \
    --to=tboegi@web.de \
    --cc=dougmencken@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=ramsay@ramsay1.demon.co.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).