You could just import the old GPG files with appropriate options. I did this a
while ago as my kbx got damaged when I had a hdd failure.
Am 27. Juli 2018 06:50:59 MESZ schrieb fe...@crowfix.com:
>I ran into a similar problem a few months ago, upgrading from a much
>older gentoo system with
I ran into a similar problem a few months ago, upgrading from a much older
gentoo system with 1.something. I don't know what specific action fixed it,
but after a couple of cycles of restoring the original and trying different
commands, it suuddenly migrated correctly. Memory says the first
On Donnerstag, 26. Juli 2018 17:17:58 CEST Franek Wiertara wrote:
> > On 26 Jul 2018, at 11:50, Paul M Furley wrote:
> > I upgraded from Ubuntu 16.04 LTS to Ubuntu 18.04 LTS and restored my
> > `.gnupg` directory from a backup disk.
> >
> > Now gpg doesn't see any keys... `gpg --list-keys` just
Is it possible the two Ubuntu distributions you mentioned ship different
versions of gnupg? I am asking about it because gnupg v. 2.0 and earlier and
gnupg v. 2.1.x and later have different ways of storing keys. I don’t know the
details because i started using gpg from version 2.1.x but this
Hi folks,
I upgraded from Ubuntu 16.04 LTS to Ubuntu 18.04 LTS and restored my `.gnupg`
directory from a backup disk.
Now gpg doesn't see any keys... `gpg --list-keys` just exists with no output.
I've attached the strace output of `strace gpg --list-keys`, and here's the
output of `tree
