gpg-agent is older than us

Ajax aajaxx at
Sun Aug 23 16:41:24 CEST 2020

Thank you Phil,
/usr/bin/gpg-agent is started by systemd and I think it should be left
as it is for the Debian package manager to use with /usr/bin/gpg.  Why
cannot ~/bin/gpg use ~/bin/gpg-agent?  Is it true that gpg in $HOME or
/usr/local should work independently from /usr/bin/gpg?

On Sat, Aug 22, 2020 at 12:22 AM Phil Pennock <gnupg-users at> wrote:
> On 2020-08-21 at 19:00 +0000, Ajax via Gnupg-users wrote:
> > On a Debian box, 'gpg -K' gives "server 'gpg-agent' is older than us
> > (2.2.12 < 2.2.21)".   2.2.21 was built using speedo in my home
> > directory populating ~/bin which appears at the head of $PATH.  The
> > commands 'which gpg' and 'which gpg-agent' both point to ~/bin.
> > 2.2.12 would have been installed by the Debian package manager with
> > /usr/bin/gpg-agent.  How can I cause '~/bin/gpg -K' to use
> > '~/bin/gp-agent' and omit "older than us" warning?
> How is gpg-agent being _started_?  Is it systemd?
> If so, go to <> and scroll down to
> "Users of systemd with vendor-installed socket activation of gpg-agent
> will have to weigh their options carefully" neat the bottom; it's one of
> the bullet points for the `optgnupg-gnupg` package.  It talks about how
> to change the gpg-agent which systemd will launch for you.
> Those are the steps I use on an Ubuntu system to swap out
> /usr/bin/gpg-agent in favour of /opt/gnupg/bin/gpg-agent.
> -Phil

More information about the Gnupg-users mailing list