gnupg update to 2.4.7 causing guix build -K seahorse to fail

  • Open
  • quality assurance status badge
Details
2 participants
  • Leo Famulari
  • Rostislav Svoboda
Owner
unassigned
Submitted by
Rostislav Svoboda
Severity
normal
R
R
Rostislav Svoboda wrote 26 hours ago
CAEtmmexTqemoQDdjO4MA7f7=tJpDb0NjMTMq69U22fFmuhRNtQ@mail.gmail.com
Hello,

I believe the commit:
64d95c78e3 2024-12-29 gnu: gnupg: Update to 2.4.7.
causes guix build --keep-failed seahorse to fail. The build log shows:

../seahorse-43.0/meson.build:52:22: ERROR: Command
`/tmp/guix-build-seahorse-43.0.drv-0/seahorse-43.0/build-aux/gpg_check_version.py
/gnu/store/bsp4vbhqpzajsdmg2k21l1lalainqasd-gnupg-2.4.7/bin/gpg 2.2.0
2.3.0` failed with status 1.

When rerun on my system, I get:
/tmp/guix-build-seahorse-43.0.drv-0/seahorse-43.0/build-aux/gpg_check_version.py
/gnu/store/bsp4vbhqpzajsdmg2k21l1lalainqasd-gnupg-2.4.7/bin/gpg 2.2.0
2.3.0
2.4.7

From casually looking at gpg_check_version.py, it appears to check
whether the available GPG version is between 2.2.0 and 2.3.0, so 2.4.7
fails that check.

Cheers
Bost
L
L
Leo Famulari wrote 23 hours ago
(name . Rostislav Svoboda)(address . rostislav.svoboda@gmail.com)
Z4bM0d6coZO4-C2S@jasmine.lan
On Tue, Jan 14, 2025 at 05:52:46PM +0100, Rostislav Svoboda wrote:
Toggle quote (4 lines)
> I believe the commit:
> 64d95c78e3 2024-12-29 gnu: gnupg: Update to 2.4.7.
> causes guix build --keep-failed seahorse to fail. The build log shows:

Thanks for the report!

Toggle quote (4 lines)
> From casually looking at gpg_check_version.py, it appears to check
> whether the available GPG version is between 2.2.0 and 2.3.0, so 2.4.7
> fails that check.

I cloned the seahorse Git repository:


Then, I grepped for the string "2.3.0". The only match is in
'meson.build'.

Guix includes seahorse version 43.0. I checked the Git log of
Seahorse's 'meson.build' since version 43.0, and found this interesting
commit:

------
$ git log 43.0..HEAD meson.build
[...]
commit 9260c74779be3d7a378db0671af862ffa3573d42
Author: Xi Ruoyao <xry111@xry111.site>
Date: Wed Dec 21 20:58:26 2022 +0800

Allow building with GnuPG-2.4.x
------

This commit is included in Seahorse 47.0 and later versions. Hopefully
that helps!
R
R
Rostislav Svoboda wrote 18 hours ago
(name . Leo Famulari)(address . leo@famulari.name)
CAEtmmeyW1_QTznGUX8_qcfbuQbD-2mpFCuRSHJj0nR0odDvwKQ@mail.gmail.com
Toggle quote (3 lines)
> This commit is included in Seahorse 47.0 and later versions. Hopefully
> that helps!

Thanks Leo. In theory, the fix should be straightforward (see
attachment). However, we need to be careful:

$ guix search ^seahorse\$ | grep synopsis
synopsis: Manage encryption keys and passwords in the GNOME keyring

Cheers,
Bost
From 08e0448224bb2db53facaa58b4cac14c055655ab Mon Sep 17 00:00:00 2001
Message-ID: <08e0448224bb2db53facaa58b4cac14c055655ab.1736902490.git.Rostislav.Svoboda@gmail.com>
From: Rostislav Svoboda <Rostislav.Svoboda@gmail.com>
Date: Wed, 15 Jan 2025 01:50:36 +0100
Subject: [PATCH] gnu: seahorse: Update to 47.0.1.


* gnu/packages/gnome.scm (seahorse): Update to 47.0.1.

Change-Id: I30095f0e3b67d0dfcc263e72bc48f4cd9a1ec7e8
---
gnu/packages/gnome.scm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

Toggle diff (26 lines)
diff --git a/gnu/packages/gnome.scm b/gnu/packages/gnome.scm
index 30038379f5..f24a6b2aa8 100644
--- a/gnu/packages/gnome.scm
+++ b/gnu/packages/gnome.scm
@@ -4500,7 +4500,7 @@ (define-public drawing
(define-public seahorse
(package
(name "seahorse")
- (version "43.0")
+ (version "47.0.1")
(source
(origin
(method url-fetch)
@@ -4508,7 +4508,7 @@ (define-public seahorse
(version-major version) "/" name "-"
version ".tar.xz"))
(sha256
- (base32 "0bc3xbjzwa4245m6nqzl3v6hzp9hyfbf50iwgwi5hdjglzxin7av"))))
+ (base32 "1k6avgd58v853nchp226qc3fgz0pwxnf7744hyvynzqzlvj1f6cw"))))
(build-system meson-build-system)
(arguments
'(#:glib-or-gtk? #t

base-commit: 7ba52cb34be061d9ce5be1ec6f84770f098321d3
--
2.47.1
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 75559@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 75559
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch