Skip to content

Changes the source of llvm-3.7 temporarily #34017

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

bltavares
Copy link
Contributor

There is an announcement on the LLVM list that the APT source has been
disabled temporarily
http://lists.llvm.org/pipermail/llvm-dev/2016-May/100303.html

This mean that every Travis CI build on Pull Requests will fail until
the repo is back online.

As a short term solution, this commit changes the source repository to
point to Ubuntu Wily 15.10, which has the llvm-3.7-tools available.

There is a risk of adding many other updated packages that is not
compatible to Trusty, and this change could be reverted when the LLVM
apt repo is back online.

There are a few warnings caused by unrelated packages not supporting the
arch, like compiz and some php libs.

There is an announcement on the LLVM list that the APT source has been
disabled temporarily
http://lists.llvm.org/pipermail/llvm-dev/2016-May/100303.html

This mean that every Travis CI build on Pull Requests will fail until
the repo is back online.

As a short term solution, this commit changes the source repository to
point to Ubuntu Wily 15.10, which has the `llvm-3.7-tools` available.

There is a risk of adding many other updated packages that is not
compatible to Trusty, and this change could be reverted when the LLVM
apt repo is back online.

There are a few warnings caused by unrelated packages not supporting the
arch, like `compiz` and some php libs.
@rust-highfive
Copy link
Contributor

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @nikomatsakis (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

Please see the contribution instructions for more information.

@sanxiyn
Copy link
Member

sanxiyn commented Jun 1, 2016

Huh, we sent pull requests to fix Travis within minutes, mine is #34016. My fix is to update everything to 16.04 using Travis's Docker support, instead of mixing 14.04 and 15.10.

@bltavares
Copy link
Contributor Author

Such a coincidence! I was chatting on IRC wondering if there was another person already taking a look on this.

I like the Docker approach better, specially if there is no concerns regarding upgrading the distro.

On June 1, 2016 12:38:51 PM GMT-03:00, Seo Sanghyeon [email protected] wrote:

Huh, we sent pull requests to fix Travis within minutes, mine is
#34016. My fix is to update everything to 16.04 using Travis's Docker
support, instead of mixing 14.04 and 15.10.


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#34017 (comment)

Sent from my Android device with K-9 Mail. Please excuse my brevity.

@bltavares
Copy link
Contributor Author

Mixing packages didn't seem to work. I'm closing this PR.

@bltavares bltavares closed this Jun 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants