From: Timothy Sample <samplet@ngyro.com>
To: Jacob MacDonald <jaccarmac@gmail.com>
Cc: 36562-done@debbugs.gnu.org, Robert Vollmert <rob@vllmrt.net>
Subject: bug#36562: downgrading ghc-ansi-terminal
Date: Wed, 07 Aug 2019 23:58:56 -0400 [thread overview]
Message-ID: <87zhkknw8v.fsf@ngyro.com> (raw)
In-Reply-To: <CACy6W0A=na52vDh6eSf-YGrXCmhkKSumgaobLoTN76WZ9T2fVA@mail.gmail.com> (Jacob MacDonald's message of "Wed, 17 Jul 2019 13:09:15 -0500")
Hi,
Jacob MacDonald <jaccarmac@gmail.com> writes:
>> I’ve CC’ed Jacob on this message since they may not be subscribed to the
>> list.
>
> That is indeed the case.
>
>>> @Jacob: Would ghc-validation version 1 be sufficient for you
>>> purposes?
>
> Glancing at the changelog, it should be. If not, I'll use a custom
> package definition. My use-case is low severity anyway.
Okay. Thanks Jacob!
I reordered these a bit so that ansi-terminal and its dependencies get
changed in a single commit. I also split off the removal of the
“Setup.hs” generating phase into its own commit.
They are (finally!) pushed as 1c54c30d9c–91732735f6.
-- Tim
prev parent reply other threads:[~2019-08-08 4:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 15:51 [bug#36562] downgrading ghc-ansi-terminal Robert Vollmert
2019-07-09 15:53 ` [bug#36562] [PATCH 1/6] Revert "gnu: Add ghc-ansi-terminal-0.8." Robert Vollmert
2019-07-09 15:53 ` [bug#36562] [PATCH 2/6] Revert "gnu: ghc-ansi-wl-pprint: Use ghc-ansi-terminal-0.8." Robert Vollmert
2019-07-09 15:53 ` [bug#36562] [PATCH 3/6] gnu: ghc-hedgehog: Use ghc-ansi-terminal Robert Vollmert
2019-07-09 15:53 ` [bug#36562] [PATCH 4/6] Revert "gnu: ghc-ansi-terminal: Update to 0.9.1." Robert Vollmert
2019-07-09 15:53 ` [bug#36562] [PATCH 5/6] gnu: ghc-concurrent-output: Downgrade to 1.10.9 Robert Vollmert
2019-07-09 15:53 ` [bug#36562] [PATCH 6/6] gnu: ghc-validation: Downgrade to 1 Robert Vollmert
2019-07-17 14:37 ` [bug#36562] downgrading ghc-ansi-terminal Timothy Sample
2019-07-17 18:09 ` Jacob MacDonald
2019-08-08 3:58 ` Timothy Sample [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=87zhkknw8v.fsf@ngyro.com \
--to=samplet@ngyro.com \
--cc=36562-done@debbugs.gnu.org \
--cc=jaccarmac@gmail.com \
--cc=rob@vllmrt.net \
/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).