all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Karl Fogel <kfogel@red-bean.com>, Zack Weinberg <zackw@panix.com>
Cc: emacs-devel@gnu.org
Subject: Re: Can't clone emacs.git
Date: Wed, 22 Mar 2017 15:16:08 -0700	[thread overview]
Message-ID: <53f0ea22-b25a-bb2f-697c-37ab4abca59c@cs.ucla.edu> (raw)
In-Reply-To: <87o9wtxcev.fsf@klen>

On 03/22/2017 01:51 PM, Karl Fogel wrote:
> Zack Weinberg<zackw@panix.com>  writes:
>> $ git clone -b master git://git.sv.gnu.org/emacs.git
>> Cloning into 'emacs'...
>> remote: Counting objects: 786327, done.
>> remote: Compressing objects: 100% (142709/142709), done.
>> error: inflate: data stream error (invalid stored block lengths)
>> fatal: pack has bad object at offset 129019143: inflate returned -3
>> fatal: index-pack failed
>>
>> Anyone else getting this?
> I think you've probably run into this problem:
>
>    http://www.rants.org/2016/04/redis_github_clone_error/

I'm not observing the problem even with a ~/.gitconfig file that 
contains the "fsckObjects = true" line mentioned in that web page, so it 
sounds like it's some sort of network or hardware problem rather than 
overly aggressive checking.

Last year when we had this problem it was a bad SSD in a RAID system on 
Savannah; see 
<http://lists.gnu.org/archive/html/savannah-hackers/2016-05/msg00081.html>. 
Zack, you may want to contact the FSF sysadmins and send them details. 
It could be that you have contacted a bad clone while the rest of us 
have been lucky enough to contact good ones.




  reply	other threads:[~2017-03-22 22:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-22 11:44 Can't clone emacs.git Zack Weinberg
2017-03-22 14:52 ` Philippe Vaucher
2017-03-22 20:51 ` Karl Fogel
2017-03-22 22:16   ` Paul Eggert [this message]
2017-03-23 11:51 ` Zack Weinberg

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=53f0ea22-b25a-bb2f-697c-37ab4abca59c@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=kfogel@red-bean.com \
    --cc=zackw@panix.com \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.