From: Guillaume Le Vaillant <glv@posteo.net>
To: 39477-done@debbugs.gnu.org
Subject: bug#39477: sbcl-serapeum yields sbcl loading error in guix environment container
Date: Fri, 07 Feb 2020 12:23:41 +0100 [thread overview]
Message-ID: <87lfpe4p4y.fsf@yamatai> (raw)
In-Reply-To: <CALNvAbdA+AHTQYc=S7K7124dH042hCbAM7GzQ=B2gDrZinza_Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]
Martin Flack <martin.flack@gmail.com> skribis:
> Hello,
>
> This command:
>
> guix environment --container --no-cwd --ad-hoc sbcl sbcl-serapeum -- \
> sbcl --eval '(require :asdf)' --eval '(require :serapeum)' --quit
>
> ...yields an error from SBCL:
>
> ...
> ASDF could not load serapeum because
> Component "fare-quasiquote-extras" not found, required by
> #<PREBUILT-SYSTEM "serapeum">.
>
> debugger invoked on a ASDF/FIND-COMPONENT:MISSING-DEPENDENCY in thread
> #<THREAD "main thread" RUNNING {10005684C3}>:
> Component "fare-quasiquote-extras" not found, required by
> #<PREBUILT-SYSTEM "serapeum">
> ...
>
> The same command works with other substantial packages if you replace (both
> mentions of) serapeum with dramka or cl-async for example. Maybe there is a
> dependency issue with either serapeum or the fare utils? How might this be
> fixed?
>
> guix --version
>
> guix (GNU Guix) 9d0dfd9a9a7c43363a4e140c20d49f119fe6f2e3
>
> Thanks!
Hi,
There was indeed an issue with the fare-quasiquote-extras input of the
serapeum package. I pushed a fix as
8137983adfe3c3f61e583aae140a62046e859435.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2020-02-07 11:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 1:18 bug#39477: sbcl-serapeum yields sbcl loading error in guix environment container Martin Flack
2020-02-07 11:23 ` Guillaume Le Vaillant [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=87lfpe4p4y.fsf@yamatai \
--to=glv@posteo.net \
--cc=39477-done@debbugs.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).