From what I understand, this isn't a bug, gpg automatically calculates when the trustdb should be checked, it's just that it happens a lot since we're doing a lot of operations. We're not really hiding an issue, just information that the average user won't be interested in (at least I think the average user doesn't really care about gpg checking the trustdb unless it fails, in which case the error will still get printed even with this change).
On Wed, 25 Aug 2021 at 22:47, Allan McRae <allan@archlinux.org> wrote:
On 26/8/21 6:42 am, Daan De Meyer wrote:
Currently, when running pacman-key --populate, gpg prints the trustdb check output once for each locally signed and revoked key. When bootstrapping a new container image, about 50 keys get signed and revoked which leads to a huge amount of output when running pacman-key which is the following text repeated 50x
``` gpg: checking the trustdb gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
Shouldn't this issue be fix rather than hiding it?