Your message dated Fri, 17 May 2013 09:09:03 +0200
with message-id 
<[email protected]>
and subject line Re: [Pkg-gnupg-maint] Bug#708534: /usr/bin/gpg: cannot specify 
--keyserver after --recv-key
has caused the Debian Bug report #708534,
regarding /usr/bin/gpg: cannot specify --keyserver after --recv-key
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.)


-- 
708534: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708534
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnupg
Version: 1.4.12-7
Severity: wishlist
File: /usr/bin/gpg

Hello,

the downloading of keys is somewhat needlessly challenging as gpg does
not allow changing the order of options:

 apt-key adv --recv-key 697B014A --keyserver keyserver.ubuntu.com
 Executing: gpg --ignore-time-conflict --no-options --no-default-keyring
 --secret-keyring /tmp/tmp.FdxQWOiQYh --trustdb-name
 /etc/apt//trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring
 /etc/apt/trusted.gpg --keyring
 /etc/apt/trusted.gpg.d//debian-archive-squeeze-automatic.gpg --keyring
 /etc/apt/trusted.gpg.d//debian-archive-squeeze-stable.gpg --keyring
 /etc/apt/trusted.gpg.d//debian-archive-wheezy-automatic.gpg --keyring
 /etc/apt/trusted.gpg.d//debian-archive-wheezy-stable.gpg --keyring
 /etc/apt/trusted.gpg.d//pkg-mozilla-archive-keyring.gpg --recv-key
 697B014A --keyserver keyserver.ubuntu.com
 gpg: "--keyserver" not a key ID: skipping
 gpg: "keyserver.ubuntu.com" not a key ID: skipping
 gpg: no keyserver known (use option --keyserver)
 gpg: keyserver receive failed: bad URI


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (910, 'testing'), (900, 'stable'), (610, 'oldstable'), (410, 
'unstable'), (200, 'experimental'), (150, 'precise-updates'), (150, 
'precise-security'), (150, 'precise')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.8-trunk-amd64 (SMP w/4 CPU cores)
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 /bin/bash

Versions of packages gnupg depends on:
ii  dpkg          1.16.10
ii  gpgv          1.4.12-7
ii  install-info  4.13a.dfsg.1-10
ii  libbz2-1.0    1.0.6-4
ii  libc6         2.17-2
ii  libreadline6  6.2+dfsg-0.1
ii  libusb-0.1-4  2:0.1.12-23+nmu1
ii  zlib1g        1:1.2.7.dfsg-13

Versions of packages gnupg recommends:
pn  gnupg-curl     <none>
ii  libldap-2.4-2  2.4.31-1+nmu2

Versions of packages gnupg suggests:
pn  gnupg-doc     <none>
ii  imagemagick   8:6.7.7.10-5
ii  libpcsclite1  1.8.8-2

-- no debconf information

--- End Message ---
--- Begin Message ---
On Thu, May 16, 2013 22:57, Daniel Leidert wrote:
> Am Donnerstag, den 16.05.2013, 15:37 +0200 schrieb Michal Suchanek:
>
>> the downloading of keys is somewhat needlessly challenging as gpg does
>> not allow changing the order of options:
>
> gpg behaves exactly as upstream described it in the manpage. Options
> come before commands and any parsing stops after a non-option. This is
> IMO not unusual. I'm in favor of closing this report and I'd suggest you
> discuss this on the gnupg mailing lists, if you want to have this design
> decision changed.

Werner has already confirmed that this won't be changed. Closing.


Thijs

--- End Message ---

Reply via email to