unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Quinten Gruenthal <quintengruenthal@gmail.com>
Cc: 41878@debbugs.gnu.org
Subject: bug#41878: Handshake Error
Date: Tue, 16 Jun 2020 10:07:51 +0200	[thread overview]
Message-ID: <87a713xwko.fsf@gnu.org> (raw)
In-Reply-To: <CAKg3DNtvP4xzdwmj_HfJUy3L5=QZy1eXynr4uxyzHPoovZ0_-Q@mail.gmail.com> (Quinten Gruenthal's message of "Mon, 15 Jun 2020 14:55:20 -0700")

Hi,

Quinten Gruenthal <quintengruenthal@gmail.com> skribis:

> Sure; though, as I mentioned before I did try again and it did work. Doing
> a pull once more I failed with:
>
> guix substitute: error: TLS error in procedure 'handshake': Error in the
> pull function.
> substitution of
> /gnu/store/k1da7bv579d8gvwdrakd9l4hxswknff2-guix-module-union failed
> guix pull: error: some substitutes for the outputs of derivation
> `/gnu/store/k2gdq7ahjaqmdgjr9xwywqpxvzazn467-guix-e07573432.drv' failed
> (usually happens due to networking issues); try `--fallback' to build
> derivation from source

Could it be that you’re on a flaky network connection?

> As with before, I was also able to succeed on a subsequent pull; but this
> error seemed to be handled better as it suggested both the cause of the
> problem and a possible solution.

If the connection is dropped, there’s little we can do, but maybe you’re
suggesting better error reporting?

Thanks,
Ludo’.

PS: Please keep the bug Cc’d.




  reply	other threads:[~2020-06-16  8:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-15 16:30 bug#41878: Handshake Error Quinten Gruenthal
2020-06-15 19:42 ` Ludovic Courtès
2020-06-15 21:55   ` Quinten Gruenthal
2020-06-16  8:07     ` Ludovic Courtès [this message]
2020-06-16  9:31       ` Bengt Richter
2020-06-16 14:57       ` Quinten Gruenthal
2020-06-17 12:03         ` Ludovic Courtès
2020-08-30 10:06 ` bug#41878: 'guix substitute' and 'guix pull' fail gracelessly on flaky networks Brendan Tildesley
2020-09-11 14:17   ` zimoun

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=87a713xwko.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=41878@debbugs.gnu.org \
    --cc=quintengruenthal@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).