Ansgar Burchardt writes:
> I imported two keys using `gpg --recv-keys 0x... 0x...` (this is gpg2
> here) this morning. After reporting that both keys had been retrieved
> successfully, gpg decided to spend some minutes doing something: I
> think checking the trustdb.
>
> However there was no indication that gpg was supposed to still be
> doing anything. It would be nice if there was an informational message
> on the terminal for long-term operations: at least a note that this
> might take a while, ideally some sort of progress indication.
The same happens when importing a single new signature:
+---
| $ gpg --import < ${something}
| gpg: key [...] 3 new signatures
| gpg: Total number processed: 1
| gpg: new signatures: 3
| gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
| gpg: depth: 0 valid: 1 signed: 140 trust: 0-, 0q, 0n, 0m, 0f, 1u
| gpg: depth: 1 valid: 140 signed: 150 trust: 1-, 13q, 35n, 77m, 14f, 0u
| gpg: depth: 2 valid: 57 signed: 80 trust: 9-, 5q, 9n, 31m, 3f, 0u
| gpg: depth: 3 valid: 9 signed: 17 trust: 2-, 0q, 3n, 4m, 0f, 0u
| gpg: depth: 4 valid: 3 signed: 5 trust: 0-, 0q, 0n, 3m, 0f, 0u
| gpg: next trustdb check due at 2016-09-07
+---
With gpg(2) taking quite a while:
+---
| 11077 ? RLs 4:49 gpg --import
+---
I guess I should no longer refresh the keyring or sign other people's
keys. Who knows how long it will take for importing more than one new
signature or key. ;)
Ansgar
