unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Troy Sankey <sankeytms@gmail.com>
To: Federico Beffa <beffa@ieee.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: updating many haskell packages
Date: Wed, 15 Feb 2017 14:07:45 -0500	[thread overview]
Message-ID: <148718566589.32672.16026626114827562716@what> (raw)
In-Reply-To: <CAKrPhPPh7Y7VHpAq-Lxfrq3zQcFGEYyYY05BpFQk8q2yJjwdPA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 778 bytes --]

Quoting Federico Beffa (2017-02-06 03:13:16)
> On Mon, Feb 6, 2017 at 9:03 AM, Federico Beffa <beffa@ieee.org> wrote:
> 
> > (ii) The latest LTS still uses GHC 8.0.1.  I'm not sure if this is
> > because of some real problem (GHC 8.0.2 introduces some
> > incompatibilities) or if it is because changing things takes time.
> 
> Looks like LTS8 is on its way http://lwm.github.io/stackage-8.0.2/

Stackage LTS 8.0 has been released:

https://www.stackage.org/lts-8.0

In the coming days, I'll work to make all our current haskell packages
(and my additions) converge to LTS 8.0.  I may backport the stackage
importer [0] if I need to, but I don't expect that it will be required.

Troy

[0] https://lists.gnu.org/archive/html/guix-devel/2017-02/msg00270.html

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEE0zLJ6STd4Cp+CgbIgs677ofYV8IFAlikpvMACgkQgs677ofY
V8Ih8Q//cCMOccTqnA6cPp6H2B8XKXdx/WzJjcSZWiS3gflrOYrfiMZ65mA4TV0l
nApJXulRtSt3ZdNQVMM2PaQz4RAU8F41T/26rM/fQK55HQmj0a30IVgWlGu+Oi2c
5qoBS27lZ9Hr0SDUsAQTQ1Ljitrr9gRq9NhGz03dgd7myb9czGMMCIkjm/FVQlVA
7XrRO9HMOFb/lVP2RaOadRobXO+92z7+F3H35viceRxs8Oc6QBjNWuMDfnkEXLEX
2px6h0WpMLWl1aZY/pXwYrDpjU8H1nhu+yCf7AkoH7582wfH9X/7vjA7R3Bpe3L7
1KNhO8/RL6SFi73OaUTphwtjK9a/uq6tPCfJh0MXWJhAxg9PoFCAc0lGt3aB6NhL
4VeZQs+hEGUPLjEPG5VhjhCvWRHx4QdLGJcl3ORJFI/FNVeLmg9kyXWSPE6ahOwI
tNABSAG6a1mxMt/uuya+PMxfZgZk7cQ3fh5LWjNie4y7nk9cO6zVR20/xnSzAvQF
2jQDFAjRqmXDgD8vE/eMrTd7v6oZ+sNmCmlUWlU49CZRllDGi3tyPrXFIaFu6eGM
e3sYBcKY3aMfZLMgHOYNNNbcyMGLKqPxnD1uhzCJbUMm0wLfRmD0x7WIRznOY2I/
YHZ5ppkCJBnzESfkONkj9qF2/0ONhizAQHE5zYJ7PYvIx+9bUi8=
=Q4JR
-----END PGP SIGNATURE-----

  reply	other threads:[~2017-02-15 19:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-06  8:03 updating many haskell packages Federico Beffa
2017-02-06  8:13 ` Federico Beffa
2017-02-15 19:07   ` Troy Sankey [this message]
2017-02-17 16:43     ` Ricardo Wurmus
2017-02-06 15:23 ` Troy Sankey
2017-02-06 20:34   ` Federico Beffa
2017-02-06 21:00     ` Troy Sankey
2017-02-15 19:31       ` Troy Sankey
2017-02-17  8:00         ` Federico Beffa
2017-02-17 17:47           ` Troy Sankey
2017-02-18  9:43             ` Federico Beffa
2017-02-18 17:40               ` Troy Sankey
2017-02-18 20:23                 ` Federico Beffa
2017-02-19 19:21                 ` Troy Sankey
  -- strict thread matches above, loose matches on Subject: below --
2017-02-06  5:23 Troy Sankey
2017-02-06 15:47 ` Leo Famulari

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=148718566589.32672.16026626114827562716@what \
    --to=sankeytms@gmail.com \
    --cc=beffa@ieee.org \
    --cc=guix-devel@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).