You are not logged in.
- Topics: Active | Unanswered
#26 2018-01-06 21:27:37
Re: [SOLVED] Can't update system due to allegedly bad PGP sigs
deep42thought wrote:
Hmm, your private key seems ok, then the question would be what date the signature on the master keys has, e.g.
pacman-key --list-sigs CE0BDE71A759A87F23F0F7D8B61DBCE10901C163 pacman-key --list-sigs A0B250C0FC9FC079EC04ADB7A50C0F20AEC3AF00 pacman-key --list-sigs 194E37A47A4C671807BACB37B1117BC1094EA6E9
karl ~ » pacman-key --list-sigs CE0BDE71A759A87F23F0F7D8B61DBCE10901C163
gpg: Note: trustdb not writable
pub rsa2048 2012-03-01 [SC]
CE0BDE71A759A87F23F0F7D8B61DBCE10901C163
uid [marginal] Balló György <ballogyor@gmail.com>
sig 3 B61DBCE10901C163 2012-03-01 Balló György <ballogyor@gmail.com>
sig 5184252D824B18E8 2012-03-16 Thomas Bächler (Arch Linux Master Key) <thomas@master-key.archlinux.org>
sig 7EFD567D4C7EA887 2012-03-16 Ionut Biru (Arch Linux Master Key) <ionut@master-key.archlinux.org>
sig 3348882F6AC6A4C2 2012-03-19 Pierre Schmitz (Arch Linux Master Key) <pierre@master-key.archlinux.org>
sig 872E6714EAF5EC44 2014-04-09 [User ID not found]
sub rsa2048 2012-03-01 []
sub rsa2048 2012-03-01 []
sig L DCB1973EA3EC7AA6 2017-11-16 Pacman Keyring Master Key <pacman@localhost>
sub rsa2048 2012-03-01 []
sig A04F9397CDFD6BB0 2014-09-01 Dan McGee (Arch Linux Master Key) <dan@master-key.archlinux.org>
sig BA1DFB64FFF979E7 2012-03-20 Allan McRae (Arch Linux Master Key) <allan@master-key.archlinux.org>
sig A88E23E377514E00 2015-12-23 Florian Pritz (Arch Linux Master Key) <florian@master-key.archlinux.org>
sub rsa2048 2012-03-01 [E]
sig B61DBCE10901C163 2012-03-01 Balló György <ballogyor@gmail.com>
karl ~ » pacman-key --list-sigs A0B250C0FC9FC079EC04ADB7A50C0F20AEC3AF00
gpg: Note: trustdb not writable
pub rsa4096 2017-05-15 [SC] [expires: 2018-05-15]
A0B250C0FC9FC079EC04ADB7A50C0F20AEC3AF00
uid [ full ] Polichronucci (Arch Linux 32 Master Key) <polichronucci@archlinux.gr>
sig L DCB1973EA3EC7AA6 2017-11-16 Pacman Keyring Master Key <pacman@localhost>
sig 3 A50C0F20AEC3AF00 2017-05-15 Polichronucci (Arch Linux 32 Master Key) <polichronucci@archlinux.gr>
karl ~ » pacman-key --list-sigs 194E37A47A4C671807BACB37B1117BC1094EA6E9
gpg: Note: trustdb not writable
pub rsa2048 2017-05-27 [SC] [expires: 2019-05-27]
194E37A47A4C671807BACB37B1117BC1094EA6E9
uid [ full ] Erich Eckner <deep42thought@archlinux32.org>
sig 3 B1117BC1094EA6E9 2017-05-27 Erich Eckner <deep42thought@archlinux32.org>
sig L DCB1973EA3EC7AA6 2017-11-16 Pacman Keyring Master Key <pacman@localhost>
sub rsa2048 2017-05-27 [E] [expires: 2019-05-27]
sig B1117BC1094EA6E9 2017-05-27 Erich Eckner <deep42thought@archlinux32.org>
sub rsa2048 2017-05-27 []
sub rsa2048 2017-05-27 []
sub rsa2048 2017-05-27 []
sub rsa2048 2017-05-27 [A] [expires: 2019-05-27]
sig B1117BC1094EA6E9 2017-05-27 Erich Eckner <deep42thought@archlinux32.org>Offline
#27 2018-01-06 21:33:18
- deep42thought
- Administrator
- From: Jena, Germany
- Registered: 2017-06-17
- Posts: 617
Re: [SOLVED] Can't update system due to allegedly bad PGP sigs
If DCB1973EA3EC7AA6 is your private key and your date is set correctly, then this looks alright to me and I have no further idea what might be wrong 
Offline
#30 2018-01-07 01:25:37
Re: [SOLVED] Can't update system due to allegedly bad PGP sigs
Turns out that running
rm -r /etc/pacman.d/gnupg/
pacman-key --init
pacman-key --populate archlinux
pacman-key --populate archlinux32
pacman -Sc
pacman -Syuuseems to have worked. I note that several packages were installed with the .pacnew extension.
Removing the gnupg subdir is suggested here.
Thanks to all who helped.
Offline
#31 2018-02-23 03:28:17
- Texbrew
- Member
- From: Deep in the Heart of Texas
- Registered: 2017-11-14
- Posts: 9
Re: [SOLVED] Can't update system due to allegedly bad PGP sigs
I hope I'm not guilty of thread bumping by saying Thanks to @kdsch. Your solution worked for me.
Cheers!
tex
Offline