From: "Axel Kielhorn (Pandoc)" <Pandoc-Mm1VAy9jqyoZTkkHcba27w@public.gmane.org>
To: Pandoc discuss discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Text.Pandoc.Citeproc.Data Build error on MacOS 11
Date: Sun, 27 Mar 2022 11:01:22 +0200 [thread overview]
Message-ID: <E4AB7E0F-CB4C-489B-B8B8-3FD889B007CE@axelkielhorn.de> (raw)
In-Reply-To: <m2tubkcucx.fsf-jF64zX8BO0+FqBokazbCQ6OPv3vYUT2dxr7GGTnW70NeoWH0uzbU5w@public.gmane.org>
Hello John,
> Am 26.03.2022 um 21:49 schrieb John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>:
>
>
> I've had this sort of issue with stack before. It seems to happen
> when we switch to using a github dependency in stack.yaml.
> (Are you compiling the dev version?)
Yes, git version downloaded yesterday.
> There's probably a better solution, but the only one that has
> worked for me is deleting the global user stack directory
> entirely.
I deleted „everything“ and now it builds fine.
> Actually, I've switched to developing in cabal just because of
> this issue!
I moved to stack because cabal didn’t handle dependencies well when skipping too many pandoc versions.
Thanks for the quick rely.
Axel
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/E4AB7E0F-CB4C-489B-B8B8-3FD889B007CE%40axelkielhorn.de.
prev parent reply other threads:[~2022-03-27 9:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-26 7:42 Axel Kielhorn (Pandoc)
[not found] ` <AD120412-17EB-4F4C-AA09-CB76632B1296-Mm1VAy9jqyoZTkkHcba27w@public.gmane.org>
2022-03-26 20:49 ` John MacFarlane
[not found] ` <m2tubkcucx.fsf-jF64zX8BO0+FqBokazbCQ6OPv3vYUT2dxr7GGTnW70NeoWH0uzbU5w@public.gmane.org>
2022-03-27 9:01 ` Axel Kielhorn (Pandoc) [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E4AB7E0F-CB4C-489B-B8B8-3FD889B007CE@axelkielhorn.de \
--to=pandoc-mm1vay9jqyoztkkhcba27w@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).