Skip to content
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

fix travis #17

Merged
merged 1 commit into from
Jul 15, 2018
Merged

fix travis #17

merged 1 commit into from
Jul 15, 2018

Conversation

maelvls
Copy link
Member

@maelvls maelvls commented Jul 13, 2018

No description provided.

Changes:
- separate the two ruby contexts:
  1) ruby 2.3 (for brew) is used by default (rvm use system)
  2) ruby 'default' (for aws-s3 and gem install) is used using
     'rvm default do ...'
- install gmp, openssl, [email protected] and libyaml so that
  the ruby default (rvm default do...) works again
- instead of 'brew update', reinstall brew from scratch as it takes
  much less time and avoid stupid errors with linking and python@2
- update macos images
- do not reinstall xquartz each time, only if it is outdated (it takes
  ~2 minutes to reinstall xquartz otherwise)

Using 'rvm default' (and not rvm system) fixes the error:

    # sudo gem install aws-sdk-s3

    ERROR:  Could not find a valid gem 'aws-sdk-s3' (>= 0), here is why:
    Unable to download data from https://rubygems.org/ - SSL_connect returned=1
    errno=0 state=SSLv2/v3 read server hello A: tlsv1 alert protocol version
    (https://rubygems.org/latest_specs.4.8.gz)
    The command "sudo gem install aws-sdk-s3" failed and exited with 2.
@maelvls maelvls merged commit 7e9820d into master Jul 15, 2018
@maelvls maelvls deleted the fix-travis branch July 15, 2018 07:17
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.

1 participant