GPG 2.2.28 introduces a breakage where Yubikey NEO is not recognized anymore. The failure is cryptic and it took me a while to find the upstream bug even. I'm filing this bug to make sure that we don't stabilize it by accident. Can we backport the patch or bump gnupg to 2.2.29?
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f05a4068e141b31247ba40d94f698b18f8e343ed commit f05a4068e141b31247ba40d94f698b18f8e343ed Author: Lars Wendler <polynomial-c@gentoo.org> AuthorDate: 2021-08-13 15:30:56 +0000 Commit: Lars Wendler <polynomial-c@gentoo.org> CommitDate: 2021-08-13 15:31:47 +0000 app-crypt/gnupg: Bump to version 2.2.29 Bug: https://bugs.gentoo.org/807631 Signed-off-by: Lars Wendler <polynomial-c@gentoo.org> app-crypt/gnupg/Manifest | 1 + app-crypt/gnupg/gnupg-2.2.29.ebuild | 152 ++++++++++++++++++++++++++++++++++++ 2 files changed, 153 insertions(+)
commit 1f9c4376818cb36d8024c4f65d02544d403aea6c Author: Lars Wendler <polynomial-c@gentoo.org> Date: Mon Sep 6 10:38:46 2021 app-crypt/gnupg: Removed old Signed-off-by: Lars Wendler <polynomial-c@gentoo.org> app-crypt/gnupg/Manifest | 1 - app-crypt/gnupg/gnupg-2.2.28.ebuild | 153 ------------------------------------ 2 files changed, 154 deletions(-)
