Can't install manjaro-keyring, arch-keyring : package missing required signature

[wanageeska]

Hi all,

Lately I have been unable to update any AUR packages and am receiving the package missing required signature error. I have been making do by temporarily changing the siglevel in pacman.conf in order to install/update things, but I really would like to fix the underlying issue.

I have tried fixing it by following the official instructions here: Pacman troubleshooting - Manjaro. However, at the step to install the .zst files I receive receive the same ```package missing required signature’ error for each. Actual output pasted below:

sudo pacman -U manjaro-keyring*.pkg.tar.zst archlinux-keyring*.pkg.tar.zst
loading packages...
error: 'manjaro-keyring-20230719-3-any.pkg.tar.zst': package missing required signature
error: 'archlinux-keyring-20240709-1-any.pkg.tar.zst': package missing required signature

I’m not entirely sure why I’m only now receiving these errors. A month or two ago I did lose my aur-build directory and so had to create a new one. I removed/uninstalled the existing AUR packages from my machine and tried to rebuild them in the new directory, but every package fails and throws the ‘package missing required signature’ error.

Does anyone know what’s happening here? I don’t have a great deal of knowledge on pacman internals but it seems like pacman or pamac might still be pointing to a non-existent db or a file containing the old path? Or something…

Any guidance would be most appreciated!

-w

Edit:
I have also tried this solution to no avail.

Can't install manjaro keyring

This fixed it for me: sudo rm -r /etc/pacman.d/gnupg sudo pacman-key --init sudo pacman-key --populate archlinux manjaro sudo pacman-key --refresh-keys sudo pacman -Syu the populate part seemed to be inportant, it disabled a certain number of keys. edit: pamac still doesn’t work. How do I tell pamac the same information that pacman has now? edit again: after running sudo pamac update - even without finishing the update that way - pamac gui also got everything it needs to run without issue…

[Takakage]

What is the output from

grep LocalFileSigLevel /etc/pacman.conf

[Arrababiski]

Run the solve-everyrhing script:

[HowTo] Work around gpg verification issue on left behind systems

Difficulty: ★☆☆☆☆ This script is the result of people here in the forum having problems with Manjaro installations that haven’t been updated for more than 2 months or booting an old ISO plus installing it which is older than 2 months. I was a bit tired of explaining how to solve that issue and created a script, which does the job. Methods Method 1 - Basic Remove lock files of pamac and pacman Refresh Package Database Populate local keyrings to the GnuPG Database of pacman Refresh GnuPG Data…

[wanageeska]

grep LocalFileSigLevel /etc/pacman.conf
#LocalFileSigLevel = Optional

I have never touched the LocalFileSigLevel line (to my knowledge anyway). I tried to avoid fiddling with things I don’t fully understand.

To update I have just been commenting/uncommenting these two lines as per a workaround I found on the forum:

SigLevel = Required DatabaseOptional
SigLevel = Optional DatabaseNever

[wanageeska]

Yowzers, looks quite thorough! I’ll give it a shot later today and report back. That is if I haven’t managed to brick my computer somehow… Eep. Thanks @Arrababiski

[Takakage]

@wanageeska

#LocalFileSigLevel = Optional

From what I have seen, the default is for that line to not be commented. That is what is keeping you from installing the downloaded keyrings. It may also be keeping you from installing any AUR package that you build, since those locally built packages will also be unsigned.

[wanageeska]

Bingo! You are correct! In the interim I managed to find the default pacman.conf on github and it does indeed have LocalFileSigLevel = Optional uncommented. Link below for anyone ever wanting to check their own config. Thank you to all!

archlinux/svntogit-packages/blob/packages/pacman/trunk/pacman.conf

[Nachlese]

Perhaps easier than searching for it on the internet:
“Normally”, you also have one or a few versions of the installed packages in cache:
/var/cache/pacman/pkg/
in this case:
ls -al /var/cache/pacman/pkg/pacman*
pacman-6.1.0-7-x86_64.pkg.tar.zst

If you don’t have it in cache, you can fetch it:
sudo pacman -Sw pacman
and then find it in the cache

unpack the archive and find the original config file

Works for any package you might need the original of again, to have a look at the contents of the original files.

[wanageeska]

Thanks @Nachlese, handy to learn!