On Tue 2016-04-19 20:27:38 -0400, Matthew Gabeler-Lee wrote: > 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.
ah, right, understood. I don't think that the gpg2 migration process has any way to account for this situation. :( All the more reason we should rip off the bandaid and just transition already. >> 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: glad you're happy about it too :) --dkg