all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: brown121407@posteo.ro, 40042@debbugs.gnu.org
Cc: Alexandru-Sergiu Marton <brown121407@member.fsf.org>,
	Timothy Sample <samplet@ngyro.com>,
	Leo Famulari <leo@famulari.name>
Subject: [bug#40042] [PATCH] gnu: ghc-extra: Update to 1.7.1.
Date: Fri, 20 Mar 2020 19:49:50 +0100	[thread overview]
Message-ID: <87pnd67tf5.fsf@devup.no> (raw)
In-Reply-To: <20200312152016.3910-1-brown121407@posteo.ro>

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

brown121407@posteo.ro writes:

> From: Alexandru-Sergiu Marton <brown121407@member.fsf.org>
>
> * gnu/packages/haskell-xyz.scm (ghc-extra): Update to 1.7.1.

Note that we follow the Stackage LTS releases to ensure the various
Haskell packages work nicely together.  The latest Stackage release of
Extra is 1.6.21, as reported by 'guix refresh':

$ ./pre-inst-env guix refresh ghc-extra
following redirection to `https://www.stackage.org/lts'...
following redirection to `https://www.stackage.org/lts-15.4'...
gnu/packages/haskell-xyz.scm:3777:13: warning: 1.7.1 is greater than the latest known version of ghc-extra (1.6.21)

So I wonder if we should downgrade this package to avoid compatibility
problems.  Thoughts?

By the way, if you use './pre-inst-env guix refresh -u PACKAGE-NAME' to
update packages, it will choose the correct version for you.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2020-03-20 18:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-12 15:20 [bug#40042] [PATCH] gnu: ghc-extra: Update to 1.7.1 brown121407
2020-03-20 18:49 ` Marius Bakke [this message]
2020-03-20 19:11   ` Alexandru-Sergiu Marton
2020-03-20 19:15     ` Marius Bakke

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=87pnd67tf5.fsf@devup.no \
    --to=mbakke@fastmail.com \
    --cc=40042@debbugs.gnu.org \
    --cc=brown121407@member.fsf.org \
    --cc=brown121407@posteo.ro \
    --cc=leo@famulari.name \
    --cc=samplet@ngyro.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.