From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Paul Eggert Newsgroups: gmane.emacs.devel Subject: Re: Can't clone emacs.git Date: Wed, 22 Mar 2017 15:16:08 -0700 Organization: UCLA Computer Science Department Message-ID: <53f0ea22-b25a-bb2f-697c-37ab4abca59c@cs.ucla.edu> References: <87o9wtxcev.fsf@klen> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: blaine.gmane.org 1490221015 3102 195.159.176.226 (22 Mar 2017 22:16:55 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 22 Mar 2017 22:16:55 +0000 (UTC) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 Cc: emacs-devel@gnu.org To: Karl Fogel , Zack Weinberg Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Mar 22 23:16:50 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cqoYe-0008JH-TL for ged-emacs-devel@m.gmane.org; Wed, 22 Mar 2017 23:16:45 +0100 Original-Received: from localhost ([::1]:53499 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cqoYk-0008Bu-RC for ged-emacs-devel@m.gmane.org; Wed, 22 Mar 2017 18:16:50 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:41802) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cqoYB-0008Bm-FC for emacs-devel@gnu.org; Wed, 22 Mar 2017 18:16:16 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cqoY8-0000us-6I for emacs-devel@gnu.org; Wed, 22 Mar 2017 18:16:15 -0400 Original-Received: from zimbra.cs.ucla.edu ([131.179.128.68]:52574) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cqoY7-0000ui-WE for emacs-devel@gnu.org; Wed, 22 Mar 2017 18:16:12 -0400 Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 3DB411600B6; Wed, 22 Mar 2017 15:16:10 -0700 (PDT) Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id Xvh3t-De_8nN; Wed, 22 Mar 2017 15:16:09 -0700 (PDT) Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 35BF41600B9; Wed, 22 Mar 2017 15:16:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at zimbra.cs.ucla.edu Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id Ecxo31muFw5d; Wed, 22 Mar 2017 15:16:09 -0700 (PDT) Original-Received: from Penguin.CS.UCLA.EDU (Penguin.CS.UCLA.EDU [131.179.64.200]) by zimbra.cs.ucla.edu (Postfix) with ESMTPSA id 188F31600B6; Wed, 22 Mar 2017 15:16:09 -0700 (PDT) In-Reply-To: <87o9wtxcev.fsf@klen> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy] X-Received-From: 131.179.128.68 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:213257 Archived-At: On 03/22/2017 01:51 PM, Karl Fogel wrote: > Zack Weinberg 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 . 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.