Package: gpg-agent Version: 2.2.17-3 Severity: important Tags: upstream I regularily work with chroots into which I bind-mount my home directory but *not* /var/run or /run (which is, incidentally, important to not do) and the recent move of gpg-agent sockets to /run breaks this totally.
Please add an option (e.g. in ~/.gnupg/gpg-agent.conf) for users to re‐ vert it. -- System Information: Debian Release: bullseye/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable'), (100, 'experimental') Architecture: x32 (x86_64) Foreign Architectures: i386, amd64 Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) Shell: /bin/sh linked to /bin/lksh Init: sysvinit (via /sbin/init) Versions of packages gpg-agent depends on: ii gpgconf 2.2.17-3 ii init-system-helpers 1.57 ii libassuan0 2.5.3-7 ii libc6 2.28-10 ii libgcrypt20 1.8.4-5 ii libgpg-error0 1.36-7 ii libnpth0 1.6-1 ii pinentry-qt [pinentry] 1.1.0-3 Versions of packages gpg-agent recommends: ii gnupg 2.2.17-3 Versions of packages gpg-agent suggests: pn dbus-user-session <none> pn libpam-systemd <none> pn pinentry-gnome3 <none> ii scdaemon 2.2.17-3 -- no debconf information
