Cloning into '/var/tmp/portage/app-emulation/lxd-2.19/work/lxd-2.19/src/github.com/rogpeppe/godeps'... fatal: unable to access 'https://github.com/rogpeppe/godeps/': Couldn't resolve host 'github.com' package github.com/rogpeppe/godeps: exit status 128 make: *** [Makefile:49: check] Error 1 * ERROR: app-emulation/lxd-2.19::gentoo failed (test phase): * emake failed ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0_test_20171216-103216 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.2.0 * Available Python interpreters, in order of preference: [1] python3.5 [2] python3.6 (fallback) [3] python2.7 (fallback) 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-emulation/lxd [ebuild N ] app-emulation/lxd-2.19 USE="daemon dnsmasq ipv6 nls {-test}"
Created attachment 510444 [details] emerge-info.txt
Created attachment 510446 [details] app-emulation:lxd-2.19:20171217-054645.log
Created attachment 510448 [details] emerge-history.txt
Created attachment 510452 [details] environment
Created attachment 510454 [details] etc.portage.tbz2
Created attachment 510456 [details] emerge-history.txt emerge-history.txt
As I write in https://bugs.gentoo.org/634726 dependencies for testing aren't pinned down yet so the "test" action requires connectivity to run. This package isn't in super great shape and I'm not experienced enough with ebuilds to make it top notch. Will get there eventually...
IMHO this can be closed as the lowest version is 3.5 as of 13 Dec 2018
I've left this open since the issue exists into 3.x. I'll need to either get USE=test working or remove it. The 3.9 release notes claim some fixes to tests so it may be worth revisiting soon.
*** Bug 634726 has been marked as a duplicate of this bug. ***
Actually this is also fixed on the latest ebuild, the test error is now for a different reason and I may have to attempt fixing it outside a container.