Skip to main content ↑ ↓
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: [SOLVED] Problematic Keys (Read 6157 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: Problematic Keys

Reply #15 –
Quote from: scottfurry – on
@thefallenrat - I mentioned bash earlier. That one may need to updating as well.

That version of bash were already in [system] stable few weeks ago. Please check your mirrors
Quote from: scottfurry – on
Artix Buildbot is marginal trust
Quote from: thefallenrat – on
If you are receiving the marginal trust issue, you can manually trust it by doing the following :
* Assuming Artix Buildbot key is the culprit


  • Edit the key (0A3EB6BB142C56653300420C1247D995F165BBAC)
Code: [Select]
sudo pacman-key --edit-key 0A3EB6BB142C56653300420C1247D995F165BBAC

  • On gpg console, run trust , and choose ultimate
Code: [Select]
Please decide how far you trust this user to correctly verify other users' keys
(by looking at passports, checking fingerprints from different sources, etc.)

  1 = I don't know or won't say
  2 = I do NOT trust
  3 = I trust marginally
  4 = I trust fully
  5 = I trust ultimately
  m = back to the main menu

Your decision? 5
  • Exit from gpg console by running quit and try to re-update again (sudo pacman -Syyu)

If I can hit that bullseye, the rest of the dominoes will fall like a house of cards. Checkmate!

Re: Problematic Keys

Reply #16 –
@thefallenrat - that seems to have done the trick.

In searching the web with the error message I ended up on an arch linux wiki page about package signing. The page talked about web of trust. Since the buildbot key was "self-signed", I suspected that was the source of my problems - gpg didn't know what to do causing pacman to choke.

I suspect bash was a "marginal trust" issue as well and not a package signing error like imagemagick. The bash package was a harbinger of the problems to come.

So - huge thank you to @thefallenrat for helping me fix this.