Hello
I've recently upgraded to Debian buster, and then upgraded gpg by
downloading and installing the new version 2.2.17.
Now, I get this warning:
> gpg: WARNING: server 'gpg-agent' is older than us (2.2.12 < 2.2.17)
$ gpg --version
gpg (GnuPG) 2.2.17
libgcrypt 1.8.4
$ which gpg-agent
/usr/loc
Matthias Herrmann [2019-07-11T01:33:43+02] wrote:
> I've recently upgraded to Debian buster, and then upgraded gpg by
> downloading and installing the new version 2.2.17.
> Now, I get this warning:
>
>> gpg: WARNING: server 'gpg-agent' is older than us (2.2.12 < 2.2.17)
> I don't know why the "wr
Hi,
I've run into this issue when my package manager updates gnupg without
killing running gpg-agent daemons.
I think you have a previous (old version) gpg-agent daemon still running.
You can see if that's the case by looking at the output of 'ps x'. I would
recommend killing that daemon by using
On 11/07/2019 15:41, Teemu Likonen wrote:
> I believe it's because there is gpg-agent.socket unit which activates
> gpg-agent.service which has the path /usr/bin/gpg-agent. To override
> that create a unit "drop-in" file:
Thank you, that was it.
I edited /usr/lib/systemd/user/gpg-agent.service di
Matthias Herrmann [2019-07-11T16:16:29+02] wrote:
> I edited /usr/lib/systemd/user/gpg-agent.service directly and changed
> the ExecStart and ExecReload paths.
It is not a good idea to edit that file directly; it's not a
configuration file. In systemd you should make your own changes in
/etc/syst
Hi all,
On 11.07.19 15:41, Teemu Likonen via Gnupg-users wrote:
> Matthias Herrmann [2019-07-11T01:33:43+02] wrote:
>
>> I've recently upgraded to Debian buster, and then upgraded gpg by
>> downloading and installing the new version 2.2.17.
>> Now, I get this warning:
>>
>>> gpg: WARNING: server
On 11/07/2019 16:36, Teemu Likonen wrote:
> Matthias Herrmann [2019-07-11T16:16:29+02] wrote:
>
>> I edited /usr/lib/systemd/user/gpg-agent.service directly and changed
>> the ExecStart and ExecReload paths.
>
> It is not a good idea to edit that file directly; it's not a
> configuration file. In
Michael Kesper [2019-07-11T16:45:06+02] wrote:
> Did anyone open a bug with Debian (best with proposing a fix)?
What bug? We have not seen a bug in this message thread.
--
/// OpenPGP key: 4E1055DC84E9DFF613D78557719D69D324539450
// https://keys.openpgp.org/search?q=tliko...@iki.fi
/ https:/
Hi Teemu,
On 11.07.19 17:11, Teemu Likonen wrote:
> Michael Kesper [2019-07-11T16:45:06+02] wrote:
>
>> Did anyone open a bug with Debian (best with proposing a fix)?
>
> What bug? We have not seen a bug in this message thread.
I'd consider it a bug if updating a package does not trigger reload
Hi
On 11/07/2019 16:45, Michael Kesper wrote:
> Did anyone open a bug with Debian (best with proposing a fix)?
Hello
This is not a bug in debian, they ship with 2.2.12 [1]. I manually
installed 2.2.17 from source.
-Hermi
[1] https://packages.debian.org/buster/gnupg
signature.asc
Description
Michael Kesper [2019-07-11T17:15:19+02] wrote:
> I'd consider it a bug if updating a package does not trigger reloading
> all necessary services.
We have not been discussing about Debian package upgrade. This message
thread is about additional local installation (/usr/local) which is
outside of D
Matthias Herrmann via Gnupg-users [2019-07-11T16:49:29+02] wrote:
> I created the .d directory and only overwrote ExecStart and ExecReload
> as you suggested.
Just remembered that there is also dirmngr.service for which you
probably want to the same thing as for gpg-agent.service.
--
/// OpenP
On 11/07/2019 20:40, Teemu Likonen wrote:
> Just remembered that there is also dirmngr.service for which you
> probably want to the same thing as for gpg-agent.service.
I didn't think of that, thanks for the hint.
-Hermi
signature.asc
Description: OpenPGP digital signature
___
13 matches
Mail list logo
