From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: bug#33100: [libssh] fatal: dumb http transport does not support shallow capabilities Date: Sun, 21 Oct 2018 15:10:18 -0400 Message-ID: <20181021191018.GA18445@jasmine.lan> References: <87zhv94as1.fsf@gmail.com> <87in1w90iu.fsf@gnu.org> <87va5w3rtj.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="r5Pyd7+fXNt84Ff3" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:57973) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gEJ7z-0004N1-EB for bug-guix@gnu.org; Sun, 21 Oct 2018 15:11:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gEJ7u-0001Un-LQ for bug-guix@gnu.org; Sun, 21 Oct 2018 15:11:07 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:58552) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gEJ7u-0001Ub-Fw for bug-guix@gnu.org; Sun, 21 Oct 2018 15:11:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gEJ7u-00045H-70 for bug-guix@gnu.org; Sun, 21 Oct 2018 15:11:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: Content-Disposition: inline In-Reply-To: <87va5w3rtj.fsf@gmail.com> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: 33100@debbugs.gnu.org, maxim.cournoyer@gmail.com --r5Pyd7+fXNt84Ff3 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Oct 20, 2018 at 11:24:24PM -0400, Maxim Cournoyer wrote: > ludo@gnu.org (Ludovic Court=C3=A8s) writes: > > On closer inspection, it seems that there=E2=80=99s nothing =E2=80=9Cfa= tal=E2=80=9D here: if you > > let it run for a while (1 or 2 minutes), it ends up silently cloning the > > whole repo and the derivation build eventually succeeds. >=20 > It did end up working fine, although it took a large amout of time for > doing what seems to be a checkout (4 min 46 s). I did some experiments > and this is really the time it took to do a full clone of the libssh > project. Great, you figured it out :) More explanation: Git has a few different server protocols: git, dumb HTTP, smart HTTP, and SSH: https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols The dumb HTTP protocol is slow and does not show any progress status or other informative message while it works, but if you monitor your network traffic you can see it working. For obvious reasons, it's rare to see the dumb HTTP protocol deployed nowadays, but you may still find it on legacy installations. --r5Pyd7+fXNt84Ff3 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAlvMzxcACgkQJkb6MLrK fwhhIBAAmTI0bBzOCc/7cZ7QeiqvvhdijEbhVi9lEejD7We7LPqNxlwOvabF8xqo 5RUvXl1EzsQNgZ+eOiJvd5UmtTzeFHJ40dSicN+7EGyK2hzCt43IroRjKf51Vjl2 f7zPqSldMGs6ZV6EEjFvkERo5V6A7Tg3fLVO4ivNucnJbmK/FgL/OY/7SOWFQwTS nqPLKav98zo58LNZRpyEPm4uxkkOW/w8svPuRRxIbC82ris8YueIpUk7CHfyqwJW foVSurk3OsGECqOiicY0xNkSl5+qAKsnu3OLdUJSauPW74Y18MCD0foy4DrGyFWz fCNgNbts8G+KThPjb3VGskoUqvEjaM9egAfcW1b9Sk+LkjIknfO+fdpPcjjL3PrA 1EiClmc8KqonzhSL8RlFx0fHpYGza+Z6c7n1R6gJH332BcsO0nJTQpVi4l1UsFBO U5Xp3fXGdF39lQSCvpAdePFJWUrY14S5Mby3pTOgIawB0uH1Jx5aoj9AY/Mw2fUz xFoRt/VyqSKoWLDCQGyORAYVlLeJPgEltIgysu7Nw7p1VV0R5RQc+U1/TYHeUawc 3cvrEb3SK3UxsC/g7ZWTrxOJH/gJT+VUYquZjzACsC0efDkgd5UoAnbe1rN3JJFn KNL62ROCQZaFkvdc69XO8PGMydeykvTskn+lnAFWXfKfgoO1pz4= =cHdi -----END PGP SIGNATURE----- --r5Pyd7+fXNt84Ff3--