From: ng0 <ng0@we.make.ritual.n0.is>
To: guix-devel@gnu.org
Subject: [PATCH 5/6] gnu: gnupg: Update to 2.1.14.
Date: Sun, 17 Jul 2016 23:20:57 +0000 [thread overview]
Message-ID: <87eg6r97hi.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: ng0@we.make.ritual.n0.is's message of "Sun\, 17 Jul 2016 22\:56\:38 +0000"
2.1.14 introduced tests in gpgscm.
This package relies on gpgscm package for now.
From 22d466e34e653eda765fe424043200d9ced54cd6 Mon Sep 17 00:00:00 2001
From: ng0 <ng0@we.make.ritual.n0.is>
Date: Sun, 17 Jul 2016 22:28:55 +0000
Subject: [PATCH 5/6] gnu: gnupg: Update to 2.1.14.
* gnu/packages/gnupg.scm (gnupg): Update to 2.1.14.
---
gnu/packages/gnupg.scm | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/gnu/packages/gnupg.scm b/gnu/packages/gnupg.scm
index 84bf19c..9102d7b 100644
--- a/gnu/packages/gnupg.scm
+++ b/gnu/packages/gnupg.scm
@@ -315,17 +315,18 @@ libskba (working with X.509 certificates and CMS data).")
(define-public gnupg
(package
(name "gnupg")
- (version "2.1.13")
+ (version "2.1.14")
(source (origin
(method url-fetch)
(uri (string-append "mirror://gnupg/gnupg/gnupg-" version
".tar.bz2"))
(sha256
(base32
- "0xcn46vcb5x5qx0bc803vpzhzhnn6wfhp7x71w9n1ahx4ak877ag"))))
+ "0hmsiscpdpdqd8kcjpzkz2gzcc3cnrvswk9p1jzi4sivd7lxwl4l"))))
(build-system gnu-build-system)
(native-inputs
- `(("pkg-config" ,pkg-config)))
+ `(("pkg-config" ,pkg-config)
+ ("gpgscm" ,gpgscm)))
(inputs
`(("adns" ,adns)
("bzip2" ,bzip2)
--
2.9.1
--
♥Ⓐ ng0
For non-prism friendly talk find me on http://www.psyced.org
SecuShare – http://secushare.org
next reply other threads:[~2016-07-17 23:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-17 23:20 ng0 [this message]
2016-07-17 23:31 ` [PATCH 5/6] gnu: gnupg: Update to 2.1.14 ng0
2016-07-29 8:32 ` ng0
2016-08-02 20:23 ` 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=87eg6r97hi.fsf@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).