When emerging gpgme if gnupg is compiled using selinux the compilation will fail. Reproducible: Always Steps to Reproduce: 1. USE="selinux" emerge -pv gnupg 2. emerge gpgme Actual Results: ..... srcdir=. ./mkdemodirs Creating: Alphagpg: WARNING: unsafe permissions on homedir `.' gpg: exporting secret keys not allowed gpg: WARNING: nothing exported make[3]: *** [Alpha/Secret.gpg] Error 2 make[3]: Leaving directory `/var/tmp/portage/gpgme-1.0.2/work/gpgme-1.0.2/tests/gpg' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/gpgme-1.0.2/work/gpgme-1.0.2/tests' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/gpgme-1.0.2/work/gpgme-1.0.2' make: *** [all] Error 2 !!! ERROR: app-crypt/gpgme-1.0.2 failed. Expected Results: Emerge subcesfuly. If gnupg is emerged with "-selinux" it will work fine. This is because the gnupg emerged with the selinux gpg will refuse to export secret keys with the message "gpg: exporting secret keys not allowed" The problem is in gpgme-1.0.2/tests/gpg/mkdemodirs script that is traying to export some secret keys.
Tudor are you feeling exceptionally generous to prove a working patch?
I will.
Created attachment 69278 [details, diff] patch for ebuild I have searched for a more elegant way to do it but seem this is the most efficient way. The option for disabling tests doesn’t exist in gpgme, and implementing one or modifying the configure.ac script will waste time regenerating configuration scripts. And by the way the option "–-disable-tests" is pointless
I get this in the middle of a Hardened ~x86 installation too. I've patched the ebuild and am building it now. Let's hope this works. :)
Yay! Thanks, Tudor. Your patch works fine for me (gpgme 1.0.3). Daniel, would you please add this in CVS?
thankyou - sorry it took so long
Latest ebuild (1.1.5) is missing this again, preventing gpgme to be build on selinux.
