https://bugs.kde.org/show_bug.cgi?id=226630
ipatrol6...@yahoo.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ipatrol6...@yahoo.com
--- Comment #14 from ipatrol6...@yahoo.com ---
(In reply to Ralf Jung from comment #13)
> > gpg2 is not the problem. But the lack of a separate config file by default
> > is.
> I would argue that the bug is in gpgconf (KWatchGnuPG does not touch the
> configfile itself): It should not write options to configfiles which are
> later read by programs not understanding these options. This problem is
> tracked upstream as https://bugs.g10code.com/gnupg/issue1448 .
Except GPG has denied that bug report, and instead says that it is not
recommended to install both gpg1 and gpg2 on the same system during normal
operation.
So now the ball is back in our court. We can either continue complaining about
it, or come up with a workaround. In the mean time, I will consult with the
Debian project about trying to resolve the gpg1 dependencies and declare the
packages in conflict with each other.
--
You are receiving this mail because:
You are watching all bug changes.
