From: klarasm <klarasm@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] seahorse: allow building with GnuPG-2.4.x
Date: Sat, 04 Feb 2023 01:22:32 +0100 [thread overview]
Message-ID: <20230204002232.vShbk2z87D5aN_Oy_9AR2BSvP2eGR6K938LDQDj6qBE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42055@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 460 bytes --]
There is an updated pull request by klarasm against master on the void-packages repository
https://github.com/klarasm/void-packages seahorse-gpg2.4
https://github.com/void-linux/void-packages/pull/42055
seahorse: allow building with GnuPG-2.4.x
This patch is taken from upstream but is not in any released version yet
- I tested the changes in this PR: see #41948
A patch file from https://github.com/void-linux/void-packages/pull/42055.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-seahorse-gpg2.4-42055.patch --]
[-- Type: text/x-diff, Size: 1451 bytes --]
From 862e2559073f42cafadb6999f0755edffa54c5c5 Mon Sep 17 00:00:00 2001
From: Klara Modin <klarasmodin@gmail.com>
Date: Wed, 1 Feb 2023 16:36:22 +0100
Subject: [PATCH] seahorse: allow building with GnuPG-2.4.x
This patch is taken from upstream but is not in any released version yet
---
.../patches/allow-building-with-gpg-2.4.patch | 25 +++++++++++++++++++
1 file changed, 25 insertions(+)
create mode 100644 srcpkgs/seahorse/patches/allow-building-with-gpg-2.4.patch
diff --git a/srcpkgs/seahorse/patches/allow-building-with-gpg-2.4.patch b/srcpkgs/seahorse/patches/allow-building-with-gpg-2.4.patch
new file mode 100644
index 000000000000..fca2c139b3c6
--- /dev/null
+++ b/srcpkgs/seahorse/patches/allow-building-with-gpg-2.4.patch
@@ -0,0 +1,25 @@
+From 9260c74779be3d7a378db0671af862ffa3573d42 Mon Sep 17 00:00:00 2001
+From: Xi Ruoyao <xry111@xry111.site>
+Date: Wed, 21 Dec 2022 20:58:26 +0800
+Subject: [PATCH] Allow building with GnuPG-2.4.x
+
+---
+ meson.build | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/meson.build b/meson.build
+index e29b5322..23d0b54f 100644
+--- a/meson.build
++++ b/meson.build
+@@ -26,7 +26,7 @@ endif
+ # Dependencies
+ min_glib_version = '2.66'
+ min_gcr_version = '3.38'
+-accepted_gpg_versions = [ '2.2.0', '2.3.0' ]
++accepted_gpg_versions = [ '2.2.0', '2.3.0', '2.4.0' ]
+ gpg_check_version = find_program('build-aux' / 'gpg_check_version.py')
+
+ glib_deps = [
+--
+2.39.1
+
next prev parent reply other threads:[~2023-02-04 0:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 17:15 [PR PATCH] " klarasm
2023-02-03 17:38 ` paper42
2023-02-03 17:56 ` [PR PATCH] [Updated] " klarasm
2023-02-03 17:58 ` klarasm
2023-02-03 23:57 ` [PR REVIEW] " paper42
2023-02-04 0:21 ` klarasm
2023-02-04 0:22 ` klarasm [this message]
2023-02-04 0:23 ` [PR PATCH] [Merged]: " paper42
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=20230204002232.vShbk2z87D5aN_Oy_9AR2BSvP2eGR6K938LDQDj6qBE@z \
--to=klarasm@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).