From: Ricardo Wurmus <rekado@elephly.net>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: 08/10: gnu: r-snpstats: Move to (gnu packages bioconductor).
Date: Tue, 29 Dec 2020 20:04:41 +0100 [thread overview]
Message-ID: <87a6twl9h2.fsf@elephly.net> (raw)
In-Reply-To: <87lfdg4h5i.fsf@gnu.org>
Mathieu Othacehe <othacehe@gnu.org> writes:
> Hello,
>
> This commit caused the following evaluation issue:
>
> --8<---------------cut here---------------start------------->8---
> Generating package cache for '/gnu/store/dylz1h2sxgaqd6jhzq01b6y26797zjm5-profile'...
> (exception unbound-variable (value #f) (value "Unbound variable: ~S") (value (r-snpstats)) (value #f))
> builder for `/gnu/store/g546w6qi19001rcx7si7imrb1z7yzf3g-guix-package-cache.drv' failed to produce output path `/gnu/store/sjy574qw76kdrria4grhx16xqqs9w78z-guix-package-cache'
> @ build-failed /gnu/store/g546w6qi19001rcx7si7imrb1z7yzf3g-guix-package-cache.drv - 1 builder for `/gnu/store/g546w6qi19001rcx7si7imrb1z7yzf3g-guix-package-cache.drv' failed to produce output path `/gnu/store/sjy574qw76kdrria4grhx16xqqs9w78z-guix-
> --8<---------------cut here---------------end--------------->8---
>
> I fixed it with 0c8bb20b7cbd39537999fce29979a6acaf64e601, which is maybe
> not the better solution.
Oh, that’s unfortunate. I’m sorry for the breakage. I did run “make”
to build the changed modules, so I’m surprised I didn’t see an “Unbound
variable” error then.
I’ll move that package from cran.scm to bioconductor.scm as we did in
similar cases.
--
Ricardo
next prev parent reply other threads:[~2020-12-29 19:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201229164122.31455.12991@vcs0.savannah.gnu.org>
[not found] ` <20201229164128.39AAE21074@vcs0.savannah.gnu.org>
2020-12-29 18:10 ` 08/10: gnu: r-snpstats: Move to (gnu packages bioconductor) Mathieu Othacehe
2020-12-29 19:04 ` Ricardo Wurmus [this message]
2020-12-30 9:10 ` zimoun
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=87a6twl9h2.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=othacehe@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).