From: filiprojek <filiprojek@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] gnupg: update to 2.4.4
Date: Mon, 29 Jan 2024 16:02:40 +0100 [thread overview]
Message-ID: <20240129150241.03FBD28654@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48419@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 551 bytes --]
There is an updated pull request by filiprojek against master on the void-packages repository
https://github.com/filiprojek/void-packages gnupg
https://github.com/void-linux/void-packages/pull/48419
gnupg: update to 2.4.4
just a version bump
tagging the maintainer @jcgruenhage
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
A patch file from https://github.com/void-linux/void-packages/pull/48419.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-gnupg-48419.patch --]
[-- Type: text/x-diff, Size: 1250 bytes --]
From e1ca9a7f14ec82902fb577a76542c997505bd638 Mon Sep 17 00:00:00 2001
From: Filip Rojek <filip@filiprojek.cz>
Date: Mon, 29 Jan 2024 15:55:23 +0100
Subject: [PATCH] gnupg: update to 2.4.4
---
srcpkgs/gnupg/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/gnupg/template b/srcpkgs/gnupg/template
index d18025c9de2bb..f9f7ddee58860 100644
--- a/srcpkgs/gnupg/template
+++ b/srcpkgs/gnupg/template
@@ -1,8 +1,8 @@
# Template file for 'gnupg'
# minor version updates (2.3-> 2.4) often need a fix in reverse dependencies
pkgname=gnupg
-version=2.4.3
-revision=2
+version=2.4.4
+revision=1
# We're building outside of the source tree, because upstream told us to:
# https://dev.gnupg.org/T6313#166339
build_wrksrc=build
@@ -24,7 +24,7 @@ maintainer="Jan Christian Grünhage <jan.christian@gruenhage.xyz>"
license="GPL-3.0-or-later"
homepage="https://www.gnupg.org/"
distfiles="https://gnupg.org/ftp/gcrypt/gnupg/gnupg-${version}.tar.bz2"
-checksum=a271ae6d732f6f4d80c258ad9ee88dd9c94c8fdc33c3e45328c4d7c126bd219d
+checksum=67ebe016ca90fa7688ce67a387ebd82c6261e95897db7b23df24ff335be85bc6
make_check_pre='env TESTFLAGS="--parallel=${XBPS_MAKEJOBS}"'
build_options="ldap"
build_options_default="ldap"
next prev parent reply other threads:[~2024-01-29 15:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 14:57 [PR PATCH] " filiprojek
2024-01-29 15:02 ` filiprojek [this message]
2024-01-29 17:24 ` jcgruenhage
2024-01-30 11:02 ` filiprojek
2024-02-01 7:29 ` realcharmer
2024-05-02 1:46 ` github-actions
2024-05-16 1:46 ` [PR PATCH] [Closed]: " github-actions
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=20240129150241.03FBD28654@inbox.vuxu.org \
--to=filiprojek@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).