From: Ryan Prior via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Julien Lepiller <julien@lepiller.eu>
Cc: 45453@debbugs.gnu.org
Subject: bug#45453: Error when I try to build a package using a JSON definition
Date: Sun, 27 Dec 2020 03:19:56 +0000 [thread overview]
Message-ID: <87tus8ndey.fsf@protonmail.com> (raw)
In-Reply-To: <182B84CA-FA45-4184-A462-96B0C28D49BE@lepiller.eu>
Julien Lepiller <julien@lepiller.eu> writes:
> Anyway, in the log you attached, it seems the issue is with downloading the sources. For some reason it cannot
> resolve the github.com domain. I wonder if this is just a transient network issue on your side? Have you tried again
> later?
I did try it twice, some hours apart. And in the meanwhile, the package
defined using Guile downloads its sources and builds just fine.
> If not, it could be that the source derivation is not fixed-output. After all, the json definition doesn't specify a hash
> (it's not even an origin record). Again I'm confused by the fact that guix lets you specify packages with json, so I'm
> not sure how that part is converted to a package object. Is that
> documented?
It is in the manual (Search for "JSON representation"):
https://guix.gnu.org/manual/en/html_node/Invoking-guix-package.html
Not clear to me whether you can provide a source hash as part of a JSON
package definition.
Thanks & let me know if you turn up any other clues!
Ryan
next prev parent reply other threads:[~2020-12-27 3:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-27 0:38 bug#45453: Error when I try to build a package using a JSON definition Ryan Prior via Bug reports for GNU Guix
2020-12-27 2:28 ` Julien Lepiller
2020-12-27 3:19 ` Ryan Prior via Bug reports for GNU Guix [this message]
2020-12-27 10:40 ` Ricardo Wurmus
2020-12-27 10:38 ` Ricardo Wurmus
2020-12-27 11:08 ` Ricardo Wurmus
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=87tus8ndey.fsf@protonmail.com \
--to=bug-guix@gnu.org \
--cc=45453@debbugs.gnu.org \
--cc=julien@lepiller.eu \
--cc=rprior@protonmail.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.
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.