QList<QSslCertificate> _approvedCerts; ^ /var/tmp/portage/net-misc/nextcloud-client-2.3.2/work/client_theming-2.3.2/client/src/libsync/account.h:226:23: error: field ‘_sslConfiguration’ has incomplete type ‘QSslConfiguration’ QSslConfiguration _sslConfiguration; ^~~~~~~~~~~~~~~~~ In file included from /usr/include/qt5/QtNetwork/QNetworkRequest:1:0, ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-desktop-plasma_libressl_20170716-132802 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-6.3.0 * llvm-config: 3.9.1 Available Python interpreters, in order of preference: [1] python3.4 [2] python2.7 (fallback) java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.4.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm
Created attachment 485930 [details] emerge-info.txt
Created attachment 485932 [details] emerge-history.txt
Created attachment 485934 [details] environment
Created attachment 485936 [details] etc.portage.tbz2
Created attachment 485938 [details] logs.tbz2
Created attachment 485940 [details] net-misc:nextcloud-client-2.3.2:20170719-133138.log
Created attachment 485942 [details] temp.tbz2
My main box is out for a few days so this is just a theory, but looks like it needs to depend on qtnetwork[ssl] (enabled by default, so that's probably why I did not see it). If that's the case I'll update the dep (and net-misc/owncloud-client too as it most probably has the same problem)
Confirmed, I just tested with qtnework[-ssl] and got the same error. Ebuilds updated!