From: motorto <motorto@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] seahorse-nautilus-fix-building.patch
Date: Sat, 13 Aug 2022 14:15:44 +0200 [thread overview]
Message-ID: <20220813121544.5Ckhut5MRzf2fjR76VvJ-8d8Y8ctKlTFfWfGTGu5PmI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38650@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 579 bytes --]
There is an updated pull request by motorto against master on the void-packages repository
https://github.com/motorto/void-packages seahorse-nautilus
https://github.com/void-linux/void-packages/pull/38650
seahorse-nautilus-fix-building.patch
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: NO
#### 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/38650.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-seahorse-nautilus-38650.patch --]
[-- Type: text/x-diff, Size: 919 bytes --]
From a3be3c1bc1c3e61bc3b1e11ec3154fcc44c94fd5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Andr=C3=A9=20Cerqueira?= <acerqueira021@gmail.com>
Date: Sat, 13 Aug 2022 13:13:05 +0100
Subject: [PATCH] seahorse-nautilus: fix-building.patch
---
srcpkgs/seahorse-nautilus/patches/new-gnupg.patch | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/srcpkgs/seahorse-nautilus/patches/new-gnupg.patch b/srcpkgs/seahorse-nautilus/patches/new-gnupg.patch
index 7cdbdbf84d1f..01d944a3cac9 100644
--- a/srcpkgs/seahorse-nautilus/patches/new-gnupg.patch
+++ b/srcpkgs/seahorse-nautilus/patches/new-gnupg.patch
@@ -7,7 +7,7 @@ Index: seahorse-nautilus-3.10.1/configure.ac
if test "$DO_CHECK" = "yes"; then
- accepted_versions="1.2 1.4 2.0"
-+ accepted_versions="1.2 1.4 2.0 2.1 2.2"
++ accepted_versions="1.2 1.4 2.0 2.1 2.2 2.3"
AC_PATH_PROGS(GNUPG, [gpg gpg2], no)
ok="no"
if test "$GNUPG" != "no"; then
next prev parent reply other threads:[~2022-08-13 12:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-13 12:15 [PR PATCH] seahorse-nautilus-fix-building.patch motorto
2022-08-13 12:15 ` motorto [this message]
2022-08-13 13:52 ` seahorse-nautilus-fix-building.patch paper42
2022-08-13 14:26 ` [PR PATCH] [Updated] seahorse-nautilus-fix-building.patch motorto
2022-08-13 15:06 ` [PR PATCH] [Merged]: seahorse-nautilus: fix build with gnupg 2.3 sgn
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=20220813121544.5Ckhut5MRzf2fjR76VvJ-8d8Y8ctKlTFfWfGTGu5PmI@z \
--to=motorto@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).