FS#49302 - [pacman][gnupg] pacman-key incompatible with gnupg 2.1.12

Attached to Project: Arch Linux
Opened by Pierre Schmitz (Pierre) - Wednesday, 11 May 2016, 19:19 GMT
Last edited by Gaetan Bisson (vesath) - Wednesday, 11 May 2016, 20:12 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Dan McGee (toofishes)
Allan McRae (Allan)
Gaetan Bisson (vesath)
Dave Reisner (falconindy)
Architecture All
Severity High
Priority High
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

When gnupg is upgraded from 2.1.11 to 2.1.12 (currently in [core]) pacman-key is no longer able to verify package signatures. For the same reasons dbscripts will no longer work when gnupg is updated on nymeria.

E.g.:

% pacman-key -v linux-4.5.3-1-x86_64.pkg.tar.xz.sig
==> Checking linux-4.5.3-1-x86_64.pkg.tar.xz.sig...
gpg: assuming signed data in 'linux-4.5.3-1-x86_64.pkg.tar.xz'
gpg: Signature made Sa 07 Mai 2016 21:05:38 CEST using RSA key ID 7EDF681F
gpg: Note: trustdb not writable
gpg: Good signature from "Tobias Powalowski <tobias.powalowski@googlemail.com>" [full]
gpg: aka "Tobias Powalowski <tpowa@archlinux.org>" [full]
==> ERROR: The signature identified by linux-4.5.3-1-x86_64.pkg.tar.xz.sig could not be verified.
This task depends upon

Closed by  Gaetan Bisson (vesath)
Wednesday, 11 May 2016, 20:12 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#49241 

Loading...