kgpg: fix

[k4leg]

As we know in Void Linux, there are two packages: gnupg & gnupg2. So, although the first time you launch kgpg, it gives you the opportunity to indicate where it is (gpg), but does not apply your actions, although it also indicates by default the correct path to gpg2.
Why not just add gnupg to the dependency, as it refers to /usr/bin/gpg? Because for some reason he does not want to work with him, he wants gnupg2.

[Hoshpak]

I don't quite understand what the issue here is. I just launched kgpg and specifically selected gpg which is version 1.4.23 on my system. kgpg detected the version correctly, launched and worked fine.

[k4leg]

Hmm, strange... I don’t have a choice of algorithms when trying to create keys, and if I try to create them, it will either give an error or create the illusion that it is being created, but actually does nothing.
In addition, if I’m not mistaken, as you said, it sets gpgme as a transistor dependence, and gpgme, in turn, depends on gnupg2, so, as for me, it’s better not to add this dependence (gnupg), but fix it in compilation time. As I said, for example, for some reason, he does not apply the actions that I told him during the first run (use /usr/bin/gpg2, and not /usr/bin/gpg) (maybe this is due to that by default it shows the correct path to gpg2 and believes that it has already set the place gpg -> gpg2).

[Hoshpak]

I can reproduce the missing algorithms while generating the key. This is a bug that should be reported upstream. Usually if a package can work with several other packages, we let the user decide and don't create a hard dependency.

[k4leg]

@Hoshpak Thank you, I didn’t even think about it. I reported a bug: https://bugs.kde.org/show_bug.cgi?id=412511