[Pkg-gnupg-maint] Candidates of bug reports to be closed with wontfix

[Sune Vuorela]

On Monday 09 June 2008, Daniel Leidert wrote:
> Hi,
>
> To all having some minutes. Please check the following list of bugs if
> you can agree to close them with wontfix. These are candidates, because
> upstream rejected the request with comment:

Thanks for going thru these. Some of them might be nice to keep open + wontfix 
for documentation purposes.

>  #38857: gnupg: no way to copy a key

hmm.. interesting. I don't think I will argue with Werner Koch over this. Let 
us kill it.

>  #61914: gnupg: confusing question in gpg key generation process (I cannot
> agree) 

haha. It is some time ago I generated keys for the first time, but when 
reading this, I can actually recall being unsure about this as well, so might 
be a reasonable request. Not a important one to want to patch it if upstream 
disagrees, though.

> #93656: gnupg; No way to specify multiple keyservers? (#139)

Might be a reasonable request, but tagging wontfix referencing upstream seems 
to be in order.

> #162742: gnupg: Please handle "deprecated option honor-http-proxy"

app is nicely telling user what to do. wontfix is fine.

> #173586: gnupg: Suggestion for a better error message

While error messages alwys can be improved, something might be not worth it. 
So I agree with  WK. 

> #185782: `--batch --output existingfile' outputs nothing and exits 0

wontfix

> #196681: gnupg: gpg says /dev/null at alea isn't a valid email address

wontfix

> #225888: gnupg: slight improvement of docs regarding IDEA

kill it.

> #290980: gnupg: 'gpg -q --verify' should be quiet on success (#919)

hmm... undecided

> #310805: gnupg: fully exportable armored homedir is completely impossible
> now! 

I don't understand exactly what user wants to do. But Werner seems to have 
understood it and what he writes sounds reasonable. let us close it.

> #318587: gnupg: should encrypt to all subkeys

wontfix, but let us keep it open.

> #300743: gnupg: Should not depend on libusb

In principle, I agree with submitter, but not enough so I want to take it up 
again. But might be worth keeping around anyway.

> If there is a "(#XXX)", then there is an entry in the upstream bug
> tracker at https://bugs.g10code.com/gnupg/issueXXX with more
> information.
>
> Please feel free to comment in the related bug report or here in this
> thread.

Done here.

/Sune
-- 
I cannot insert the port, how does it work?

From the control panel inside Word 97 you need to download the virus to ping 
to a coaxial AGP space bar.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://lists.alioth.debian.org/pipermail/pkg-gnupg-maint/attachments/20080609/0656579a/attachment.pgp