25 Aug
2021
25 Aug
'21
6:56 p.m.
On 26/8/21 8:01 am, Daan De Meyer wrote:
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).
Having this repeated 50 times sounds like an issue that should be fixed: gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10