Summary: | =app-crypt/gnupg-2.1.20: keyring_get_keyblock: read error: Invalid packet / failed to rebuild keyring cache: Invalid keyring | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Kristian Fiskerstrand (RETIRED) <k_f> |
Component: | Current packages | Assignee: | Kristian Fiskerstrand (RETIRED) <k_f> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | crypto+disabled |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commit;h=22739433e98be80e46fe7d01d52a9627c1aebaae | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 617960 |
Description
Kristian Fiskerstrand (RETIRED)
2017-04-22 19:08:18 UTC
I'm contemplating p.masking 2.1.20 until this is narrowed down (In reply to Kristian Fiskerstrand from comment #1) > I'm contemplating p.masking 2.1.20 until this is narrowed down Seems it only affects the old keyring format (pubring.gpg) and not the newer keybox format (pubring.kbx) that is created by default for new setups (old setups can migrate to it by moving pubring.gpg out of gnupg homedir and doing an --import along with a trustdb export and import) This is fixed upstream in https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commit;h=22739433e98be80e46fe7d01d52a9627c1aebaae commit 68d406d2de327f13ad3906d50c458c9727f7e024 Author: Kristian Fiskerstrand <k_f@gentoo.org> Date: Tue May 9 14:59:22 2017 +0200 app-crypt/gnupg: Fix regression from 2.1.19 Gentoo-Bug: 616336 Package-Manager: Portage-2.3.3, Repoman-2.3.1 |