Skip to main content
Topic: can't install any packages - Public keyring not found - wiki does not solve (Read 686 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

can't install any packages - Public keyring not found - wiki does not solve

upon a new artix plasma weekly install, which was installed offline by the way because the online install kept failing, when i run `sudo pacman -Syu` it gives me:

Code: [Select]
warning: Public keyring not found; have you run 'pacman-key --init'?

so i run that, and it seems to do some stuff just fine, then when i run `sudo pacman -Syu` again, it asks me:

Code: [Select]
:: Import PGP key 1247D995F165BBAC, "Dudemanguy <[email protected]>"? [Y/n]

so i hit enter for the default Y, and it spits this out:

Code: [Select]
(4/4) checking package integrity                                   [####################################] 100%
error: exfatprogs: signature from "Artix Buildbot <[email protected]>" is unknown trust
:: File /var/cache/pacman/pkg/exfatprogs-1.2.4-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]

so i hit enter for the default Y, and it asks that about a few more packages and then spits out:

Code: [Select]
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.

so at some point i find the wiki, but it doesn't help. step 1 fails. step 2 deletes files. step 1 fails again. infinite loop. i tried other steps, but to no avail. step 1 either tells me to init, or tells me files are corrupted, but in no scenario does it work.




Re: can't install any packages - Public keyring not found - wiki does not solve

Reply #1
Code: [Select]
pacman-key --populate
makes it work. i suggest updating the wiki. and i suggest fixing this issue so that it doesn't happen on new installs.

Re: can't install any packages - Public keyring not found - wiki does not solve

Reply #2
Code: [Select]
pacman-key --populate
makes it work. i suggest updating the wiki. and i suggest fixing this issue so that it doesn't happen on new installs.
Hello,
The wiki says:
Code: [Select]
pacman-key --populate archlinux artix
https://wiki.artixlinux.org/Main/Troubleshooting#Invalid_or_corrupted_packages_.28PGP_signature.29

Re: can't install any packages - Public keyring not found - wiki does not solve

Reply #3
Code: [Select]
pacman-key --populate
makes it work. i suggest updating the wiki. and i suggest fixing this issue so that it doesn't happen on new installs.

On my Arch box, I have this as an alias

alias update='doas pacman -Sy --needed archlinux-keyring && doas pacman -Sy && doas pacman -Qu'

Of course, this has always taken care of key issues for me. Modify to taste.
Supercalifragilisticexpialidocious

Re: can't install any packages - Public keyring not found - wiki does not solve

Reply #4
I had this too with my recent install from a weekly iso, i resorted to temporarily putting SigLevel = Never and manually installing artix-keyring.

Re: can't install any packages - Public keyring not found - wiki does not solve

Reply #5
tintin, no, the wiki does not say that if steps 1 and 2 fail, then run step 4, and the command in the wiki is different.

hitman, i tried siglevel = never and that didn't work. i couldn't bypass it.

cds, that looks like a nifty one-liner, but my point is that artix linux is broken out of the box. it does not "Just Work", and the wiki wasn't helpful, i had to look elsewhere.

Re: can't install any packages - Public keyring not found - wiki does not solve

Reply #6
so how could one fix this upstream, so that 'pacman-key --populate' is run automatically instead of the user having to troubleshoot?

 

Re: can't install any packages - Public keyring not found - wiki does not solve

Reply #7
tintin, no, the wiki does not say that if steps 1 and 2 fail, then run step 4, and the command in the wiki is different.

The wiki says:
"If you can't install the artix-keyring because of signature errors, perform step 2 and repeat 1, otherwise proceed to step 3".

Obviously, all these commands must be executed as root or preceded by sudo.