From: ludo@gnu.org (Ludovic Courtès)
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 33100@debbugs.gnu.org
Subject: bug#33100: [libssh] fatal: dumb http transport does not support shallow capabilities
Date: Sat, 20 Oct 2018 16:05:13 +0200 [thread overview]
Message-ID: <87in1w90iu.fsf@gnu.org> (raw)
In-Reply-To: <87zhv94as1.fsf@gmail.com> (Maxim Cournoyer's message of "Fri, 19 Oct 2018 22:22:38 -0400")
Hello!
Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
> guix build --check /gnu/store/f0i7bdcg1lksr9dhz0cidi3ym8r8a5wl-libssh-0.7.6-checkout.drv
> building /gnu/store/f0i7bdcg1lksr9dhz0cidi3ym8r8a5wl-libssh-0.7.6-checkout.drv...
> Initialized empty Git repository in /gnu/store/gqyjgpvzqy55dzibm59530fsx21dpiz4-libssh-0.7.6-checkout/.git/
> fatal: dumb http transport does not support shallow capabilities
On closer inspection, it seems that there’s nothing “fatal” 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.
Could you check if that’s the case for you?
berlin.guixsd.org has a substitute for this checkout, which suggests it
went fine there.
Thanks,
Ludo’.
next prev parent reply other threads:[~2018-10-20 14:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-20 2:22 bug#33100: [libssh] fatal: dumb http transport does not support shallow capabilities Maxim Cournoyer
2018-10-20 14:05 ` Ludovic Courtès [this message]
2018-10-21 3:24 ` Maxim Cournoyer
2018-10-21 19:10 ` Leo Famulari
2018-10-21 21:42 ` Maxim Cournoyer
2018-10-22 9:55 ` Ludovic Courtès
2018-10-22 17:07 ` Leo Famulari
2018-10-24 13:01 ` Maxim Cournoyer
2018-10-24 14:11 ` Ludovic Courtès
2018-10-24 14:15 ` Leo Famulari
2018-10-24 21:33 ` Ludovic Courtès
2018-10-25 1:02 ` Leo Famulari
2018-10-25 1:44 ` Maxim Cournoyer
2018-10-25 12:24 ` Ludovic Courtès
2018-10-27 2:05 ` Maxim Cournoyer
2018-10-27 14:45 ` Ludovic Courtès
2018-10-29 2:45 ` Maxim Cournoyer
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87in1w90iu.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=33100@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).