Package: gnupg2 Version: 2.1.0-1 Severity: important When upgrading to 2.1, if an existing 2.0 gpg-agent is running, then the migration of secret keys fails silently with an unobvious warning the first time you run gpg2 after the upgrade.
This can be circumvented, by killing all running gpg-agents during the upgrade. GPG 2.1 will automatically start them up when missing, so this should be safe. An alternative is to pop up a warning during the install process, similar to how libc upgrades pop up a warning that prompt you to restart various services. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnupg2 depends on: ii dpkg 1.17.21 ii gnupg-agent 2.1.0-1 ii install-info 5.2.0.dfsg.1-5 ii libassuan0 2.1.2-2 ii libbz2-1.0 1.0.6-7+b1 ii libc6 2.19-13 ii libgcrypt20 1.6.2-4+b1 ii libgpg-error0 1.17-2 ii libksba8 1.3.2-1 ii libreadline6 6.3-8+b1 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages gnupg2 recommends: ii dirmngr 2.1.0-1 Versions of packages gnupg2 suggests: ii gnupg-doc 2003.04.06+dak1-1 pn parcimonie <none> pn xloadimage <none> -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
