Closed aetxeberriasqs closed 2 years ago
This appears to be a network problem on your side, which we cannot fix from here. The provided URLs (like https://rubygems.org/gems/json-2.5.1.gem) are resolvable from my network.
Maybe a wild guess, but bundle
has / had some problems with ipv6. Basically ipv6 on ruby gems.org is broken for some people, the work around is to either disable ipv6 completely on your host or try something like a new config option they seem to have as documented in https://github.com/rubygems/rubygems/pull/2662.
The work around is to include :ipv4_fallback_enabled: true
in a file called ~/.gemrc
We have managed to make the bundle install statment run, but for that to happen we have needed to first make the following entries:
sudo apt-get install ruby-full bundle install sudo apt-get install libsqlite3-dev bundle install
maybe this two statments should appear in the documentation as they are not noted there, or maybe there is a problem in the installation or prior configuration that should be adressed or noted in the documentation before reaching this point.
No. For the following reasons:
apt-get
is (mostly) exclusive to Debian based distributions and other people's setups will deviate from that. I use arch, btw.Happy to hear that your install is now working :) Closing this issue
There is a problem when executing the bundle install. When following the steps to instal the bundle, the following error ocurred and the next message pooped up in the console. The first part appear cross out and dont know why.
Your user account isn't allowed to install to the system RubyGems. You can cancel this installation and run:
to install the gems into ./vendor/bundle/, or you can enter your password and install the bundled gems to RubyGems using sudo.
Password: Installing bcrypt 3.1.16 with native extensions Installing eventmachine 1.2.7 with native extensions Using temple 0.8.2 Using tilt 2.0.10 Fetching json 2.5.1 Using jwt 2.2.3 Using multi_json 1.15.0 Using ruby2_keywords 0.0.4 Using net-ldap 0.17.0 Fetching openssl 2.2.0
Retrying download gem from https://rubygems.org/ due to error (2/4): Gem::RemoteFetcher::UnknownHostError no such name (https://rubygems.org/gems/json-2.5.1.gem)
Retrying download gem from https://rubygems.org/ due to error (2/4): Gem::RemoteFetcher::UnknownHostError no such name (https://rubygems.org/gems/openssl-2.2.0.gem)
Retrying download gem from https://rubygems.org/ due to error (3/4): Gem::RemoteFetcher::UnknownHostError no such name (https://rubygems.org/gems/json-2.5.1.gem)
Retrying download gem from https://rubygems.org/ due to error (3/4): Gem::RemoteFetcher::UnknownHostError no such name (https://rubygems.org/gems/openssl-2.2.0.gem)
Retrying download gem from https://rubygems.org/ due to error (4/4): Gem::RemoteFetcher::UnknownHostError no such name (https://rubygems.org/gems/json-2.5.1.gem)
Retrying download gem from https://rubygems.org/ due to error (4/4): Gem::RemoteFetcher::UnknownHostError no such name (https://rubygems.org/gems/openssl-2.2.0.gem)
Using power_assert 2.0.0 Using rack 2.2.3 Using require_all 3.0.0 Using rspec-support 3.10.2 Using scanf 1.0.0 Using sinatra-cors 1.2.0 Fetching sqlite3 1.4.2
Using webrick 1.7.0 Using i18n 1.8.10 Using tzinfo 2.0.4 Using haml 5.2.1 Using mustermann 1.1.1
Retrying download gem from https://rubygems.org/ due to error (2/4): Gem::RemoteFetcher::UnknownHostError no such name (https://rubygems.org/gems/sqlite3-1.4.2.gem)
Retrying download gem from https://rubygems.org/ due to error (3/4): Gem::RemoteFetcher::UnknownHostError no such name (https://rubygems.org/gems/sqlite3-1.4.2.gem)
Retrying download gem from https://rubygems.org/ due to error (4/4): Gem::RemoteFetcher::UnknownHostError no such name (https://rubygems.org/gems/sqlite3-1.4.2.gem)
--- ERROR REPORT TEMPLATE -------------------------------------------------------
Error Report
Questions
Please fill out answers to these questions, it'll help us figure out why things are going wrong.
What did you do?
I ran the command
/bin/bundle install
What did you expect to happen?
I expected Bundler to...
What happened instead?
Instead, what happened was...
Have you tried any solutions posted on similar issues in our issue tracker, stack overflow, or google?
I tried...
Have you read our issues document, https://github.com/rubygems/rubygems/blob/master/bundler/doc/contributing/ISSUES.md?
...
Backtrace
Environment
Bundler Build Metadata
Gemfile
Gemfile
Gemfile.lock
--- TEMPLATE END ----------------------------------------------------------------
Unfortunately, an unexpected error occurred, and Bundler cannot continue.
First, try this link to see if there are any existing issue reports for this error: https://github.com/rubygems/rubygems/search?q=no+such+name+%28https+%2F%2Frubygems.org%2Fgems%2Fjson-2.5.1.gem%29&type=Issues
If there aren't any reports for this error yet, please create copy and paste the report template above into a new issue. Don't forget to anonymize any private data! The new issue form is located at: https://github.com/rubygems/rubygems/issues/new?labels=Bundler&template=bundler-related-issue.md
Thanks in advance