HOW to upgrade: 2.0.22 --> 2.3.3 ???

[Mike Schleif]

Finally, we are moving from CentOS Linux release 7.9.2009 (Core) _to_
AlmaLinux release 9.4 (Seafoam Ocelot).

I copied .gnupg/ to the new host. Problems unsued ...

[ROOT at russell ~/tmP ] # date; /bin/gpg -K ;date
Thu Oct  3 11:13:52 CDT 2024
gpg: DBG: Oops: keyid_from_fingerprint: no pubkey; fpr:
5d5ddc60954d5b06fa7b592ec45b70d9
gpg: DBG: Oops: keyid_from_fingerprint: no pubkey; fpr:
850d581e35383b8c11b50e471bb1b9be
gpg: key 0000000000000000 occurs more than once in the trustdb
gpg: DBG: Oops: keyid_from_fingerprint: no pubkey; fpr:
95b748bd217e51c036d8d0ce4387c502
gpg: key 0000000000000000 occurs more than once in the trustdb
/root/.gnupg/pubring.gpg
------------------------
sec   dsa1024 2002-04-01 [SCA]
      8C71B38C3A071ABCD831D4655257EBE831A070A8
uid           [ultimate] publickey at provell.com
ssb   elg1024 2002-04-01 [E]

sec   rsa4096 2016-03-18 [SC]
      3EA174A350A97D4356A35BC6455FC35E80167A71
uid           [ultimate] Sempris <publickey at Sempris.com>
ssb   rsa4096 2016-03-18 [E]

Thu Oct  3 11:13:52 CDT 2024


[ROOT at russell ~/tmP ] # date; /bin/gpg -K --debug=ipc ;date
Thu Oct  3 11:14:09 CDT 2024
gpg: reading options from '/root/.gnupg/gpg.conf'
gpg: reading options from '[cmdline]'
gpg: enabled debug flags: ipc
gpg: DBG: Oops: keyid_from_fingerprint: no pubkey; fpr:
5d5ddc60954d5b06fa7b592ec45b70d9
gpg: DBG: Oops: keyid_from_fingerprint: no pubkey; fpr:
850d581e35383b8c11b50e471bb1b9be
gpg: key 0000000000000000 occurs more than once in the trustdb
gpg: DBG: Oops: keyid_from_fingerprint: no pubkey; fpr:
95b748bd217e51c036d8d0ce4387c502
gpg: key 0000000000000000 occurs more than once in the trustdb
gpg: DBG: chan_6 <- OK Pleased to meet you, process 88789
gpg: DBG: connection to the gpg-agent established
gpg: DBG: chan_6 -> RESET
gpg: DBG: chan_6 <- OK
gpg: DBG: chan_6 -> OPTION ttyname=/dev/pts/4
gpg: DBG: chan_6 <- OK
gpg: DBG: chan_6 -> OPTION ttytype=xterm
gpg: DBG: chan_6 <- OK
gpg: DBG: chan_6 -> OPTION lc-ctype=C
gpg: DBG: chan_6 <- OK
gpg: DBG: chan_6 -> OPTION lc-messages=C
gpg: DBG: chan_6 <- OK
gpg: DBG: chan_6 -> GETINFO version
gpg: DBG: chan_6 <- D 2.3.3
gpg: DBG: chan_6 <- OK
gpg: DBG: chan_6 -> OPTION allow-pinentry-notify
gpg: DBG: chan_6 <- OK
gpg: DBG: chan_6 -> OPTION agent-awareness=2.1.0
gpg: DBG: chan_6 <- OK
gpg: DBG: chan_6 -> HAVEKEY --list=1000
gpg: DBG: chan_6 <- [ 44 20 d5 a1 e8 57 87 66 fc 6d cc 90 8b 25 32 35
...(74 byte(s) skipped) ]
gpg: DBG: chan_6 <- OK
gpg: DBG: chan_6 -> KEYINFO D5A1E8578766FC6DCC908B25D600BAD639D641A6
gpg: DBG: chan_6 <- S KEYINFO D5A1E8578766FC6DCC908B25D600BAD639D641A6 D -
- - P - - -
gpg: DBG: chan_6 <- OK
gpg: DBG: chan_6 -> KEYINFO 50C781CC9FD53404EC17CF98BFC22BE65A1547E7
gpg: DBG: chan_6 <- S KEYINFO 50C781CC9FD53404EC17CF98BFC22BE65A1547E7 D -
- - P - - -
gpg: DBG: chan_6 <- OK
/root/.gnupg/pubring.gpg
------------------------
sec   dsa1024 2002-04-01 [SCA]
      8C71B38C3A071ABCD831D4655257EBE831A070A8
uid           [ultimate] publickey at provell.com
ssb   elg1024 2002-04-01 [E]

gpg: DBG: chan_6 -> KEYINFO 6924009722E1790A3D3CB382FD26707F0A3136EE
gpg: DBG: chan_6 <- S KEYINFO 6924009722E1790A3D3CB382FD26707F0A3136EE D -
- - P - - -
gpg: DBG: chan_6 <- OK
gpg: DBG: chan_6 -> KEYINFO 13CF8D0A979ADBF4D7D34E66841FCFA5CC7F5EB8
gpg: DBG: chan_6 <- S KEYINFO 13CF8D0A979ADBF4D7D34E66841FCFA5CC7F5EB8 D -
- - P - - -
gpg: DBG: chan_6 <- OK
sec   rsa4096 2016-03-18 [SC]
      3EA174A350A97D4356A35BC6455FC35E80167A71
uid           [ultimate] Sempris <publickey at Sempris.com>
ssb   rsa4096 2016-03-18 [E]

gpg: secmem usage: 0/65536 bytes in 0 blocks
Thu Oct  3 11:14:09 CDT 2024


Initial attempt to encrypt resulted in error:
gpg: starting migration from earlier GnuPG versions

All subsequent attempts failed with this:
DBG: Oops: keyid_from_fingerprint: no pubkey; fpr:
5d5ddc60954d5b06fa7b592ec45b70d9

HOW to eliminate these?
gpg: DBG: Oops: keyid_from_fingerprint: no pubkey; fpr:
850d581e35383b8c11b50e471bb1b9be
gpg: key 0000000000000000 occurs more than once in the trustdb


[ROOT at russell ~/tmP ] # date; /bin/gpg --list-secret-keys ;date
Thu Oct  3 11:19:03 CDT 2024
gpg: DBG: Oops: keyid_from_fingerprint: no pubkey; fpr:
5d5ddc60954d5b06fa7b592ec45b70d9
gpg: DBG: Oops: keyid_from_fingerprint: no pubkey; fpr:
850d581e35383b8c11b50e471bb1b9be
gpg: key 0000000000000000 occurs more than once in the trustdb
gpg: DBG: Oops: keyid_from_fingerprint: no pubkey; fpr:
95b748bd217e51c036d8d0ce4387c502
gpg: key 0000000000000000 occurs more than once in the trustdb
/root/.gnupg/pubring.gpg
------------------------
sec   dsa1024 2002-04-01 [SCA]
      8C71B38C3A071ABCD831D4655257EBE831A070A8
uid           [ultimate] publickey at provell.com
ssb   elg1024 2002-04-01 [E]

sec   rsa4096 2016-03-18 [SC]
      3EA174A350A97D4356A35BC6455FC35E80167A71
uid           [ultimate] Sempris <publickey at Sempris.com>
ssb   rsa4096 2016-03-18 [E]

Thu Oct  3 11:19:03 CDT 2024


Please, advise. Thank you.

~ Mike
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20241003/97efe095/attachment-0001.html>