From: "Todor Kondić" <tk.code@protonmail.com>
To: "help-guix\\@gnu.org" <help-guix@gnu.org>
Subject: Re: Updating substitute error: TLS error in the push function
Date: Thu, 18 Feb 2021 12:18:22 +0000 [thread overview]
Message-ID: <trDM23fUPE3QVCnwch1cRUFLyGB3jI1qnbHrGJTBspgHiha2DVWrUQUrTuHJDRqYS5We8_OHRKKxGtl_jtoVynwWlqe0T0Oebq4xaU8yfGM=@protonmail.com> (raw)
In-Reply-To: <2ef35fed4378696d00d9e283c3c85fa9@dismail.de>
[I know some people are going to grumble because of top posting: sorry!]
Yes, I did. I pulled a few times during last and this week.
The recompilation hit because of an unrelated matter. I did a very evil thing: evaluated my own version of the net-base package inside the module where net-base resides.
This dirty technique does work for services tho ;)
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Wednesday, 17 February 2021 20:36, <jbranso@dismail.de> wrote:
> Hmmmm, Have you tried updating guix recently?
>
> February 16, 2021 2:47 AM, "Todor Kondić" tk.code@protonmail.com wrote:
>
> > I keep getting this error,
> >
> > substitute: updating substitutes from 'https://ci.guix.gnu.org'... 0.0%guix substitute: error: TLS
> > error in procedure 'write_to_session_record_port': Error in the push function.
> >
> > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> >
> > while `sudo guix system reconfigure ...`.
> > Then I get into the whole compilation cycle.
> > Guix version:
> > 61361ef2646cc59f18fd1d33d9d13348930255b7
next prev parent reply other threads:[~2021-02-18 12:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 7:46 Updating substitute error: TLS error in the push function Todor Kondić
2021-02-17 19:36 ` jbranso
2021-02-18 12:18 ` Todor Kondić [this message]
2021-02-18 15:16 ` Joshua Branson
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='trDM23fUPE3QVCnwch1cRUFLyGB3jI1qnbHrGJTBspgHiha2DVWrUQUrTuHJDRqYS5We8_OHRKKxGtl_jtoVynwWlqe0T0Oebq4xaU8yfGM=@protonmail.com' \
--to=tk.code@protonmail.com \
--cc=help-guix@gnu.org \
/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.
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).