unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Léo Le Bouter via Guix-patches via" <guix-patches@gnu.org>
To: 46643-done@debbugs.gnu.org
Subject: bug#46643:
Date: Wed, 24 Feb 2021 15:27:43 +0100	[thread overview]
Message-ID: <1fb2ba44f701f4bf10876deb73a3d45cb4b53e9b.camel@zaclys.net> (raw)
In-Reply-To: <20210219200427.105200-1-stefan@xsteve.at>

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

Pushed all patches in a1386815503036773a1092554f36d45dd9361efe.

It seems the licenses for ghc-wordexp and greenclip is BSD-3-Clause
from <https://hackage.haskell.org/package/wordexp> and <
https://hackage.haskell.org/package/greenclip>.

Also, your upgrade of ghc-protolude broke the purescript build which
depends on ghc-protolude<0.2.4 so I created a secondary ghc-protolude-
0.2 package that purescript now depends on.

Think about running "$ guix refresh -l <package>" if you modify any
package to check for all its dependents and then try to build all the
dependents see if they don't break and if they do break please fix
them. That's what I did here.

I also fixed lint errors on ghc-wordexp. Think about running "$ guix
lint <package>" on any package you are adding or altering before
submitting.

Thank you!

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

  parent reply	other threads:[~2021-02-24 14:28 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 ` Léo Le Bouter via Guix-patches via [this message]
2021-02-24 15:40   ` [bug#46643] zimoun
2021-02-24 17:00     ` [bug#46643] Léo Le Bouter via Guix-patches via
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

  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=1fb2ba44f701f4bf10876deb73a3d45cb4b53e9b.camel@zaclys.net \
    --to=guix-patches@gnu.org \
    --cc=46643-done@debbugs.gnu.org \
    --cc=lle-bout@zaclys.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).