From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: any nix experts out there?
Date: Fri, 24 Mar 2023 08:42:07 -0700 [thread overview]
Message-ID: <FABB4A81-4BC9-4101-96BA-70538B9645AA@gmail.com> (raw)
I've been enjoying using nix to develop pandoc, but I've hit a snag.
"nix develop" (using flake.nix in the pandoc source directory) now gives me:
trace: WARNING[haskell-flake]: Multiple haskell overlays are applied in arbitrary order.
error: anonymous function at /nix/store/m2pzc238j1y121xy640b7g4vc78v30v9-cabal2nix-pandoc-lua-engine/default.nix:1:1 called without required argument 'hslua-repl'
at /nix/store/p41naxfyrpdamlxdl4iasvkb6l5rlrnb-source/pkgs/development/haskell-modules/make-package-set.nix:97:40:
96| # this wraps the `drv` function to add `scope` and `overrideScope` to the result.
97| drvScope = allArgs: ensureAttrs (drv allArgs) // {
| ^
98| inherit scope;
(use '--show-trace' to show detailed location information)
Does anyone have suggestions about how this can be fixed?
reply other threads:[~2023-03-24 15:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=FABB4A81-4BC9-4101-96BA-70538B9645AA@gmail.com \
--to=fiddlosopher-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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 NNTP newsgroup(s).