llvm-toolchain-precise and the rest of LLVM apt are offline #279
Comments
|
Announcement here http://lists.llvm.org/pipermail/llvm-dev/2016-May/100303.html Related: #156 |
fnichol
added a commit
to habitat-sh/habitat
that referenced
this issue
Jun 1, 2016
This change is to work around the LLVM apt site going offline (source: http://lists.llvm.org/pipermail/llvm-dev/2016-May/100303.html) which caused the Travis builds to all fail (source travis-ci/apt-source-safelist#279). We'll use the gcc/g++ alternative toolchain from the [docs](https://docs.travis-ci.com/user/languages/javascript-with-nodejs#Node.js-v4-(or-io.js-v3)-compiler-requirements). Signed-off-by: Fletcher Nichol <fnichol@nichol.ca>
thesentinels
pushed a commit
to habitat-sh/habitat
that referenced
this issue
Jun 1, 2016
This change is to work around the LLVM apt site going offline (source: http://lists.llvm.org/pipermail/llvm-dev/2016-May/100303.html) which caused the Travis builds to all fail (source travis-ci/apt-source-safelist#279). We'll use the gcc/g++ alternative toolchain from the [docs](https://docs.travis-ci.com/user/languages/javascript-with-nodejs#Node.js-v4-(or-io.js-v3)-compiler-requirements). Signed-off-by: Fletcher Nichol <fnichol@nichol.ca> Pull request: #599 Approved by: reset
jtimberman
pushed a commit
to habitat-sh/habitat
that referenced
this issue
Jun 12, 2016
This change is to work around the LLVM apt site going offline (source: http://lists.llvm.org/pipermail/llvm-dev/2016-May/100303.html) which caused the Travis builds to all fail (source travis-ci/apt-source-safelist#279). We'll use the gcc/g++ alternative toolchain from the [docs](https://docs.travis-ci.com/user/languages/javascript-with-nodejs#Node.js-v4-(or-io.js-v3)-compiler-requirements). Signed-off-by: Fletcher Nichol <fnichol@nichol.ca> Pull request: #599 Approved by: reset
|
The LLVM apt repositories have been back online since 2016-06-23: http://lists.llvm.org/pipermail/llvm-dev/2016-June/101500.html |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Just reaching out to see if there is anything you can do to try to reach out to LLVM to help escalate that the entire repo seems to have gone offline and it is affecting your endusers
Here is an example of a project that is blocked and has gone offline within the last 4 hours : https://travis-ci.org/department-of-veterans-affairs/healthcare-application/builds/134238073
http://llvm.org/apt/ and http://llvm.org/apt/llvm-snapshot.gpg.key are examples.
The text was updated successfully, but these errors were encountered: