Upgrading 2.0.20 to 2.2.24 -- WORKING NOW

felix at crowfix.com felix at crowfix.com
Thu Jun 21 17:49:21 CEST 2018

Well I'll be that crazy monkey's crazy uncle!

I started from scratch -- copied the 2.0.20 .gnupg dir to the 2.2.24 machine,
and imported the secret key as the very first operation:

    $ gpg --import <182E8151.exported
    gpg: starting migration from earlier GnuPG versions
    gpg: porting secret keys from '/home/felix/.gnupg/secring.gpg' to gpg-agent
    gpg: key 783876E9182E8151: secret key imported
    gpg: key 44752F7C4D3D351A: secret key imported
    gpg: migration succeeded
    gpg: key 783876E9182E8151: "Felix Finch (Scarecrow Repairman)
    <felix at crowfix.com>" not changed
    gpg: key 783876E9182E8151: secret key imported
    gpg: Total number processed: 1
    gpg:              unchanged: 1
    gpg:       secret keys read: 1
    gpg:  secret keys unchanged: 1
    $ gpg --list-secret-keys
    sec   dsa1024 1999-12-06 [SCA]
    uid           [ultimate] Felix Finch (Scarecrow Repairman) <felix at crowfix.com>
    ssb   elg2048 1999-12-06 [E]

    sec   dsa1024 1999-12-06 [SCA]
    uid           [ unknown] Felix Finch (Remote Access) <felix-control at crowfix.com>
    ssb   elg1024 1999-12-06 [E]

Of course this confused me, why would it matter that I imported and migrated
together?  So I started from scratch again with just --list-secret-keys, no
import, and it worked too.

I can only guess that the original copy of .gnupg was not copied correctly, or
got corrupted somehow.

And thanks to everyone who had the patience to deal with my problem.

            ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
     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

More information about the Gnupg-users mailing list