Skip to content

`error: archzfs: signature from "ArchZFS Bot <buildbot@archzfs.com>" is unknown trust` and how to solve it

I ran into this error error: archzfs: signature from "ArchZFS Bot <buildbot@archzfs.com>" is unknown trust on multiple machines over the last days.

Since one machine was working which is also running one of my dns servers, I was searching into this direction. After a while, I switched all my machines using this one dns server without fixing the real issue. Furthermore, by just trying to refresh keys with sudo pacman-key --refresh-keys, I ran into another error: gpg: WARNING: Tor is not running.

I could solve this with a one liner:

echo "no-use-tor" >> ~/.gnupg/dirmngr.conf

Next step was finally to delete the broken key and re-import ist again.

sudo pacman-key -d DDF7DB817396A49B2A2723F7403BD972F75D9D76
sudo pacman-key -r DDF7DB817396A49B2A2723F7403BD972F75D9D76
sudo pacman-key --lsign-key DDF7DB817396A49B2A2723F7403BD972F75D9D76

After running through all this steps, I was able to run a system update again with pacman.

Thanks to this issue report on github, this entry on redit and this entry on gnupg.org.

Translate to de es fr it pt ja

solving arch linux error message: ":: installing pacman (5.2.1-1) breaks dependency 'pacman<=5.1.3' required by yay"

If you get the error message below, there are easy steps you have to do to fix this.

:: installing pacman (5.2.1-1) breaks dependency 'pacman<=5.1.3' required by yay
  • yay -S yay-bin
  • sudo pacman -Syy
  • sudo pacman -S pacman
  • yay -Syyu

So all in all, you will replace yay with yay-bin since yay-bin is newer and supports latest pacman. Afterwards, you are updating your database followed by updating pacman to the latest version. Finally, you will do your regular system update maintenance.

Translate to de es fr it pt ja

archzfs has a new key and a new maintainer for the unofficial arch linux user repository

The unofficial but great archzfs build has a new maintainer and most important, a new key.

#pacman-key -r F75D9D76
#pacman-key --lsign-key F75D9D76

And you are ready to upgrade. The key was changed since they are now using a buildbot to reduce the time between new kernel release and adapted archzfs package. Thanks for your great work people!

Translate to de es fr it pt ja

It just happens on my Rasperry pi: signature from "Arch Linux ARM Build System <builder@archlinuxarm.org>" is unknown trust

I've started a regular update by using sudo pacman -Syyu and the following lines where the final result.

warning: Public keyring not found; have you run 'pacman-key --init'?
downloading required keys...
error: key "77193F152BDBE6A6" could not be looked up remotely
error: required key missing from keyring
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.

I did what was told me to do ;-).

sudo pacman-key --init

And after running sudo pacman -Syyu I was asked.

:: Import PGP key 4096R/68B3537F39A313B3E574D06777193F152BDBE6A6, "Arch Linux ARM Build System <builder@archlinuxarm.org>", created: 2014-01-18? [Y/n]

"As expected, I though" but than I got a long list of the error mention in the headline (for each package).

I've fixed this by executing the following command.

pacman-key --lsign-key 77193F152BDBE6A6

After that, sudo pacman -Syyu was running fine as expected. Strange note, all was working fine a week ago (2018-05-25) and the pgp key was created 2014 :-O.

Translate to de es fr it pt ja