error: xxx: signature from "Christoph Reiter (MSYS2 master key) <reiter.christoph@gmail.com>" is unknown trust

[ibuclaw]

Describe the issue

$ pacman -Syu
error: mingw32: signature from "Christoph Reiter (MSYS2 master key) <reiter.christoph@gmail.com>" is unknown trust
error: mingw64: signature from "Christoph Reiter (MSYS2 master key) <reiter.christoph@gmail.com>" is unknown trust
error: msys: signature from "Christoph Reiter (MSYS2 development key) <reiter.christoph@gmail.com>" is unknown trust
:: Synchronizing package databases...
 mingw32                                                  953.3 KiB  2.84 MiB/s 00:00 [#################################################] 100%
 mingw32.sig                                              566.0   B  0.00   B/s 00:00 [#################################################] 100%
error: mingw32: signature from "Christoph Reiter (MSYS2 master key) <reiter.christoph@gmail.com>" is unknown trust
error: failed to update mingw32 (invalid or corrupted database (PGP signature))
 mingw64                                                  956.9 KiB  7.60 MiB/s 00:00 [#################################################] 100%
 mingw64.sig                                              566.0   B  0.00   B/s 00:00 [#################################################] 100%
error: mingw64: signature from "Christoph Reiter (MSYS2 master key) <reiter.christoph@gmail.com>" is unknown trust
error: failed to update mingw64 (invalid or corrupted database (PGP signature))
 msys                                                     305.5 KiB  4.66 MiB/s 00:00 [#################################################] 100%
 msys.sig                                                 566.0   B  0.00   B/s 00:00 [#################################################] 100%
error: msys: signature from "Christoph Reiter (MSYS2 development key) <reiter.christoph@gmail.com>" is unknown trust
error: failed to update msys (invalid or corrupted database (PGP signature))
error: failed to synchronize all databases

Steps to Reproduce the Problem

1. Install latest msys2 'https://repo.msys2.org/distrib/x86_64/msys2-x86_64-20210228.exe'
2. Run 'pacman -Syu'
3. Describe what happens? Fails
4. What did you expect to happen instead? Not fail

[Biswa96]

Do these command help?

rm -r /etc/pacman.d/gnupg/
pacman-key --init
pacman-key --populate msys2

From here https://www.msys2.org/news/#2020-06-29-new-packagers

[ibuclaw]

Do these command help?

rm -r /etc/pacman.d/gnupg/
pacman-key --init
pacman-key --populate msys2

From here https://www.msys2.org/news/#2020-06-29-new-packagers

They do not, GPG is simply broken here.

$ pacman-key --populate msys2
==> Appending keys from msys2.gpg...
gpg: starting migration from earlier GnuPG versions
gpg: can't connect to the agent: IPC connect call failed
gpg: error: GnuPG agent unusable. Please check that a GnuPG agent can be started.
gpg: migration aborted
gpg: can't connect to the agent: IPC connect call failed
gpg: can't connect to the agent: IPC connect call failed
gpg: can't connect to the agent: IPC connect call failed

$ gpg-connect-agent /bye
gpg-connect-agent: no running gpg-agent - starting '/usr/bin/gpg-agent'
gpg-connect-agent: waiting for the agent to come up ... (5s)
gpg-connect-agent: waiting for the agent to come up ... (4s)
gpg-connect-agent: waiting for the agent to come up ... (3s)
gpg-connect-agent: waiting for the agent to come up ... (2s)
gpg-connect-agent: waiting for the agent to come up ... (1s)
gpg-connect-agent: can't connect to the agent: IPC connect call failed
gpg-connect-agent: error sending standard options: No agent running

[lazka]

Might be due to anti virus or other security software.

[ibuclaw]

Might be due to anti virus or other security software.

Not sure about that, this being ran on the free Windows developer VM, so wouldn't have any antivirus software on it.

[Biswa96]

In antivirus category, we also include Windows Defender program.

[mati865]

Is this Windows Insider or regular release?

[Biswa96]

auto this->https://developer.microsoft.com/en-us/windows/downloads/virtual-machines/

[lispstudent]

I had same issue, I believe my firewall was too quick to prevent the complete download of the proper signatures. I was able to authorise them, but perhaps too late.

The mentioned commands solved it,

rm -r /etc/pacman.d/gnupg/
pacman-key --init
pacman-key --populate msys2

[efa]

after populate I got another error:

user@host MSYS ~
$ pacman-key --populate msys2
==> Appending keys from msys2.gpg...
==> Locally signing trusted keys in keyring...
  -> Locally signing key D55E7A6D7CE9BA1587C0ACACF40D263ECA25678A...
  -> Locally signing key 123D4D51A1793859C2BE916BBBE514E53E0D0813...
  -> Locally signing key B91BCF3303284BF90CC043CA9F418C233E652008...
  -> Locally signing key 9DD0D4217D75A33B896159E6DA7EF2ABAEEA755C...
==> Importing owner trust values...
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: inserting ownertrust of 4
==> Updating trust database...
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:   1  signed:   4  trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1  valid:   4  signed:   3  trust: 0-, 0q, 0n, 4m, 0f, 0u
gpg: depth: 2  valid:   3  signed:   0  trust: 3-, 0q, 0n, 0m, 0f, 0u

user@host MSYS ~
$ pacman -Syu
error: mingw32: key "5F944B027F7FE2091985AA2EFA11531AA0AA7F57" is unknown
:: Import PGP key 5F944B027F7FE2091985AA2EFA11531AA0AA7F57? [Y/n] y
error: key "5F944B027F7FE2091985AA2EFA11531AA0AA7F57" could not be looked up remotely
error: mingw64: key "5F944B027F7FE2091985AA2EFA11531AA0AA7F57" is unknown
:: Import PGP key 5F944B027F7FE2091985AA2EFA11531AA0AA7F57? [Y/n]
...

the error "could not be looked up remotely" happen for each new key, update cannot proceed

[vladimir-kokovic]

What else is to say about this still unresolved problem ?

Windows 10 Pro, 20H2, 4/‎30/‎2021, 19042.928, Windows Feature Experience Pack 120.2212.551.0

msys2-x86_64-20210419.exe

``
vlada@vlada-kuci-win MSYS ~

rm -r /etc/pacman.d/gnupg/

vlada@vlada-kuci-win MSYS ~

pacman-key --init

gpg: /etc/pacman.d/gnupg/trustdb.gpg: trustdb created
gpg: no ultimately trusted keys found
gpg: starting migration from earlier GnuPG versions
gpg: can't connect to the agent: IPC connect call failed
gpg: error: GnuPG agent unusable. Please check that a GnuPG agent can be started.
gpg: migration aborted
gpg: starting migration from earlier GnuPG versions
gpg: can't connect to the agent: IPC connect call failed
gpg: error: GnuPG agent unusable. Please check that a GnuPG agent can be started.
gpg: migration aborted
gpg: Generating pacman keyring master key...
gpg: can't connect to the agent: IPC connect call failed
gpg: agent_genkey failed: No agent running
gpg: key generation failed: No agent running
gpg: Done
==> Updating trust database...
gpg: no need for a trustdb check
vlada@vlada-kuci-win MSYS ~

pacman-key --populate msys2

==> Appending keys from msys2.gpg...
gpg: starting migration from earlier GnuPG versions
gpg: can't connect to the agent: IPC connect call failed
gpg: error: GnuPG agent unusable. Please check that a GnuPG agent can be started.
gpg: migration aborted
gpg: can't connect to the agent: IPC connect call failed
gpg: can't connect to the agent: IPC connect call failed
gpg: can't connect to the agent: IPC connect call failed
gpg: can't connect to the agent: IPC connect call failed
gpg: can't connect to the agent: IPC connect call failed
gpg: can't connect to the agent: IPC connect call failed
gpg: can't connect to the agent: IPC connect call failed
gpg: can't connect to the agent: IPC connect call failed
gpg: can't connect to the agent: IPC connect call failed
gpg: can't connect to the agent: IPC connect call failed
gpg: can't connect to the agent: IPC connect call failed
gpg: can't connect to the agent: IPC connect call failed
==> Locally signing trusted keys in keyring...
-> Locally signing key 123D4D51A1793859C2BE916BBBE514E53E0D0813...
==> ERROR: 123D4D51A1793859C2BE916BBBE514E53E0D0813 could not be locally signed.
-> Locally signing key B91BCF3303284BF90CC043CA9F418C233E652008...
==> ERROR: B91BCF3303284BF90CC043CA9F418C233E652008 could not be locally signed.
-> Locally signing key 6E8FEAFF9644F54EED90EEA0790AE56A1D3CFDDC...
==> ERROR: 6E8FEAFF9644F54EED90EEA0790AE56A1D3CFDDC could not be locally signed.
-> Locally signing key 69985C5EB351011C78DF7F6D755B8182ACD22879...
==> ERROR: 69985C5EB351011C78DF7F6D755B8182ACD22879 could not be locally signed.
-> Locally signing key 9DD0D4217D75A33B896159E6DA7EF2ABAEEA755C...
==> ERROR: 9DD0D4217D75A33B896159E6DA7EF2ABAEEA755C could not be locally signed.
-> Locally signing key D55E7A6D7CE9BA1587C0ACACF40D263ECA25678A...
==> ERROR: D55E7A6D7CE9BA1587C0ACACF40D263ECA25678A could not be locally signed.
vlada@vlada-kuci-win MSYS ~

pacman -Syu

error: mingw32: signature from "David Macek david.macek.0@gmail.com" is unknown trust
error: mingw64: signature from "David Macek david.macek.0@gmail.com" is unknown trust
error: msys: signature from "David Macek david.macek.0@gmail.com" is unknown trust
:: Synchronizing package databases...
mingw32 975.3 KiB 4.60 MiB/s 00:00 [################################] 100%
mingw32.sig 566.0 B 0.00 B/s 00:00 [################################] 100%
error: mingw32: signature from "Christoph Reiter (MSYS2 development key) reiter.christoph@gmail.com" is unknown trust
error: failed to update mingw32 (invalid or corrupted database (PGP signature))
mingw64 988.3 KiB 4.73 MiB/s 00:00 [################################] 100%
mingw64.sig 566.0 B 0.00 B/s 00:00 [################################] 100%
error: mingw64: signature from "Christoph Reiter (MSYS2 development key) reiter.christoph@gmail.com" is unknown trust
error: failed to update mingw64 (invalid or corrupted database (PGP signature))
msys 314.3 KiB 2.18 MiB/s 00:00 [################################] 100%
msys.sig 566.0 B 0.00 B/s 00:00 [################################] 100%
error: msys: signature from "Christoph Reiter (MSYS2 development key) reiter.christoph@gmail.com" is unknown trust
error: failed to update msys (invalid or corrupted database (PGP signature))
error: failed to synchronize all databases

vlada@vlada-kuci-win MSYS ~

``

Vladimir Koković, DP senior(70),
Serbia, Belgrade, 11.May 2021

[efa]

I solved by:

1. save the list of installed packages (just in case)
2. copy the msys2 install directory
3. un-install msys2
4. kill all MSYS2 process
5. re-install base 350 MB msys2
6. fully update the freshly 350 MB base install
7. close MSYS2 shell
8. restore old install dir
9. fully update the old full install
   see:
   Execution failed (unexpected exit code: -1073741819) msys2.github.io#124

[ibuclaw]

I solved by:

1. save the list of installed packages (just in case)

This happens from a first installation of msys2 on an new Windows image. So no, not a solution.

[ibuclaw]

Current workaround is just to disable signature verification until GPG is fixed.

[vladimir-kokovic]

Iain,
But what is the procedure to resolve it?
I tried a change in /etc/paman.conf:
Siglevel = Never
#Siglevel = required databaseoptional
And nothing has changed!