Your message dated Tue, 5 May 2009 18:48:08 +0200 (CEST)
with message-id <[email protected]>
and subject line gnupg: Please handle "deprecated option honor-http-proxy"
has caused the Debian Bug report #162742,
regarding gnupg: Please handle "deprecated option honor-http-proxy"
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.)


-- 
162742: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=162742
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnupg
Version: 1.2.0-1
Severity: wishlist

---------------
jdth...@thanatos:~$ gpg --edit-key 0xdeadbeef
gpg: /home/jdthood/.gnupg/options:82: deprecated option "honor-http-proxy"
gpg: please use "keyserver-options honor-http-proxy" instead
gpg (GnuPG) 1.2.0; Copyright (C) 2002 Free Software Foundation, Inc.
This program comes with ABSOLUTELY NO WARRANTY.
---------------

As I have never edited the .gnupg file myself, I would 
wish that the maintainer scripts would upgrade config
files as required, or at least inform me of the manual
changes I need to make.

-- System Information:
Debian Release: 3.0
Architecture: i386
Kernel: Linux thanatos 2.4.19-ac4 #1 Wed Sep 25 08:46:39 EDT 2002 i686
Locale: LANG=C, LC_CTYPE=

Versions of packages gnupg depends on:
ii  devfsd                        1.3.25-10  Daemon for the device filesystem
ii  libc6                         2.2.5-14.2 GNU C Library: Shared libraries an
ii  libldap2                      2.0.23-6   OpenLDAP libraries.
ii  makedev                       2.3.1-58   Creates device files in /dev.
ii  zlib1g                        1:1.1.4-1  compression library - runtime



--- End Message ---
--- Begin Message ---
I'm closing this report:

I don't think, we should touch user configuration files. It's also not possible 
to
determine, if the user has changed the file or not and if the content is there 
for
intent or or. Further the software itself informs about the fix.

Please feel free to comment my decision and/or reopen your report if necessary.

Regards, Daniel



--- End Message ---

Reply via email to