From: "Ludovic Courtès" <ludo@gnu.org>
To: Christopher Baines <mail@cbaines.net>
Cc: help-guix@gnu.org
Subject: Re: Unable to build derivation, even if inputs are available
Date: Fri, 24 Jul 2020 16:32:20 +0200 [thread overview]
Message-ID: <87lfj96l1n.fsf@gnu.org> (raw)
In-Reply-To: <87mu4x7vpg.fsf@cbaines.net> (Christopher Baines's message of "Sat, 20 Jun 2020 13:44:43 +0100")
Hi,
Christopher Baines <mail@cbaines.net> skribis:
> I thought I was beginning to understand derivations, but I've hit a
> problem I can't explain.
>
> I've got a derivation in my local store, and as far as I can work out,
> all the outputs for all the required inputs of this derivation are in
> the store as well.
>
> scheme@(guix-user)> (use-modules (srfi srfi-1) (guix derivations))
> scheme@(guix-user)> (define drv (read-derivation-from-file "/gnu/store/mafs37vw7k65ah071p8f080c9y1y3l7n-bbmap-35.82.drv"))
> scheme@(guix-user)> (define required-outputs (append-map derivation-input-output-paths (derivation-inputs drv)))
> scheme@(guix-user)> (define missing-outputs (remove file-exists? required-outputs))
> scheme@(guix-user)> missing-outputs
> $1 = ()
You should use ‘valid-path?’ instead of ‘file-exists?’: it’s possible
for an item to be present in store while being “invalid”, for instance
because it’s a leftover from a failed build (with ‘-K’).
Ludo’.
prev parent reply other threads:[~2020-07-24 14:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-20 12:44 Unable to build derivation, even if inputs are available Christopher Baines
2020-07-24 14:32 ` Ludovic Courtès [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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lfj96l1n.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=help-guix@gnu.org \
--cc=mail@cbaines.net \
/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).