Dear Maintainer,
gpgconf is supposed to be used by GUIs for configuring GPG, it does the reading
and writing of options as well as the bookkeeping of which options exist at
all. The GPG configuration GUI of KMail is an example of such a GUI. However,
there is a problem: gpgconf advertises options that, when used, break the old
v1 gpg. An example is the log-file option announced by "gpgconf --list-options
gpg": The option is not supported by the old gpg, but still the GUIs offer to
set it. After doing so, every operation of gpg fails since it complains about
an invalid option in the gpg.conf file. IMHO this is unacceptable and a bug in
this package (and not the GUIs), since gpgconf was used exactly the way it was
intended.
I had the following ideas how this could potentially be solved, but I don't
know the implications anything of this could cause:
* Patch the old gpg to ignore the options which are potentially added by the
gnupg2 gpgconf
* Patch gpgconf to always use a gpg.conf-2 configuration file when writing
(creating such a file manually in ~/.gnupg fixes the problem as gpgconf will
then leave gpg.conf alone - but of course, requiring the user to do this
manually is not an option)
* Let the gnupg2 package break/conflict with the gnupg one - which however
would first require the entire Debian key management to be ported to gnupg2
Kind regards,
Ralf