Bug 16749 - DBG: armor-keys-failed
Summary: DBG: armor-keys-failed
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL: https://bugs.gnupg.org/gnupg/issue1934
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-13 19:40 CEST by Johnny A. Solbu
Modified: 2017-02-01 20:04 CET (History)
2 users (show)

See Also:
Source RPM: gnupg-1.4.19-1.mga5
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Johnny A. Solbu 2015-09-13 19:40:02 CEST 
Description of problem:
In gnupg 1.4.19, some messages appear when refreshing keys from a key server, which clutters the interface.
Upstream says it's «left-over debug message».

LC_ALL=C gpg --refresh-keys solbu.net
gpg: refreshing 1 key from hkp://pgp.surfnet.nl
gpg: requesting key FA687324 from hkp server pgp.surfnet.nl
gpg: DBG: armor-keys-failed (KEY 0x7F09D1F81C3E17584AC9C61A4F5AD64DFA687324 BEGIN
) ->0
gpg: DBG: armor-keys-failed (KEY 0x7F09D1F81C3E17584AC9C61A4F5AD64DFA687324 END
) ->0
gpg: key FA687324: "Johnny Arild Solbu <johnny@solbu.net>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1


Reproducible: 

Steps to Reproduce:
Comment 1 Yann Cantin 2015-09-16 21:18:00 CEST 
Fix ready in the svn for mga5 and cauldron : debug call deleted.

Not sure if it's worth pushing an update.

CC: (none) => yann.cantin

Comment 2 Johnny A. Solbu 2015-11-02 22:32:14 CET 
(In reply to Yann Cantin from comment #1)
> Fix ready in the svn for mga5 and cauldron : debug call deleted.
> 
> Not sure if it's worth pushing an update.

I think it varants an upgrade. The message imply that the refresh failed, when it doesn't, which could lead users to think that GnuPG is broken, and stop trusting it.
Comment 3 Marja Van Waes 2017-02-01 20:04:24 CET 
I suppose this got fixed? We have gnupg-1.4.19-1.2.mga5 now.

Please reopen if needed

Status: NEW => RESOLVED
CC: (none) => marja11
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.