You are not logged in.
Hello.
I am not sure if this relates to installation but still.
After the fresh install of 2020.06.01 snapshot I have noticed that my keyring in /etc/pacman.d/gnupg is not up to date.
Which is weird because I had archlinux-keyring installed, version 20200622-1.
I was so surprised I have performed another quick and dirty install on the VM but the problem remained.
If I wipe this directory and reinit the keyring this fixes the prob.
Is this normal and I am just missing something, like to init the keyring manually?
I just seem to cannot find anything like this in the install guide.
Or is it something went wrong?
Last edited by Synchrotron (2020-07-13 16:07:49)
Offline
How are you determining that it's not up to date?
Offline
gpg --homedir /etc/pacman.d/gnupg --list-keys | wc -l
gives me 826 rows for a VM which is already long time in service versus 795 on a fresh install.
Investigating the difference in keys reveals that the new install has only one key for Jan Alexander Steffens (heftig) while long-running install has two.
BTW, gpg reports about
gpg: WARNING: unsafe permissions on homedir '/etc/pacman.d/gnupg'
Last edited by Synchrotron (2020-07-08 09:37:18)
Offline
I have realized where this comes from.
Looking at the install file for archlinux-keyring it can be seen that it relies on pacman-key to populate the keyring.
In my case archlinux-keyring was installed before pacman package which provides this script.
Offline
The install file is executed at the end of the transaction. The transaction did not contain pacman?
Offline
Oh, I didn't know that.
It did.
Which means I am out of ideas once again.
Offline
Nope, the .install file is executed right after the package is installed. Hooks are executed at the end.
Offline
Changing the install file to a hook providing the same functionality cause the keyring to be updated perhaps open a bug report.
Offline
Offline
Thank you guys.
The mystery is solved.
Offline