Your message dated Mon, 05 Dec 2016 20:00:23 -0500
with message-id <[email protected]>
and subject line Re: [pkg-gnupg-maint] Bug#845720: gnupg: missing dependency on
dirmngr
has caused the Debian Bug report #845720,
regarding gnupg: missing dependency on dirmngr
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
845720: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845720
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnupg
Version: 2.1.15-9
Severity: normal
Dear Maintainer,
on a fresh system setup with debootstrap I got the following output:
gpg --list-keys 79BE3E4300411886 || \
gpg --keyserver keys.gnupg.net --recv-key 79BE3E4300411886
gpg: directory '/home/user/.gnupg' created
gpg: can't open '/usr/share/gnupg/dirmngr-conf.skel': No such file or directory
gpg: new configuration file '/home/user/.gnupg/gpg.conf' created
gpg: keybox '/home/user/.gnupg/pubring.kbx' created
gpg: /home/user/.gnupg/trustdb.gpg: trustdb created
gpg: error reading key: No public key
gpg: failed to start the dirmngr '/usr/bin/dirmngr': No such file or directory
gpg: connecting dirmngr at '/run/user/1000/gnupg/S.dirmngr' failed: No such
file or directory
gpg: keyserver receive failed: No dirmngr
Please, add the missing dependency on package dirmngr.
Best regards
Heinrich Schuchardt
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: arm64 (aarch64)
Kernel: Linux 4.9.0-rc6-next-20161124-00001-gbf7e142 (SMP w/4 CPU cores;
PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages gnupg depends on:
ii gnupg-agent 2.1.15-9
ii libassuan0 2.4.3-2
ii libbz2-1.0 1.0.6-8
ii libc6 2.24-5
ii libgcrypt20 1.7.3-2
ii libgpg-error0 1.25-1
ii libksba8 1.3.5-2
ii libreadline7 7.0-1
ii libsqlite3-0 3.15.1-1
ii zlib1g 1:1.2.8.dfsg-2+b3
Versions of packages gnupg recommends:
ii dirmngr 2.1.15-9
pn gnupg-l10n <none>
Versions of packages gnupg suggests:
pn parcimonie <none>
pn xloadimage <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Control: tags 845720 + wontfix
Hi Heinrich--
Thanks for your report! I think we disagree about the utility of
dirmngr compared to GnuPG. I'm marking this report wontfix and closing
it for reasons described below. If you feel that i've missed something,
you're welcome to reopen the report and help me see what i've missed.
On Sat 2016-11-26 01:29:53 -0500, Heinrich Schuchardt wrote:
> on a fresh system setup with debootstrap I got the following output:
>
> gpg --list-keys 79BE3E4300411886 || \
> gpg --keyserver keys.gnupg.net --recv-key 79BE3E4300411886
> gpg: directory '/home/user/.gnupg' created
> gpg: can't open '/usr/share/gnupg/dirmngr-conf.skel': No such file or
> directory
> gpg: new configuration file '/home/user/.gnupg/gpg.conf' created
> gpg: keybox '/home/user/.gnupg/pubring.kbx' created
> gpg: /home/user/.gnupg/trustdb.gpg: trustdb created
> gpg: error reading key: No public key
> gpg: failed to start the dirmngr '/usr/bin/dirmngr': No such file or directory
> gpg: connecting dirmngr at '/run/user/1000/gnupg/S.dirmngr' failed: No such
> file or directory
> gpg: keyserver receive failed: No dirmngr
>
> Please, add the missing dependency on package dirmngr.
gnupg already Recommends: dirmngr. Without dirmngr, the gnupg package
can perform all sorts of useful functionality (encryption, decryption,
signing, verification, local key management, etc). The only thing it
needs dirmngr for is network access.
ยง7.2 of policy says of Recommends:
This declares a strong, but not absolute, dependency.
The Recommends field should list packages that would be found
together with this one in all but unusual installations.
and of Depends:
This declares an absolute dependency. A package will not be
configured unless all of the packages listed in its Depends field
have been correctly configured (unless there is a circular
dependency as described above).
The Depends field should be used if the depended-on package is
required for the depending package to provide a significant amount
of functionality.
I'm closing this bug report because dirmngr fits much better in
Recommends than in Depends.
--dkg
signature.asc
Description: PGP signature
--- End Message ---
