GNU bug report logs - #62294
gnupg is pinned at 2.2.32 for bug that is fixed upstream

Previous Next

Package: guix;

Reported by: Ethan Blanton <elb <at> kb8ojh.net>

Date: Mon, 20 Mar 2023 13:02:01 UTC

Severity: normal

Done: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>

Bug is archived. No further changes may be made.

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Ethan Blanton <elb <at> kb8ojh.net>
Subject: bug#62294: closed (Re: bug#62294: gnupg is pinned at 2.2.32 for
 bug that is fixed upstream)
Date: Sun, 07 May 2023 15:04:02 +0000

[Message part 1 (text/plain, inline)]
Your bug report

#62294: gnupg is pinned at 2.2.32 for bug that is fixed upstream

which was filed against the guix package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 62294 <at> debbugs.gnu.org.

-- 
62294: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=62294
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]
From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Ethan Blanton <elb <at> kb8ojh.net>
Cc: Leo Famulari <leo <at> famulari.name>, 62294-done <at> debbugs.gnu.org,
 Simon Tournier <zimon.toutoune <at> gmail.com>
Subject: Re: bug#62294: gnupg is pinned at 2.2.32 for bug that is fixed
 upstream
Date: Sun, 07 May 2023 11:03:40 -0400

Hello,

We're now at 2.2.39 on master.  Closing!

-- 
Thanks,
Maxim


[Message part 3 (message/rfc822, inline)]
From: Ethan Blanton <elb <at> kb8ojh.net>
To: bug-guix <at> gnu.org
Subject: gnupg is pinned at 2.2.32 for bug that is fixed upstream
Date: Mon, 20 Mar 2023 09:01:33 -0400

It looks like the gnupg package is pinned at 2.2.32 with the following
note:

    ;; Note2: 2.2.33 currently suffers from regressions, so do not update to it
    ;; (see: https://dev.gnupg.org/T5742).

However, the bug referenced here is fixed in upstream commit
4cc724639c012215f59648cbb4b7631b9d352e36, which shipped in gnupg
2.2.34.  Meanwhile, all gnupg releases older than 2.2.35 suffer from
an S/MIME key-parsing bug (referenced in
https://www.mail-archive.com/gnupg-users <at> gnupg.org/msg40758.html).

I believe the pin on 2.2.32 can be lifted, but as gnupg is important
infrastructure I am unsure about directly submitting a patch to update
to a newer version.

Ethan
This bug report was last modified 2 years and 13 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.