From: Stephen Scheck <singularsyntax@gmail.com>
To: Christopher Baines <mail@cbaines.net>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Name resolution failures during build
Date: Fri, 20 Nov 2020 16:15:49 -0500 [thread overview]
Message-ID: <CAKjnHz06CNROkEv7=1Zq0B=88RnNRg1kZBpOKeUe3bL961QCtA@mail.gmail.com> (raw)
In-Reply-To: <87h7pjkb60.fsf@cbaines.net>
Sure - I understand the reasoning - but this is an open-source project with
its own build system that I'm trying to package, and I believe its build
system depends on network access (it's Go-based, and my understanding is
that the Go dependency model relies on access to numerous external Git
repos). Is such a project unsupportable by Guix?
On Fri, Nov 20, 2020 at 3:47 PM Christopher Baines <mail@cbaines.net> wrote:
>
> Stephen Scheck <singularsyntax@gmail.com> writes:
>
> > I'm getting the following error when I try to install a package I'm
> working
> > on:
> >
> > go: github.com/BurntSushi/toml@v0.3.1: Get "
> > https://proxy.golang.org/github.com/%21burnt%21sushi/toml/@v/v0.3.1.mod
> ":
> > dial tcp: lookup proxy.golang.org on [::1]:53: read udp
> > [::1]:43973->[::1]:53: read: connection refused
> >
> > It uses `gnu-build-system`. Is there some package that needs to be added
> to
> > the build inputs for ordinary name resolution to work?
>
> To ensure that builds don't depend on the network, the build processes
> don't have network access.
>
> This could mean you're missing something in the build environment (an
> input), or that there's an input being ignored (and the network is being
> used to try and fetch it).
>
> Does that make sense?
>
> Chris
>
next prev parent reply other threads:[~2020-11-20 21:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 20:09 Name resolution failures during build Stephen Scheck
2020-11-20 20:47 ` Christopher Baines
2020-11-20 21:15 ` Stephen Scheck [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-11-20 21:34 Christopher Baines
2020-11-20 22:55 ` Stephen Scheck
2020-11-21 19:22 ` Efraim Flashner
2020-11-21 20:38 ` raingloom
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='CAKjnHz06CNROkEv7=1Zq0B=88RnNRg1kZBpOKeUe3bL961QCtA@mail.gmail.com' \
--to=singularsyntax@gmail.com \
--cc=help-guix@gnu.org \
--cc=mail@cbaines.net \
/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).