On Tue, 19 Apr 2016, Daniel Kahn Gillmor wrote:
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.
It did do that properly. My problem was having created a new key with
gpg long after gpg2 ran that migration.
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.
:happydance:
--
-Matt
"Reality is that which, when you stop believing in it, doesn't go away".
-- Philip K. Dick
GPG fingerprint: 0061 15DF D282 D4A9 57CE 77C5 16AF 1460 4A3C C4E9
