all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: guix-devel@gnu.org, jcguu95 <jcguu95@gmail.com>, 47867@debbugs.gnu.org
Subject: Re: bug#47867: [1.2.1 pre-release testing] substitute downloading and TLS errors
Date: Sun, 18 Apr 2021 12:15:47 +0200	[thread overview]
Message-ID: <87a6pvnbjg.fsf@gnu.org> (raw)
In-Reply-To: <20210418093856.a6r2zqw2gks56dg5@pelzflorian.localdomain> (pelzflorian@pelzflorian.de's message of "Sun, 18 Apr 2021 11:38:56 +0200")

Hi Florian,

"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:

> On Fri, Apr 16, 2021 at 10:40:55PM -0500, jcguu95 wrote:
>>    2.2. Unexpected failure
>> 
>>    After running `guix system init /mnt/etc/config.scm /mnt' for 5 to 10
>>    minutes, I got the error
>> 
>>    ,----
>>    |    substitute: updating substitutes from 'https://ci.guix.gnu.org'... 0.0%guix substitute: error: TSL error in procedure 'write_to_session_port': Resource temporarily unavailable, try again.
>>    | 
>>    |    guix system: error: `/gnu/store/1nmwil4cs...vc2p-guix-1.2.0-21.4dff6ec/bin/guix substitute` died unexpectedly
>>    |    root@gnu ~# _
>>    `----
>> 
>>    Retrying it did resolve the problem. And I got a working guix system
>>    out of it :)
>
> I’ve got the same TLS error (though the procedure for me is
> ‘write_to_session_record_port’.
>
> I needed to restart the installer at the last step, this stopped while
> downloading enlightenment with no error but it does not continue.

Was this in a VM?  Could it be that networking was unstable (e.g., you
were running this over a flaky WiFi connection)?  How reproducible is
this?  Any tips on how to reproduce it?

I did a full bare-bones OS install in a VM, which went fine, but maybe
that’s not representative of your setup.

Thanks,
Ludo’.


  parent reply	other threads:[~2021-04-18 10:16 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-17  3:40 1.2.1 pre-release testing jcguu95
2021-04-17  5:43 ` Leo Famulari
2021-04-17 11:35   ` GIT_EXEC_PATH " François
2021-04-17 17:24     ` Leo Famulari
2021-04-17 18:07       ` François
2021-04-17  9:32 ` pelzflorian (Florian Pelz)
2021-04-17 12:58   ` Guu, Jin-Cheng
2021-04-17 13:17     ` pelzflorian (Florian Pelz)
2021-04-17 17:27 ` Leo Famulari
2021-04-17 21:57   ` pelzflorian (Florian Pelz)
2021-04-18  0:09     ` Guu, Jin-Cheng
2021-04-18  0:19       ` Leo Famulari
2021-04-18  8:57       ` pelzflorian (Florian Pelz)
2021-04-18  9:38 ` [1.2.1 pre-release testing] substitute downloading and TLS errors pelzflorian (Florian Pelz)
2021-04-18  9:44   ` bug#47867: " pelzflorian (Florian Pelz)
2021-04-18  9:48     ` pelzflorian (Florian Pelz)
2021-04-18  9:57       ` pelzflorian (Florian Pelz)
2021-04-18 10:15   ` Ludovic Courtès [this message]
2021-04-18 11:33     ` pelzflorian (Florian Pelz)
2021-04-18 12:10       ` pelzflorian (Florian Pelz)
2021-04-19  8:05         ` pelzflorian (Florian Pelz)
2021-04-19  8:22           ` pelzflorian (Florian Pelz)
2021-04-19 11:02           ` pelzflorian (Florian Pelz)
2021-04-20  1:21           ` pelzflorian (Florian Pelz)
2021-04-20 15:27             ` pelzflorian (Florian Pelz)
2021-04-20 17:03               ` pelzflorian (Florian Pelz)
2021-04-20 18:00                 ` Leo Famulari
2021-04-20 19:41                   ` pelzflorian (Florian Pelz)
2021-04-20 22:38               ` Ludovic Courtès
2021-04-21 20:17                 ` pelzflorian (Florian Pelz)
2021-04-23  9:19                   ` Ludovic Courtès
2021-04-23 14:07                     ` pelzflorian (Florian Pelz)
2021-04-24 17:13                       ` Ludovic Courtès
2021-04-25  0:20                         ` pelzflorian (Florian Pelz)
2021-06-21 19:18                         ` Ludovic Courtès

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a6pvnbjg.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=47867@debbugs.gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=jcguu95@gmail.com \
    --cc=pelzflorian@pelzflorian.de \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.