From: Ricardo Wurmus <rekado@elephly.net>
To: gwl-devel@gnu.org
Subject: Re: workflow dependencies are not built
Date: Wed, 12 Jun 2019 14:40:56 +0200 [thread overview]
Message-ID: <874l4v9dt3.fsf@elephly.net> (raw)
In-Reply-To: <875zpb9fh0.fsf@elephly.net>
Ricardo Wurmus <rekado@elephly.net> writes:
> Some of my recent changes must have broken deployment of package
> inputs: […]
The problem appears to have been caused by commit
08ccba0d4848bc4a693e90936201e5dee71b6b19, which introduced containerized
expressions.
The problem is likely with the definition of “package-dirs”:
(with-store store
(run-with-store store
(mapm %store-monad package-file
(process-packages process))))
--
Ricardo
prev parent reply other threads:[~2019-06-12 12:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 12:04 workflow dependencies are not built Ricardo Wurmus
2019-06-12 12:40 ` Ricardo Wurmus [this message]
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://www.guixwl.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874l4v9dt3.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=gwl-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.
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).