[pkg-gnupg-maint] Bug#796931: gnupg-agent: no longer writes $GNUPGHOME/gpg-agent-info-$(hostname) file

Thorsten Glaser tg at mirbsd.de
Tue Aug 25 21:29:05 UTC 2015


Package: gnupg-agent
Version: 2.1.7-2
Severity: important

Hi,

since one of the recent upgrades, gpg-agent no longer writes its
environment file. This is a rather bad regression for my setup,
which uses the env file for sharing a gpg-agent across all (both
SSH and local console or X11) sessions of one user (i.e. that
particular sharing now becomes impossible).

-- System Information:
Debian Release: stretch/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable')
Architecture: x32 (x86_64)
Foreign Architectures: i386, amd64

Kernel: Linux 4.1.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages gnupg-agent depends on:
ii  libassuan0               2.2.1-1
ii  libc6                    2.19-19
ii  libgcrypt20              1.6.3-2
ii  libgpg-error0            1.19-2
ii  libnpth0                 1.2-1
ii  libreadline6             6.3-8+b3
ii  pinentry-qt4 [pinentry]  0.9.5-4

Versions of packages gnupg-agent recommends:
ii  gnupg   1.4.19-5
ii  gnupg2  2.1.7-2
ii  gpgsm   2.1.7-2

gnupg-agent suggests no packages.

-- no debconf information



More information about the pkg-gnupg-maint mailing list