From: "Ludovic Courtès" <ludo@gnu.org>
To: Caleb Ristvedt <caleb.ristvedt@cune.org>
Cc: guix-devel@gnu.org
Subject: Re: 02/09: guix: store: Make register-items transactional, register drv outputs
Date: Thu, 04 Apr 2019 18:20:44 +0200 [thread overview]
Message-ID: <87a7h5rbc3.fsf@gnu.org> (raw)
In-Reply-To: <87sgv11ujj.fsf@cune.org> (Caleb Ristvedt's message of "Mon, 01 Apr 2019 12:53:36 -0500")
Caleb Ristvedt <caleb.ristvedt@cune.org> skribis:
> As we found out on IRC yesterday, https://bugs.gnu.org/15602 is causing
> this to fail. If I understand correctly, the workaround involves trying
> to make sure that modules that use (guix memoization) are compiled
> before (guix memoization) is (and it turns out that once that's solved
> the same issue occurs with (guix config)). Considering that the
> module-import-compiled builders just do a depth-first-search for scheme
> source files ordered alphabetically, that's a bit tricky. I ended up
> making a dummy module, (gnu build dummy), that does nothing but use
> (guix config) and (guix memoization), and the tests now pass.
I finally got around to fixing it in
a31174e896047e6a0f42b69db331fdeebb3cc995.
The kludge is no longer needed!
Ludo’.
next prev parent reply other threads:[~2019-04-04 16:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190204192241.15758.66035@vcs0.savannah.gnu.org>
[not found] ` <20190204192243.A58BA20B45@vcs0.savannah.gnu.org>
2019-02-04 23:14 ` 01/09: patches: honor NIX_STORE in site.py Ludovic Courtès
[not found] ` <20190204192243.D1BD820B84@vcs0.savannah.gnu.org>
2019-02-09 22:09 ` 02/09: guix: store: Make register-items transactional, register drv outputs Ludovic Courtès
2019-02-13 8:43 ` Caleb Ristvedt
2019-03-06 13:14 ` Ludovic Courtès
2019-04-01 17:53 ` Caleb Ristvedt
2019-04-01 19:43 ` Ludovic Courtès
2019-04-04 16:20 ` Ludovic Courtès [this message]
2019-04-06 23:57 ` Caleb Ristvedt
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=87a7h5rbc3.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=caleb.ristvedt@cune.org \
--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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).