Upgrading 2.0.20 to 2.2.24

[felix at crowfix.com]

On Mon, Jun 18, 2018 at 08:36:38AM +0200, Werner Koch wrote:
> On Mon, 18 Jun 2018 07:44, skquinn at rushpost.com said:
> 
> > The format secret keys are stored in changed between 2.0.x and 2.1.x. It
> > is possible that 2.2.x no longer has the code in it to migrate to the
> 
> 2.2 still has the migration code.  However, once a migration is done it
> will not be done again.  Thus adding a new key with an old version of gpg
> at least the secret key won't show up in a newer gpg version.
> 
> > new format, in which case you might need to import secring.gpg manually
> > and set the trust to ultimate manually as well.
> 
> Right.  The official way to do this is to run 
>   gpg --export-secret-key KEYID >FILE
> using the old version of gpg and then to run
>   gpg --import <FILE
> using the new version of gpg.  It is also possible to delete the file
> ~/.gnupg/.gpg-v21-migrated so that a migration will be triggered again.

I tried both these steps, and neither changed anything.  Import said it
imported, but I have a saved copy of .gnupg, and there was no difference after
the import.  The re-migration recreated the .gpg-v21-migrated file, but also
made no difference.  Still can't see the secret keys or decrypt anything.

-- 
            ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
     Felix Finch: scarecrow repairman & wood chipper / felix at crowfix.com
  GPG = E987 4493 C860 246C 3B1E  6477 7838 76E9 182E 8151 ITAR license #4933
I've found a solution to Fermat's Last Theorem but I see I've run out of room o