2019-06-14 22:25:51 ERROR 404: Not Found. !!! Couldn't download 'libbpf-0.0.3.tar.gz'. Aborting. * Fetch failed for 'dev-util/bcc-0.10.0', Log file: * '/var/log/portage/dev-util:bcc-0.10.0:20190614-202549.log' ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1-desktop-gnome-systemd_libressl_20190608-014115 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.1.0 * Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) [3] jython2.7 (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) * Available Rust versions: [1] rust-1.35.0 * java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.12.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpvO dev-util/bcc [ebuild N ] dev-util/bcc-0.10.0 USE="luajit -test" PYTHON_SINGLE_TARGET="python3_6 -python2_7 -python3_5 -python3_7" PYTHON_TARGETS="python2_7 python3_6 -python3_5 -python3_7"
Created attachment 579800 [details] emerge-info.txt
Created attachment 579802 [details] dev-util:bcc-0.10.0:20190614-202549.log
Created attachment 579804 [details] emerge-history.txt
Created attachment 579806 [details] etc.portage.tbz2
I am guessing this is a transient problem with GitHub, or a problem with the network configuration of the server this is being built on. This is on the Gentoo mirrors now as well. Whatever the issue, there isn't much I can do about it >>> Downloading 'https://104.19.137.75/gentoo/distfiles/libbpf-0.0.3.tar.gz' --2019-06-14 22:25:49-- https://104.19.137.75/gentoo/distfiles/libbpf-0.0.3.tar.gz Connecting to 104.19.137.75:443... connected. ERROR: certificate common name ‘ssl382663.cloudflaressl.com’ doesn't match requested host name ‘104.19.137.75’. To connect to 104.19.137.75 insecurely, use `--no-check-certificate'. >>> Downloading 'https://104.19.139.75/gentoo/distfiles/libbpf-0.0.3.tar.gz' --2019-06-14 22:25:49-- https://104.19.139.75/gentoo/distfiles/libbpf-0.0.3.tar.gz Connecting to 104.19.139.75:443... connected. ERROR: certificate common name ‘ssl382663.cloudflaressl.com’ doesn't match requested host name ‘104.19.139.75’. To connect to 104.19.139.75 insecurely, use `--no-check-certificate'. >>> Downloading 'https://104.19.138.75/gentoo/distfiles/libbpf-0.0.3.tar.gz' --2019-06-14 22:25:49-- https://104.19.138.75/gentoo/distfiles/libbpf-0.0.3.tar.gz Connecting to 104.19.138.75:443... connected. ERROR: certificate common name ‘ssl382663.cloudflaressl.com’ doesn't match requested host name ‘104.19.138.75’. To connect to 104.19.138.75 insecurely, use `--no-check-certificate'. >>> Downloading 'rsync://ftp-stud.hs-esslingen.de/gentoo/distfiles/libbpf-0.0.3.tar.gz' Welcome to the ftp-stud.hs-esslingen.de archives.
This works: tinderbox@mr-fox /var/db/repos/gentoo/dev-util/bcc $ ebuild bcc-0.10.0.ebuild fetch * bcc-0.10.0.tar.gz BLAKE2B SHA512 size ;-) ... [ ok ] * libbpf-0.0.3.tar.gz BLAKE2B SHA512 size ;-) ... [ ok ] Shouldn't an ebuild being disallowed to download additional packages during emerge?
