From: 4ricci <4ricci@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] gnupg2: update to 2.2.26
Date: Tue, 22 Dec 2020 15:09:19 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27350@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 313 bytes --]
There is a new pull request by 4ricci against master on the void-packages repository
https://github.com/4ricci/void-packages gnupg2-2.2.26
https://github.com/void-linux/void-packages/pull/27350
gnupg2: update to 2.2.26
A patch file from https://github.com/void-linux/void-packages/pull/27350.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-gnupg2-2.2.26-27350.patch --]
[-- Type: text/x-diff, Size: 1004 bytes --]
From bbfcfd6ece2617f979dff72e52e43b2da471c577 Mon Sep 17 00:00:00 2001
From: Roberto Ricci <ricci@disroot.org>
Date: Tue, 22 Dec 2020 15:07:35 +0100
Subject: [PATCH] gnupg2: update to 2.2.26
---
srcpkgs/gnupg2/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/gnupg2/template b/srcpkgs/gnupg2/template
index 55831aafbbb..fe98ce4c7cd 100644
--- a/srcpkgs/gnupg2/template
+++ b/srcpkgs/gnupg2/template
@@ -1,6 +1,6 @@
# Template file for 'gnupg2'
pkgname=gnupg2
-version=2.2.25
+version=2.2.26
revision=1
wrksrc="gnupg-${version}"
build_style=gnu-configure
@@ -17,7 +17,7 @@ maintainer="Orphaned <orphan@voidlinux.org>"
license="GPL-3.0-or-later"
homepage="https://www.gnupg.org/"
distfiles="https://gnupg.org/ftp/gcrypt/gnupg/gnupg-${version}.tar.bz2"
-checksum=c55307b247af4b6f44d2916a25ffd1fb64ce2e509c3c3d028dbe7fbf309dc30a
+checksum=517569e6c9fad22175df16be5900f94c991c41e53612db63c14493e814cfff6d
build_options="ldap"
build_options_default="ldap"
next reply other threads:[~2020-12-22 14:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 14:09 4ricci [this message]
2020-12-22 20:47 ` [PR PATCH] [Closed]: " ahesford
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27350@inbox.vuxu.org \
--to=4ricci@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).