Since gnupg 1.4.19, gpg is emitting seemingly non-fatal debug messages that
clutter the interface:

$ gpg --recv-keys 1E42B367
gpg: requesting key 1E42B367 from hkp server keys.gnupg.net
gpg: DBG: armor-keys-failed (KEY 0x1E42B367 BEGIN
) ->0
gpg: DBG: armor-keys-failed (KEY 0x1E42B367 END
) ->0
gpg: key 1E42B367: public key "Werner Koch <wk@gnupg.org>" imported
gpg: no ultimately trusted keys found
gpg: Total number processed: 1
gpg: imported: 1

$ gpg --refresh-keys
gpg: refreshing 1 key from hkp://keys.gnupg.net
gpg: requesting key 1E42B367 from hkp server keys.gnupg.net
gpg: DBG: armor-keys-failed (KEY 0x80615870F5BAD690333686D0F2AD85AC1E42B367 BEGIN
) ->0
gpg: DBG: armor-keys-failed (KEY 0x80615870F5BAD690333686D0F2AD85AC1E42B367 END
) ->0
gpg: key 1E42B367: "Werner Koch <wk@gnupg.org>" not changed
gpg: Total number processed: 1
gpg: unchanged: 1

The particular log_debug has been introduced here:

http://lists.gnutls.org/pipermail/gnupg-devel/2015-February/029524.html

I'm not sure why this happens but the messages are confusing and indicate
failure even though everything seems to be working fine.