checking for setlocale... yes checking for gpg-error-config... /usr/bin/gpg-error-config checking for GPG Error - version >= 1.24... yes (1.27) checking for x86_64-pc-linux-gnu-libassuan-config... no checking for libassuan-config... /usr/bin/libassuan-config checking for LIBASSUAN - version >= 2.4.2... yes (2.4.3) ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-desktop-plasma-systemd_libressl_20171208-173134 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.2.0 * Available Python interpreters, in order of preference: [1] python3.5 [2] python2.7 (fallback) Available Ruby profiles: [1] ruby22 (with Rubygems) * java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.6.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpv app-crypt/gpgme [ebuild U ] app-crypt/gpgme-1.10.0 [1.10.0_beta81] USE="cxx qt5 -common-lisp -python -static-libs" PYTHON_TARGETS="python2_7 python3_5 -python3_4 -python3_6"
Created attachment 509634 [details] emerge-info.txt
Created attachment 509636 [details] app-crypt:gpgme-1.10.0:20171212-191217.log
Created attachment 509638 [details] emerge-history.txt
Created attachment 509640 [details] environment
Created attachment 509642 [details] etc.portage.tbz2
Created attachment 509644 [details] logs.tbz2
Created attachment 509646 [details] temp.tbz2
seems that somehow this image has gnupg 1.4 installed instead of 2.2.3? Mon Dec 11 22:38:14 2017 <<< app-crypt/gnupg-2.2.3 Mon Dec 11 22:38:19 2017 >>> app-crypt/gnupg-1.4.21 Maybe a good reason to mask 1.4 in the gentoo repo and get ready to remove it altogether.
(In reply to Kristian Fiskerstrand from comment #8) > seems that somehow this image has gnupg 1.4 installed instead of 2.2.3? > > Mon Dec 11 22:38:14 2017 <<< app-crypt/gnupg-2.2.3 > Mon Dec 11 22:38:19 2017 >>> app-crypt/gnupg-1.4.21 > > Maybe a good reason to mask 1.4 in the gentoo repo and get ready to remove > it altogether. Yes, can you please? we do not need it around any more.
Fixed all packages to pull >=gnupg-2