From: Leo Famulari <leo@famulari.name>
To: 22937@debbugs.gnu.org, ludo@gnu.org, cmmarusich@gmail.com
Subject: bug#22937: guix package fails when --substitute-urls specifies an HTTPS endpoint
Date: Thu, 10 Mar 2016 16:21:33 -0500 [thread overview]
Message-ID: <20160310212133.GA8829@jasmine> (raw)
In-Reply-To: <8737rywke6.fsf@gnu.org>
On Thu, Mar 10, 2016 at 02:08:17PM +0100, Ludovic Courtès wrote:
> After some more testing and tweaks, notably with
> <https://hydra.gnunet.org> and its brand new Let’s Encrypt certificate,
> I pushed the patch as 9b7bd1b160be7c740a798c09e3b8986368b92036.
With this commit, I still get the backtrace in the original report of
this bug.
I ran `guix pull` and confirmed the changes were in ~/.config/guix/latest.
I cleared the cache at /vat/guix/substitute/cache.
Then, I updated --substitute-urls in the daemon invocation and reloaded the
daemon, and then did `guix build hello`.
Did I miss a step?
>
> I can no longer reproduce the ECONNRESET issue I mentioned for
> <https://hydra-mirror.marusich.info>, but feel free to open a new bug if
> that comes up again!
>
> For the record, the main test I used for that was:
>
> $ sudo rm -rf /var/guix/substitute/cache
> $ guix build libreoffice --no-grafts -n \
> --substitute-urls=https://hydra.gnunet.org
>
> That forces a redownload of all .narinfo files from hydra.gnunet.org,
> which involves HTTP pipelining.
>
> Anyway, thanks for giving me an incentive to address this. This was
> long overdue!
>
> Ludo’.
>
>
>
next prev parent reply other threads:[~2016-03-10 21:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 6:16 bug#22937: guix package fails when --substitute-urls specifies an HTTPS endpoint Chris Marusich
2016-03-09 22:51 ` Ludovic Courtès
2016-03-10 13:08 ` Ludovic Courtès
2016-03-10 21:21 ` Leo Famulari [this message]
2016-03-11 8:39 ` 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
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=20160310212133.GA8829@jasmine \
--to=leo@famulari.name \
--cc=22937@debbugs.gnu.org \
--cc=cmmarusich@gmail.com \
--cc=ludo@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.
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).