Package: gnupg2 Version: 2.1.0-1 Severity: normal >From what I can figure out by googling, for gnupg 2.1, dirmngr is mandatory for --refresh-keys. Without it, that operation fails.
And it also doesn't seem to like dirmngr < 2.1.0-1 at all, again failing (with the error "IPC connect call failed"). I hadn't thought about checking for a higher version to dirmngr until dkg told me it recommends this version. Yes, with dirmngr 2.1.0-1, it works. Well, apart from an apparently known and fixed upstream bug that --refresh-keys fails with "Too many objects" (<http://web.archiveorange.com/archive/v/2TGPMrmEQ8Qf4Fpiwett>, <https://bugs.g10code.com/gnupg/issue1755>). Not quite sure if something should be done about it. Set a hard dependency on dirmngr >= 2.1.0-1 instead of a recommendation? Add a conflicts dirmngr < 2.1.0-1? Or is it just a user error on my part? -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.17.2 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash 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 ii libgpg-error0 1.17-2 ii libksba8 1.3.1-1 ii libreadline6 6.3-8+b1 ii zlib1g 1:1.2.8.dfsg-2 Versions of packages gnupg2 recommends: ii dirmngr 2.1.0-1 Versions of packages gnupg2 suggests: pn gnupg-doc <none> pn parcimonie <none> pn xloadimage <none> -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
