From: clyhtsuriva <clyhtsuriva@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] gnupg: update to 2.2.33
Date: Mon, 03 Jan 2022 10:49:45 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34830@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1181 bytes --]
There is a new pull request by clyhtsuriva against master on the void-packages repository
https://github.com/clyhtsuriva/void-packages gnupg-update
https://github.com/void-linux/void-packages/pull/34830
gnupg: update to 2.2.33
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration)
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
#### Note
New LTS release : https://lists.gnupg.org/pipermail/gnupg-announce/2021q4/000467.html
A patch file from https://github.com/void-linux/void-packages/pull/34830.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-gnupg-update-34830.patch --]
[-- Type: text/x-diff, Size: 1007 bytes --]
From 6186daab9d6d7a9c14d1b67f4c5659321ba4ea05 Mon Sep 17 00:00:00 2001
From: clyhtsuriva <aimeric@adjutor.xyz>
Date: Mon, 3 Jan 2022 10:47:37 +0100
Subject: [PATCH] gnupg: update to 2.2.33
---
srcpkgs/gnupg/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/gnupg/template b/srcpkgs/gnupg/template
index 9f1bb8a27bb0..9c77969b5ec9 100644
--- a/srcpkgs/gnupg/template
+++ b/srcpkgs/gnupg/template
@@ -1,6 +1,6 @@
# Template file for 'gnupg'
pkgname=gnupg
-version=2.2.32
+version=2.2.33
revision=1
build_style=gnu-configure
configure_args="$(vopt_enable ldap)
@@ -18,7 +18,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=b2571b35f82c63e7d278aa6a1add0d73453dc14d3f0854be490c844fca7e0614
+checksum=8688836e8c043d70410bb64d72de6ae15176e09ecede8d24528b4380c000e4e3
build_options="ldap"
build_options_default="ldap"
next reply other threads:[~2022-01-03 9:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 9:49 clyhtsuriva [this message]
2022-02-09 13:22 ` tibequadorian
2022-02-09 14:05 ` [PR PATCH] [Updated] " clyhtsuriva
2022-02-09 14:06 ` clyhtsuriva
2022-02-09 14:13 ` [PR PATCH] [Updated] " clyhtsuriva
2022-02-11 22:15 ` [PR PATCH] [Merged]: gnupg: update to 2.2.34 leahneukirchen
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-34830@inbox.vuxu.org \
--to=clyhtsuriva@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).