all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Léo Le Bouter via Guix-patches via" <guix-patches@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>,
	46643@debbugs.gnu.org, stefan@xsteve.at
Subject: [bug#46643]
Date: Wed, 24 Feb 2021 18:00:18 +0100	[thread overview]
Message-ID: <3f58e4c2479d81ac22aa4e591910240bed8fde21.camel@zaclys.net> (raw)
In-Reply-To: <CAJ3okZ2bLzq+wiqL_sbDFhXr0oxM8bDzozb7Y7mx2RtwGYJqvg@mail.gmail.com>

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

On Wed, 2021-02-24 at 16:40 +0100, zimoun wrote:
> Hi Léo,

Hello! :-)

> If greenclip cannot be built with ghc-protolude@0.2.3, please let the
> "define-public ghc-protolude" at 0.2.3 and instead define
> ghc-protolude-0.3.  As it is done for ghc-atomic-write or
> ghc-generic-random or ghc-prettyprinter or ghc-repline.

I see, pushed 6bea71afac702fcab9fb420daa30aec95652e1a0 to hopefully fix
these concerns. Will keep in mind!

What about ghc-wordexp? Is the version on LTS channel? I couldnt find
much about that online (not very at ease with Stackage).

Thank you!

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-02-24 17:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-19 20:04 [bug#46643] [PATCH 1/3] gnu: ghc-protolude: Update to 0.3.0 Stefan Reichör
2021-02-19 20:04 ` [bug#46645] [PATCH 2/3] gnu: Add ghc-wordexp Stefan Reichör
2021-02-19 20:04 ` [bug#46644] [PATCH 3/3] gnu: Add greenclip Stefan Reichör
2021-02-24 14:27 ` bug#46643: Léo Le Bouter via Guix-patches via
2021-02-24 15:40   ` [bug#46643] zimoun
2021-02-24 17:00     ` Léo Le Bouter via Guix-patches via [this message]
2021-02-24 19:14       ` [bug#46643] Stefan Reichör

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=3f58e4c2479d81ac22aa4e591910240bed8fde21.camel@zaclys.net \
    --to=guix-patches@gnu.org \
    --cc=46643@debbugs.gnu.org \
    --cc=lle-bout@zaclys.net \
    --cc=stefan@xsteve.at \
    --cc=zimon.toutoune@gmail.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.