From: Alex Kost <alezost@gmail.com>
To: guix-devel@gnu.org
Subject: Re: Guix Pull Failure
Date: Tue, 30 Sep 2014 14:06:55 +0400 [thread overview]
Message-ID: <87ppedbeww.fsf@gmail.com> (raw)
In-Reply-To: <87wq8lbk65.fsf@gmail.com> (Alex Kost's message of "Tue, 30 Sep 2014 12:13:22 +0400")
This message is the answer to myself, so please ignore it and the
previous one.
Alex Kost (2014-09-30 12:13 +0400) wrote:
> Alex Sassmannshausen (2014-09-30 11:40 +0400) wrote:
>
>> Hello,
>>
>> When doing `guix pull` this morning it consistently fails with:
>>
>> ---8<-------->8------------
>> copying and compiling to '/gnu/store/gjb8zsijysxfcizw1374k5hcadd3x7mf-guix-latest'...
>> compiling... 8.7% of 335 filesERROR: no code for module (json)
>> ---8<-------->8------------
>>
>> It does this even after I have installed guile-json. Could this be due
>> to the recent addition of the PyPi Importer?
>
> Indeed, I thought it would be fixed after
> <http://git.savannah.gnu.org/cgit/guix.git/commit/?id=85054932667d57224dde1d18c381d7d7c0a95dd4>,
> but it is not.
My mistake: this commit couldn't affect “guix pull” in any way.
For some reason I thought that “guix pull” does configure+make process
but it just copies and compiles *.scm files from "gnu/" and "guix/"
directories (and a couple of other scm-files).
And now (with Ludovic's commit 6d7328b), "guile-json" package is being
built (or downloaded from hydra) by “guix pull” before the main
"pulling" process.
Sorry for the noize and thanks Ludovic for a "virtual help" (I looked at
the source of “guix/scripts/pull.scm” and “guix/build/pull.scm” after
your commit).
next prev parent reply other threads:[~2014-09-30 10:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 7:40 Guix Pull Failure Alex Sassmannshausen
2014-09-30 8:13 ` Alex Kost
2014-09-30 10:06 ` Alex Kost [this message]
2014-09-30 8:13 ` Ludovic Courtès
2014-09-30 8:40 ` Alex Sassmannshausen
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=87ppedbeww.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=guix-devel@gnu.org \
/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.