unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Vollmert <rob@vllmrt.net>
To: 36562@debbugs.gnu.org
Subject: [bug#36562] downgrading  ghc-ansi-terminal
Date: Tue, 9 Jul 2019 17:51:33 +0200	[thread overview]
Message-ID: <92ADF111-C58E-45B6-B20A-A98EE61838FA@vllmrt.net> (raw)

A patch set to downgrade ghc-ansi-terminal to the stackage LTS
version, to have a consistent package set. This also downgrades
the recently added ghc-validation to version 1 from version 1.1.

The problem with the current situation is that we have some
packages depending on the updated ghc-ansi-terminal 0.9, and
some depending on ghc-ansi-terminal 0.8. By themselves, they
compile, but it’s now impossible to package modules that depend
directly on packages from both sets.

@Jacob: Would ghc-validation version 1 be sufficient for you
purposes?

Cheers
Robert

             reply	other threads:[~2019-07-09 15:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-09 15:51 Robert Vollmert [this message]
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     ` bug#36562: " 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=92ADF111-C58E-45B6-B20A-A98EE61838FA@vllmrt.net \
    --to=rob@vllmrt.net \
    --cc=36562@debbugs.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).