From: ng0 <ng0@we.make.ritual.n0.is>
To: guix-devel@gnu.org
Subject: [PATCH 03/29] gnu: ghc-cryptonite: Update to 0.19.
Date: Sat, 3 Sep 2016 12:46:02 +0000 [thread overview]
Message-ID: <20160903124628.14100-3-ng0@we.make.ritual.n0.is> (raw)
In-Reply-To: <20160903124628.14100-1-ng0@we.make.ritual.n0.is>
* gnu/packages/haskell.scm (ghc-cryptonite): Update to 0.19.
---
gnu/packages/haskell.scm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gnu/packages/haskell.scm b/gnu/packages/haskell.scm
index 3934c17..6fda9d8 100644
--- a/gnu/packages/haskell.scm
+++ b/gnu/packages/haskell.scm
@@ -5979,7 +5979,7 @@ tasty.")
(define-public ghc-cryptonite
(package
(name "ghc-cryptonite")
- (version "0.9")
+ (version "0.19")
(source (origin
(method url-fetch)
(uri (string-append "https://hackage.haskell.org/package/"
@@ -5987,7 +5987,7 @@ tasty.")
version ".tar.gz"))
(sha256
(base32
- "1h22x22lq2m8h456v5j50xm0l25bcm3h1pchsk83br909hjxql4z"))))
+ "1rw5k34vpn4134yrzdhf0rsshsrkixfbv9ap18di2n00z2cw1shw"))))
(build-system haskell-build-system)
(propagated-inputs
`(("ghc-memory" ,ghc-memory)
--
2.9.3
next prev parent reply other threads:[~2016-09-03 12:46 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-03 12:46 [PATCH 01/29] gnu: Add ghc-base16-bytestring ng0
2016-09-03 12:46 ` [PATCH 02/29] gnu: Add ghc-binary ng0
2016-09-03 12:46 ` ng0 [this message]
2016-09-03 12:46 ` [PATCH 04/29] gnu: Add ghc-cryptohash ng0
2016-09-03 12:46 ` [PATCH 05/29] gnu: Add ghc-data-ordlist ng0
2016-09-03 12:46 ` [PATCH 06/29] gnu: Add ghc-terminfo ng0
2016-09-03 12:46 ` [PATCH 07/29] gnu: Add ghc-haskeline ng0
2016-09-03 12:46 ` [PATCH 08/29] gnu: Add ghc-regex-applicative ng0
2016-09-03 12:46 ` [PATCH 09/29] gnu: Add ghc-regex-tdfa ng0
2016-09-03 12:46 ` [PATCH 10/29] gnu: Add ghc-regex-compat-tdfa ng0
2016-09-03 12:46 ` [PATCH 11/29] gnu: Add ghc-tasty-th ng0
2016-09-03 12:46 ` [PATCH 12/29] gnu: Add ghc-sandi ng0
2016-09-03 12:46 ` [PATCH 13/29] gnu: Add ghc-bytestring-handle ng0
2016-09-03 12:46 ` [PATCH 14/29] gnu: Add ghc-tar ng0
2016-09-03 12:46 ` [PATCH 15/29] gnu: Add ghc-transformers ng0
2016-09-03 12:46 ` [PATCH 16/29] gnu: Add ghc-findbin ng0
2016-09-03 12:46 ` [PATCH 17/29] gnu: Add ghc-patience ng0
2016-09-03 12:46 ` [PATCH 18/29] gnu: Add ghc-monads-tf ng0
2016-09-03 12:46 ` [PATCH 19/29] gnu: Add ghc-bytestring ng0
2016-09-03 12:46 ` [PATCH 20/29] gnu: Add ghc-colour ng0
2016-09-03 12:46 ` [PATCH 21/29] gnu: Add ghc-directory ng0
2016-09-03 12:46 ` [PATCH 22/29] gnu: Add ghc-process ng0
2016-09-03 12:46 ` [PATCH 23/29] gnu: Add ghc-wl-pprint-text ng0
2016-09-03 12:46 ` [PATCH 24/29] gnu: ghc-fgl: Update to 5.5.3.0 ng0
2016-09-03 12:46 ` [PATCH 25/29] gnu: Add ghc-fgl-arbitrary ng0
2016-09-03 12:46 ` [PATCH 26/29] gnu: Add ghc-graphviz ng0
2016-09-03 12:46 ` [PATCH 27/29] gnu: Add ghc-array ng0
2016-09-03 12:46 ` [PATCH 28/29] gnu: Add ghc-findbin ng0
2016-09-03 12:46 ` [PATCH 29/29] gnu: Add darcs ng0
2016-09-03 12:52 ` ng0
2016-09-03 13:51 ` Peter Mikkelsen
2016-09-03 16:32 ` ng0
2016-09-04 13:17 ` ng0
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=20160903124628.14100-3-ng0@we.make.ritual.n0.is \
--to=ng0@we.make.ritual.n0.is \
--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).