From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: typeclass branch merged into master
Date: Sat, 4 Feb 2017 10:33:51 +0100 [thread overview]
Message-ID: <20170204093350.GG89252@Johns-MBP.home> (raw)
In-Reply-To: <a919f816-0b41-4b0a-8b55-1e095ee5b495-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
You need to update submodules
git submodule update
I'm not sure about the other error; I'd do a cabal clean
before trying again.
+++ Bruce D'Arcus [Feb 03 17 07:05 ]:
> FYI, I just tried to build off master, and got this error.
> pandoc-2.0: copy/register
> data/templates/default.html4: copyFile: does not exist (No such file or
> directory)
> 'cabal copy' failed. Error message:
> -- While building package pandoc-2.0 using:
>
> /home/bruce/Code/thirdparty/pandoc/.stack-work/dist/x86_64-linux/Cabal-
> 1.24.0.0/setup/setup
> --builddir=.stack-work/dist/x86_64-linux/Cabal-1.24.0.0 copy
> Process exited with code: ExitFailure 1
> Possible causes of this issue:
> * No module named "Main". The 'main-is' source file should usually have
> a header indicating that it's a 'Main' module.
> * The Setup.hs file is changing the installation target dir.
> On Sunday, January 29, 2017 at 4:19:01 PM UTC-5, John MacFarlane wrote:
>
> With the release of 1.19.2, I'm planning for
> the next release to be 2.0. So I've rather
> optimistically merged the 'typeclass' branch
> into master and removed the old 'typeclass'
> branch.
> This should simplify progress towards 2.0.
>
> --
> 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 [1]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To post to this group, send email to
> [2]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit
> [3]https://groups.google.com/d/msgid/pandoc-discuss/a919f816-0b41-4b0a-
> 8b55-1e095ee5b495%40googlegroups.com.
> For more options, visit [4]https://groups.google.com/d/optout.
>
>References
>
> 1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 2. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 3. https://groups.google.com/d/msgid/pandoc-discuss/a919f816-0b41-4b0a-8b55-1e095ee5b495-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
> 4. https://groups.google.com/d/optout
prev parent reply other threads:[~2017-02-04 9:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-29 21:18 John MacFarlane
[not found] ` <20170129211843.GA76027-l/d5Ua9yGnxXsXJlQylH7w@public.gmane.org>
2017-02-01 11:15 ` BP Jonsson
[not found] ` <CAFC_yuSQ+8bySqJ8HxRAQWxnNo=9nzoo7qYUKEiE5AVYSy3CKw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-02-01 13:25 ` John MacFarlane
2017-02-03 15:05 ` Bruce D'Arcus
[not found] ` <a919f816-0b41-4b0a-8b55-1e095ee5b495-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-02-04 9:33 ` John MacFarlane [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=20170204093350.GG89252@Johns-MBP.home \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@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).