From: Simon Tournier <zimon.toutoune@gmail.com>
To: Zach Philipchook <z.pilipchuk@gmail.com>, help-guix@gnu.org
Subject: Re: "Could not resolve host" while using git-fetch
Date: Mon, 16 Jan 2023 11:42:22 +0100 [thread overview]
Message-ID: <87ilh6vjzl.fsf@gmail.com> (raw)
In-Reply-To: <CACXroRs5niKHM-DaVGrzp2rXcc1pxABrtOdQ2xUKjSGXvsQMLQ@mail.gmail.com>
Hi,
On sam., 14 janv. 2023 at 01:31, Zach Philipchook <z.pilipchuk@gmail.com> wrote:
> The package definition: https://pastebin.com/UJEm396s
> guix command I'm executing: `guix package --manifest=manifest.scm -v3`
This works for me.
> guix log: https://pastebin.com/NYbH8iGX
Hum, it appears something is wrong with your network and Guix. Because
the last failure is about SWH and I get:
--8<---------------cut here---------------start------------->8---
Trying to download from Software Heritage...
SWH: found revision 83471599284b2a23027b9ab4514684a6eeb08a19 with directory at 'https://archive.softwareheritage.org/api/1/directory/1605408342b2ada130d73056c8ef800f57e42879/'
--8<---------------cut here---------------end--------------->8---
Well, I do not what could be useful to debug your issue. Something is
missing configured between your network and Guix. And I do not think
the issue is related to nscd.
Are you running Guix System or Guix on foreign distro?
Cheers,
simon
PS:
Unrelated, please note:
--8<---------------cut here---------------start------------->8---
r:sha256 hash mismatch for /gnu/store/blfa1pp705gq42fmsbvjwp0jbbr59dfc-sfgui--checkout:
expected hash: 17pjvprmdrx4h6bb1hhc98w9qi6ki7yl57f090n9kbhswxqfs7s3
actual hash: 0x4c79hjgzm8hxkchi5zxlc1fi5jikxddmlzb6bpyym4rjrvhm6z
--8<---------------cut here---------------end--------------->8---
prev parent reply other threads:[~2023-01-16 11:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 23:31 "Could not resolve host" while using git-fetch Zach Philipchook
2023-01-16 10:42 ` Simon Tournier [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=87ilh6vjzl.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=help-guix@gnu.org \
--cc=z.pilipchuk@gmail.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.
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).