From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Bob Proulx Newsgroups: gmane.emacs.help Subject: Re: Error while trying to clone the Emacs git repo (via http) Date: Thu, 26 Jan 2017 12:08:53 -0700 Message-ID: <20170126115415341017787@bob.proulx.com> References: <83h94n2kyh.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: blaine.gmane.org 1485457783 6837 195.159.176.226 (26 Jan 2017 19:09:43 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 26 Jan 2017 19:09:43 +0000 (UTC) User-Agent: NeoMutt/20170113 (1.7.2) Cc: help-gnu-emacs@gnu.org To: Eli Zaretskii Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Thu Jan 26 20:09:38 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 1cWpQK-0000xs-Tn for geh-help-gnu-emacs@m.gmane.org; Thu, 26 Jan 2017 20:09:33 +0100 Original-Received: from localhost ([::1]:40672 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cWpQQ-0005Kr-7j for geh-help-gnu-emacs@m.gmane.org; Thu, 26 Jan 2017 14:09:38 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38880) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cWpPs-0005KZ-OZ for help-gnu-emacs@gnu.org; Thu, 26 Jan 2017 14:09:09 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cWpPn-0006xz-GF for help-gnu-emacs@gnu.org; Thu, 26 Jan 2017 14:09:04 -0500 Original-Received: from havoc.proulx.com ([96.88.95.61]:46927) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cWpPh-0006xE-VZ; Thu, 26 Jan 2017 14:08:54 -0500 Original-Received: from joseki.proulx.com (localhost [127.0.0.1]) by havoc.proulx.com (Postfix) with ESMTP id 92F67524; Thu, 26 Jan 2017 12:08:53 -0700 (MST) Original-Received: from hysteria.proulx.com (hysteria.proulx.com [192.168.230.119]) by joseki.proulx.com (Postfix) with ESMTP id 5BBAC217E0; Thu, 26 Jan 2017 12:08:53 -0700 (MST) Original-Received: by hysteria.proulx.com (Postfix, from userid 1000) id 4625F2DC5F; Thu, 26 Jan 2017 12:08:53 -0700 (MST) Mail-Followup-To: Eli Zaretskii , help-gnu-emacs@gnu.org Content-Disposition: inline In-Reply-To: <83h94n2kyh.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 96.88.95.61 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:112170 Archived-At: Eli Zaretskii wrote: > Dani Moncayo wrote: > > 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 > > AFAIK, Savannah doesn't (yet) support Git via HTTPS. If there is a problem with http and if the problem is on the server then there should be no difference between http and https. They both provide exactly the same files. It is the same web server serving the same files. Shouldn't be any difference. Using http and an http proxy however may be a source of additional problems however because I have chased down many problems over the years that were due only to corruption caused by the proxy. I don't know why but corporate http proxies seem to have a high error rate well above any reasonable expectation. These days, in other work, if I need any type of reliability, or any type of web form, then I always force https in order to avoid use of corrupting bad proxies, in order to avoid those problems. In some ways it is a shame that bad proxies have destroyed it for the good ones. But in other developments we are trying to encrypt everything and so proxies either good or bad have been deprecated. Perhaps counter-intuitively the problems with git-daemon and shallow checkouts have prevented me releasing https to production. Or rather I did previously release git to production. Thought everything was working okay. Announced it. Hadn't said anything about https being available "just in case" there were problems because it isn't available on the old server. Then after a while started receiving problem reports. Argh! I had to recall git back to the old server while working through the problems. Was glad I hasn't said anything about the availability of https. Thrashed for a bit. Decided to push through the other version control services in order to get as much as possible off of the old server. Now I am back to trying to resolve the git-daemon problem with shallow checkouts. Unfortunately all git services are tied to the git.savannah.gnu.org dns name and so it is all of it or none of it at the same time. Just to give some visibility into the happenings for those not following along on the Savannah mailing lists. :-) Bob