Will gpg 1.x remain supported for the foreseeable future?

[Dan Kegel]

On Wed, Jan 17, 2018 at 8:58 PM, Dan Kegel <dank at kegel.com> wrote:
> Here's the bit where it explodes,
>
> + sudo GNUPGHOME=/tmp/obs_localbuild_gpghome_dank.tmp
> APT_CONFIG=/home/dank/src/obs/foo.tmp/etc/apt.conf apt-get -q -q
> update
> inside VerifyGetSigners
> Preparing to exec:  /usr/bin/apt-key --quiet --readonly --keyring
> /tmp/obs_localbuild_gpghome_dank.tmp/keyrings/localhost.gpg verify
> --status-fd 3 /tmp/apt.sig.UbNAaM /tmp/apt.data.5w6fyj
> Read: [GNUPG:] ERRSIG 77D1F0D4EC3422C4 1 8 01 1516232802 9
> Got ERRSIG
> Read: [GNUPG:] NO_PUBKEY 77D1F0D4EC3422C4
> Got NO_PUBKEY

One little clue: apt evidently runs apt-key as user _apt, and
/tmp/obs_localbuild_gpghome_dank.tmp/ is owned by me,
with permissions 700.  So apt-key can't read it.  Whee!

And if I try creating it with permissions 755, gpg complains
about unsafe permissions.

I'm still stuck in a twisty maze of little passages, all different.
I probably should boil down my test to a simple linear
script so I can ask for help properly...
- Dan