From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Dan =?utf-8?B?xIxlcm3DoWs=?= Newsgroups: gmane.emacs.help Subject: Re: Error while trying to clone the Emacs git repo (via http) Date: Wed, 25 Jan 2017 10:42:48 +0100 Message-ID: <878tpzscfb.fsf@cgc-instruments.com> References: NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1485337428 9199 195.159.176.226 (25 Jan 2017 09:43:48 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 25 Jan 2017 09:43:48 +0000 (UTC) To: "help-gnu-emacs\@gnu.org list" Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Jan 25 10:43:42 2017 Return-path: Envelope-to: geh-help-gnu-emacs@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 1cWK6v-0000kJ-Q1 for geh-help-gnu-emacs@m.gmane.org; Wed, 25 Jan 2017 10:43:25 +0100 Original-Received: from localhost ([::1]:58517 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cWK71-0005L1-2q for geh-help-gnu-emacs@m.gmane.org; Wed, 25 Jan 2017 04:43:31 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:52264) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cWK6V-0005Kj-F9 for help-gnu-emacs@gnu.org; Wed, 25 Jan 2017 04:43:00 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cWK6S-0002af-Bm for help-gnu-emacs@gnu.org; Wed, 25 Jan 2017 04:42:59 -0500 Original-Received: from cgc-instruments.com ([83.169.1.125]:53662) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cWK6S-0002Zm-4x for help-gnu-emacs@gnu.org; Wed, 25 Jan 2017 04:42:56 -0500 Original-Received: from Eclipse.local (p3E9E277A.dip0.t-ipconnect.de [62.158.39.122]) by cgc-instruments.com (Postfix) with ESMTPSA id 62B33A11DB for ; Wed, 25 Jan 2017 10:42:53 +0100 (CET) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=cgc-instruments.com; b=KyiKv98f1IrGwldMqj/ZvW6/6HgJvI8FUPuXidlc6jLASvmqW4IAKImnBXGyFIZdvcRXnMtYYx8sUt9wzqCBY4KBPMqUpuTOaicB6HVVx3PDDV/hVJLfiacy8sjwAyMaOYdUOw6672nXqrwMip32jnzU/Tloetj+pcSuP8oW/YA=; h=From:To:Subject:In-Reply-To:References:Date:Message-ID:MIME-Version:Content-Type; In-Reply-To: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy] X-Received-From: 83.169.1.125 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:112159 Archived-At: It's not just you: $ git clone http://git.savannah.gnu.org/r/emacs.git/ Cloning into 'emacs'... remote: Counting objects: 780227, done. remote: aborting due to possible repository corruption on the remote side. fatal: protocol error: bad pack header I however do not know whom to tell, mayble you can find some contact info on the savannah webpage: https://savannah.gnu.org/ Dani Moncayo writes: > Hello all, > > I'm trying to clone the Emacs git repository, from a cygwin > environment, installed on my work PC. This PC connects to the > internet through a corporate proxy server. > > I've configured git to know about the proxy: > > $ git config --global http.proxy http://myproxy.mycompany.com:xxxx > > And then I've tried to clone the repo: > > $ git clone -b master git://git.sv.gnu.org/emacs.git > Cloning into 'emacs'... > fatal: unable to connect to git.sv.gnu.org: > git.sv.gnu.org[0: 208.118.235.72]: errno=Connection timed out > > My second try has been to uset the http protocol (since the proxy > probably does not allow the git protocol): > > $ git clone http://git.sv.gnu.org/r/emacs.git > Cloning into 'emacs'... > remote: Counting objects: 780227, done. > remote: aborting due to possible repository corruption on the remote side. > fatal: protocol error: bad pack header > > The above error message suggests a problem on the remote side. So, > could anyone try the above and see if it fails the same way? > > If the problem is actually on the server side, who could I report it to? > > TIA > > -- > Dani Moncayo