>>> Verifying ebuild manifests >>> Running pre-merge checks for sys-devel/llvm-9999 * Checking for at least 1200 megabytes disk space at "/var/tmp/portage/sys-devel/llvm-9999/temp" ... [ ok ] >>> Emerging (1 of 1) sys-devel/llvm-9999 * Checking for at least 1200 megabytes disk space at "/var/tmp/portage/sys-devel/llvm-9999/temp" ... [ ok ] >>> Unpacking source... Initialized empty Git repository in /usr/portage/distfiles/git3-src/compiler-rt.git/ * Fetching HEAD from http://llvm.org/git/compiler-rt.git ... fatal: http://llvm.org/git/compiler-rt.git/info/refs not valid: is this a git repository? git fetch --no-tags http://llvm.org/git/compiler-rt.git --unshallow fatal: http://llvm.org/git/compiler-rt.git/info/refs not valid: is this a git repository? * ERROR: sys-devel/llvm-9999::gentoo failed (unpack phase): * Unable to fetch from any of EGIT_REPO_URI * * Call stack: * ebuild.sh, line 93: Called src_unpack * environment, line 4602: Called git-r3_fetch 'http://llvm.org/git/compiler-rt.git' * environment, line 2528: Called die * The specific snippet of code: * [[ -n ${success} ]] || die "Unable to fetch from any of EGIT_REPO_URI"; * * If you need support, post the output of `emerge --info '=sys-devel/llvm-9999::gentoo'`, * the complete build log and the output of `emerge -pqv '=sys-devel/llvm-9999::gentoo'`. * The complete build log is located at '/var/tmp/portage/sys-devel/llvm-9999/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-devel/llvm-9999/temp/environment'. * Working directory: '/var/tmp/portage/sys-devel/llvm-9999/work' * S: '/var/tmp/portage/sys-devel/llvm-9999/work/llvm-9999' >>> Failed to emerge sys-devel/llvm-9999, Log file: Maybe can be used mirror https://github.com/llvm-mirror/llvm as backup repository ? Reproducible: Always
Well, the github thingie says 'unofficial'. I'll need to check whether the commits match...
Ok, backup URL added. I've fixed a few small bugs in git-r3 as well :). I've tested it with llvm.org blocked using iptables. I'm not sure if it will work all the same with the specific kind of error you've seen.
So there are two benefits of this bug:) Thanks.
