On February 14, 2019 1:54:24 PM UTC, "白い熊＠相撲道" <[email protected]>
wrote:
>Plus, I checked just to make sure — after this run, in the session,
>guix clearly can access the internet, as “guix build hello” downloads
>the hello package nicely. “guix package -i hello” fails, as it
>downloads other stuff and tries to build curl — whereby building curl
>fails on tests, as internet access tests for curl make fail.
>
>Don't know why it's not just installing “hello” and wants to install
>other stuff — substitutes are authorized, that's why “guix build”
>downloads it directly?
>
>Anyhow — this seems to be specific issue — armhf related? Why is it
>failing on “guix pull” with the name resolution failure? It seems to
>be revolving around this.
>
>Anything else I can debug?
I ran guix's ncsd on another terminal in debug mode. This is what happens when
guix fails on the letsencrypt name resolution:
Thu Feb 14 21:16:54 2019 - 15215: handle_request: request received (Version =
2) from PID 15460
Thu Feb 14 21:16:54 2019 - 15215: GETFDPW
Thu Feb 14 21:16:54 2019 - 15215: handle_request: request received (Version =
2) from PID 15460
Thu Feb 14 21:16:54 2019 - 15215: GETPWBYUID (10224)
Thu Feb 14 21:16:54 2019 - 15215: handle_request: request received (Version =
2) from PID 15589
Thu Feb 14 21:16:54 2019 - 15215: GETFDGR
Thu Feb 14 21:16:54 2019 - 15215: handle_request: request received (Version =
2) from PID 15589
Thu Feb 14 21:16:54 2019 - 15215: GETGRBYNAME (guixbuild)
Thu Feb 14 21:16:56 2019 - 15215: handle_request: request received (Version =
2) from PID 15595
Thu Feb 14 21:16:56 2019 - 15215: GETFDHST
Thu Feb 14 21:16:56 2019 - 15215: handle_request: request received (Version =
2) from PID 15595
Thu Feb 14 21:16:56 2019 - 15215: GETFDSERV
Thu Feb 14 21:16:56 2019 - 15215: handle_request: request received (Version =
2) from PID 15595
Thu Feb 14 21:16:56 2019 - 15215: GETSERVBYNAME (https/tcp)
Thu Feb 14 21:16:56 2019 - 15215: handle_request: request received (Version =
2) from PID 15595
Thu Feb 14 21:16:56 2019 - 15215: GETAI (letsencrypt.org)
So, it seems it's resolving. What could be the problem?
--
白い熊＠相撲道
