Ricardo Wurmus writes:
> I’ll change this to use the Guixy license names first, and only fall
> back to SPDX names when that fails. And there should be a proper error
> message, of course.
This is now fixed with commit 5aae614868.
--
Ricardo
Hey Julien,
> I'm surprised guix builds from a json file…
it’s a little known feature. I added it a long time ago, half in jest,
half in the realization that this removes a common superficial objection
to Guix.
> If not, it could be that the source derivation is not
> fixed-output. After all,
Hi Ryan,
> Any idea what the issue here is or how I should go about debugging?
You were *so* close! The problem is with the license field.
Uncharacteristically, we are using spdx-string->license here, so “expat”
is not a valid license name. When you replace it with “MIT” it will
work.
I’ll c
Julien Lepiller 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, som
I'm surprised guix builds from a json file… doesn't it simply interpret it as a
guile file, and fails at that?
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 netwo
Hi guix! Today I wrote a package in Guile and then decided to try and
reproduce the same thing using JSON, but I hit a snag. I'm attaching
the package definition in its Guile and JSON forms, along with the error
I get when I try to build the package using `guix build -f countdown.json'.
Any idea w
