Arch Linux

dreieck

Member

Registered: 2012-10-08

Posts: 74

pacman-key lsign-key: update trust database: error message on 1st run.

Ahoj,

when I do a `pacman-key --lsign-key <key-ID>`, in the first run in the update of the trust database it always finishes with exitcode 1 and the output

ERROR: Trust database could not be updated.

However, the signing has worked.

A subsequent run does terminate with exitcode 0 and a "having done nothing"-response (as expected when the first run already did work).

I am here on a testing installation, but it also happens on my productive installation.

An example of the testing installation:

First run of `pacman-key --lsign-key eworm@archlinux.org`: 

  -> Locally signed 1 keys.
==> Updating trust database...
gpg: public key of ultimately trusted key E5B904847340E87C not found
gpg: public key of ultimately trusted key E710B62402966D9B not found
gpg: public key of ultimately trusted key 58CBD1867E888DEA not found
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:   4  signed:  77  trust: 0-, 0q, 0n, 0m, 0f, 4u
gpg: depth: 1  valid:  77  signed:  89  trust: 73-, 0q, 0n, 4m, 0f, 0u
gpg: next trustdb check due at 2023-07-12
==> ERROR: Trust database could not be updated.

Second run of `pacman-key --lsign-key eworm@archlinux.org`: 

  -> Locally signed 1 keys.
==> Updating trust database...
gpg: next trustdb check due at 2023-07-12

(It also happens on my production system where the arch linux keys are all OK and trusted when I manually add other keys.)

Versions: Pacman v6.0.2 - libalpm v13.0.2

Regards!

Last edited by dreieck (2023-07-04 18:43:59)