From: 白い熊 <help-guix_gnu.org@sumou.com>
To: help-guix@gnu.org
Subject: Re: Guix on Android, getaddrinfo, failure in name resolution
Date: Tue, 15 Jan 2019 17:26:02 +0000 [thread overview]
Message-ID: <77125048-BECE-4364-8B7B-01D5AB051F3B@sumou.com> (raw)
In-Reply-To: <52019D8B-FA10-413E-8776-6B594BABFFA1@sumou.com>
On January 15, 2019 5:13:26 PM UTC, "白い熊" <help-guix_gnu.org@sumou.com> wrote:
>One thing now that I'm thinking — looking at the error output — could
>this be somehow associated with https ufiticil? I see that all the
>files from all the substitutes “guix pull” is trying to download are
>from https:// locations. The first item that it's trying to download
>for the update are certificates from letsencrypt.org
>
>Could it be that hostnames are resolved fine — which they are, as I can
>ping successfully any of the sites it's trying to access — but not the
>https:// locations?
>
>Is this possible? Can it be tested? I don't think you can nslookup or
>whatever an https:// location right? What if guix can't access secure
>sites? Is that possible?
This shouldn't be the case either — I just tried connecting to letsencrypt.org on port 443 by openssl — no problem. So that's not generating the getaddrinfo error…
--
白い熊
next prev parent reply other threads:[~2019-01-15 17:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7DD810A8-FBFF-4609-981B-AD6169C384AB@sumou.com>
2019-01-15 14:39 ` Guix on Android, getaddrinfo, failure in name resolution 白い熊
2019-01-15 15:30 ` Julien Lepiller
2019-01-15 17:13 ` 白い熊
2019-01-15 17:24 ` Julien Lepiller
2019-01-15 17:53 ` 白い熊
2019-01-15 18:03 ` Julien Lepiller
2019-01-15 19:43 ` 白い熊
2019-01-16 18:33 ` 白い熊
2019-01-15 17:26 ` 白い熊 [this message]
2019-01-19 22:34 ` Ludovic Courtès
2019-01-20 14:21 ` 白い熊＠相撲道
2019-02-12 16:16 ` Ludovic Courtès
2019-02-13 18:19 ` 白い熊＠相撲道
2019-02-14 13:54 ` 白い熊＠相撲道
2019-02-14 13:55 ` 白い熊
2019-02-14 21:20 ` 白い熊＠相撲道
2019-02-15 13:06 ` 白い熊
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=77125048-BECE-4364-8B7B-01D5AB051F3B@sumou.com \
--to=help-guix_gnu.org@sumou.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.
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.