From: Eric Bavier <ericbavier@centurylink.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 37434@debbugs.gnu.org, bavier <bavier@member.fsf.org>
Subject: [bug#37434] [PATCH 1/2] gnu: ghc-megaparsec: Update to 7.0.5.
Date: Mon, 23 Sep 2019 21:59:24 -0400 (EDT) [thread overview]
Message-ID: <1991034139.35893173.1569290364575.JavaMail.zimbra@centurylink.net> (raw)
In-Reply-To: <87muevl8qm.fsf@gnu.org>
Idris 1.3.2 unfortunately needs megaparsec>=7.0.4.
FWIW, idris is our only package that depends on ghc-megaparsec. :) So maybe an upgrade is fine?
I was under the impression that our 'guix refresh' updater was supposed to use the appropriate stackage version? But it seems to be referencing version 14.6.
----- On Sep 23, 2019, at 3:25 AM, Ludovic Courtès ludo@gnu.org wrote:
> Hello!
>
> Timothy Sample <samplet@ngyro.com> skribis:
>
>> Timothy Sample <samplet@ngyro.com> writes:
>>
>>> Stackage LTS 14 targets GHC 8.6, which we are not (yet) using for
>>> Haskell builds. We still use GHC 8.4, so we follow Stackage LTS 12
>>> (<https://www.stackage.org/lts-12>), which lists megaparsec at 1.0.0.
>>
>> That should 6.5.0.
>
> OK, got it—I had “LTS” right but the number wrong, which is
> unfortunate. :-)
>
> Eric, could you adjust accordingly?
>
> Thanks,
> Ludo’.
--
`~Eric
next prev parent reply other threads:[~2019-09-24 2:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 3:37 [bug#37434] [PATCH 1/2] gnu: ghc-megaparsec: Update to 7.0.5 ericbavier
2019-09-17 3:37 ` [bug#37435] [PATCH 2/2] gnu: idris: Update to 1.3.2 ericbavier
2019-09-20 20:32 ` [bug#37434] [PATCH 1/2] gnu: ghc-megaparsec: Update to 7.0.5 Ludovic Courtès
2019-09-20 22:21 ` Timothy Sample
2019-09-20 22:25 ` Timothy Sample
2019-09-23 8:25 ` Ludovic Courtès
2019-09-24 1:59 ` Eric Bavier [this message]
2019-09-24 7:16 ` Ludovic Courtès
2019-09-24 14:06 ` Eric Bavier
2019-09-24 17:08 ` Ludovic Courtès
2019-09-25 2:20 ` bug#37435: " Eric Bavier
2019-09-25 17:49 ` Timothy Sample
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=1991034139.35893173.1569290364575.JavaMail.zimbra@centurylink.net \
--to=ericbavier@centurylink.net \
--cc=37434@debbugs.gnu.org \
--cc=bavier@member.fsf.org \
--cc=ludo@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).