On Wed, Oct 3, 2018 at 9:28 AM Joseph Herlant <herla...@gmail.com> wrote:
>
> Hi,
>
> On Tue, Oct 2, 2018 at 6:10 PM Seth Arnold <seth.arn...@canonical.com> wrote:
> > Two thoughts: first, give it another try. I was able to refresh my
> > keyring using the debian keyserver a few seconds ago:
> >
> > $ gpg  --refresh-keys --keyserver keyring.debian.org
> > gpg: refreshing 229 keys from hkp://keyring.debian.org
> > ...
> > gpg:         new signatures: 160
> > ...
>
> Ok, so that's really a problem on my end. I've been having this issue
> since I started trying to update it yesterday and still have now.
> Tried 4 or 5 times during the day, same issue.
> Same error while trying to refresh.
>

Have you succeed?
You may debug with,

add following line to ~/.gnupg/dirmngr.conf

log-file /tmp/dirmngr.log
debug-level advanced
debug-all

then run `gpgconf --kill dirmngr`,
send/recv it again, you will see the log in /tmp/tmp/dirmngr.log

This method applies to other gpg components.

-- 
Shengjing Zhu

Reply via email to