From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 45051@debbugs.gnu.org, pkill9 <pkill9@runbox.com>
Subject: bug#45051: Guix pull fails: `In procedure put-string: Wrong type argument in position 1 (expecting open output port): #<closed: string 7f1182257850>`
Date: Fri, 07 Oct 2022 22:58:18 -0400 [thread overview]
Message-ID: <87y1tr2f91.fsf@gmail.com> (raw)
In-Reply-To: <878sa45js2.fsf@gnu.org> ("Ludovic Courtès"'s message of "Fri, 11 Dec 2020 18:34:21 +0100")
Hi,
Ludovic Courtès <ludo@gnu.org> writes:
> Hi pkill9,
>
> pkill9 <pkill9@runbox.com> skribis:
>
>> Computing Guix derivation for 'x86_64-linux'... /@ substituter-started
>> /gnu/store/9ph7spq3b72fv4scqqzwxalb8n0wc6xn-graphviz-2.42.3-doc
>> substitute -following redirection to
>
> Could it be that your substitute URL is <https://ci.guix.info>?
>
> If so, could you try:
>
> guix build inkscape --substitute-urls=https://ci.guix.gnu.org
Given this was the actual problem, what was the underlying error that
should have appeared in the error output that would have made that
clear? A TLS cert validation error?
--
Thanks,
Maxim
prev parent reply other threads:[~2022-10-08 2:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-05 8:27 bug#45051: Guix pull fails: `In procedure put-string: Wrong type argument in position 1 (expecting open output port): #<closed: string 7f1182257850>` pkill9
[not found] ` <handler.45051.B.160715686816877.ack@debbugs.gnu.org>
2020-12-05 8:55 ` bug#45051: Acknowledgement (Guix pull fails: `In procedure put-string: Wrong type argument in position 1 (expecting open output port): #<closed: string 7f1182257850>`) pkill9
2020-12-06 2:14 ` pkill9
2020-12-11 17:34 ` bug#45051: Guix pull fails: `In procedure put-string: Wrong type argument in position 1 (expecting open output port): #<closed: string 7f1182257850>` Ludovic Courtès
2020-12-11 18:40 ` pkill9
2022-10-08 2:58 ` Maxim Cournoyer [this message]
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=87y1tr2f91.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=45051@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=pkill9@runbox.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).