[pkg-gnupg-maint] Bug#821808: Bug#821808: Acknowledgement (libgpgme11: Fails to locate new key in agent (wrong keygrip?))

[Daniel Kahn Gillmor]

Version: 1.6.0-1

On Tue 2016-04-19 09:39:58 -0400, Matthew Gabeler-Lee wrote:
> I tracked down the problem.  It is because all the instructions on the
> web for creating new keys are about using "gpg", but gpgme is built on
> "gpg2", and the two no longer share the private key ring.
>
> Quick fix for anyone that comes across this via google or such:
>
> gpg --export-secret-keys | gpg2 --import -

Thanks for the followup.  I'm closing this report since there's a clear
workaround.  However, gpg2 (from the 2.1 branch) should have migrated
your secret keyring automatically the first time it ever encountered
them.

See, for example: https://bugs.launchpad.net/bugs/1565963

fwiw, i'm hoping that gpg and gpg2 will be the same thing (from the
2.1.x sources) in debian in the not-too-distant future.  There are
packages uploaded to experimental yesterday that make that transition,
and i welcome people trying them out once they pass the build daemons.

    --dkg