On Tue, 25 Apr 2017 22:31, d...@fifthhorseman.net said:
> Do you recommend terminating all per-user gpg-agent and dirmngr
> instances upon package upgrade? This would be a significant change from
I can't decide this. What I do if something goes wrong after an update
is to look into the
Control: tags 860745 + upstream
Control: forwarded 860745 https://dev.gnupg.org/T3117
On Sun 2017-04-23 18:52:11 +0200, Werner Koch wrote:
> Well, correct installation of a software update is the task of the
> sysadmin or the distribution. This is the same as an update of libc or
> other
On Sun, 23 Apr 2017 11:09, enr...@debian.org said:
> Technically it sounds like the right thing. I had no idea I could get
> hints with --verbose, though, so I wouldn't have seen it.
Isn't it the first thing with Unix tools to add -v when you wonder what
is going on ;-).
> Could gpg tell
On Fri, Apr 21, 2017 at 06:52:20PM +0200, Werner Koch wrote:
> > gpg: WARNING: server 'dirmngr' is older than us (2.1.17 < 2.1.18). Run
> > 'gpgconf --kill dirmngr' to terminate it. A new instance will be restarted
> > as needed.
> We already have some hints messages printed in --verbose
On Wed, 19 Apr 2017 18:53, d...@fifthhorseman.net said:
> I wouldn't want to encourage people to restart the daemons -- i'd rather
> encourage them to terminate them and let the new versions be restarted
Right.
> gpg: WARNING: server 'dirmngr' is older than us (2.1.17 < 2.1.18). Run
>
Hi Enrico--
On Wed 2017-04-19 18:26:48 +0200, Enrico Zini wrote:
> I get some warnings when I run some gpg commands:
>
> gpg: WARNING: server 'dirmngr' is older than us (2.1.17 < 2.1.18)
> gpg: WARNING: server 'gpg-agent' is older than us (2.1.17 < 2.1.18)
>
> I'd like to restart those services,
6 matches
Mail list logo
