> but I get the same ultra-lengthy output. Okay, so the issue is a different one. I did not replicate it but looked for chnages which could have introduced it.
> Once again, the --no-verbose option does not seem to help, while the -q > option seems to only suppress the old (useful) output, while retaining > the lengthy signature check output... --no-verbose simply removes as previous given --verbose (e.g. in gpg.conf). --quit instead should really shut up gpg. > a) If gpg repairs the key, while it refreshes it, why does it need > to repair it again and again, each time I refresh the same key > (which is unchanged on the keyserver)? > Is the key "broken" on the keyserver itself? The repair thing requires that all key signatures are checked and that is why I assumed it was the cuase for the verbose output. > b) While gpg is repairing the key, does it really need to be so > verbose and show one line for each verifiable signature? > Could gpg repair the key without producing all this output? > Maybe when the --no-verbose option has been passed? No real reasons, probably introduced during development. OTOH, I consider it useful to have _some_ diagnostics to see why an import takes long. Consider for example my key which has a lot of made up key signature for a fun effect. I'd appreciate if you can file a bug upstream at https://dev.gnupg.org Shalom-Salam, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
pgpXeVLseo5if.pgp
Description: PGP signature
