[pkg-gnupg-maint] Bug#834922: marked as done (gnupg: Fails to sign if secret part of a signing subkey is not present, but its public part known (regression from gpg1))

[Debian Bug Tracking System]

Your message dated Sat, 06 May 2017 03:33:31 +0000
with message-id <E1d6qTL-0002R7-NB at fasolo.debian.org>
and subject line Bug#834922: fixed in gnupg2 2.1.18-7
has caused the Debian Bug report #834922,
regarding gnupg: Fails to sign if secret part of a signing subkey is not present, but its public part known (regression from gpg1)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner at bugs.debian.org
immediately.)


-- 
834922: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834922
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Axel Beckert <abe at debian.org>
Subject: gnupg: No more able to sign with my 4096R key since the switch to GnuPG 2.x, but still able to sign with my old 1024D key
Date: Sat, 20 Aug 2016 17:28:09 +0200
Size: 7815
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnupg-maint/attachments/20170506/a71e6ef6/attachment-0002.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Daniel Kahn Gillmor <dkg at fifthhorseman.net>
Subject: Bug#834922: fixed in gnupg2 2.1.18-7
Date: Sat, 06 May 2017 03:33:31 +0000
Size: 6214
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnupg-maint/attachments/20170506/a71e6ef6/attachment-0003.mht>