parcimonie does not refresh custom reprepro's keyring on apt.lizard

After having updated my GnuPG key, I was not able to upload a package in our custom reprepro on apt.lizard. After having investigated a bit, my key was not up-to-date there and had expired.

Looking at parcimonie’s log, it seems it does not refresh the keyring but fail:

Sep 10 07:01:43 apt dbus-launch[538]: {"state":"FetchEnd","details":{"keyid":"XXX","gpg_error":"gpg: WARNING: Tor is not properly configured\ngpg: keyserver receive failed: Permission denied\n at /usr/share/perl5/App/Parcimonie/Daemon.pm line 350.\n","success":0,"signal":"FetchEnd"}}
Sep 10 07:01:43 apt dbus-launch[538]: {"details":{"duration":144751.229622572},"state":"Sleeping"}
Sep 10 07:01:43 apt dbus-launch[538]: gpgconf: warning: can not open list file /srv/reprepro/.gnupg/dirmngr_ldapservers.conf: No such file or directory
Sep 10 07:01:43 apt dbus-launch[538]: dirmngr:Network:/usr/bin/dirmngr:1:1:
Sep 10 07:01:43 apt dbus-launch[538]: Using 75600 seconds as average sleep time, and 877.672832659127 seconds as fallback sleep time.
Sep 10 07:01:43 apt dbus-launch[538]: tryRecvKey: trying to fetch XXXX
Sep 10 07:01:43 apt dbus-launch[538]: {"details":{"keyid":"05657A225A048861565961DB43AB710FAE9FE593","signal":"FetchBegin"},"state":"FetchBegin"}
Sep 10 07:01:43 apt dbus-launch[538]: gpgconf: warning: can not open list file /srv/reprepro/.gnupg/dirmngr_ldapservers.conf: No such file or directory
Sep 10 07:01:43 apt dbus-launch[538]: dirmngr:Network:/usr/bin/dirmngr:1:1:
Sep 10 07:01:43 apt dbus-launch[538]: gpg: WARNING: Tor is not properly configured
Sep 10 07:01:43 apt dbus-launch[538]: gpg: keyserver receive failed: Permission denied
Sep 10 07:01:43 apt dbus-launch[538]:  at /usr/share/perl5/App/Parcimonie/Daemon.pm line 350.

I suspect the transition to GnuPG v2 broke the setup.

Related issues

• Blocks #13242

Original created by @bertagaz on 15939 (Redmine)