Note that there are some explanatory texts on larger screens.

plurals
  1. POBundle install and update cannot find and install jQuery-rails 2.0.0
    primarykey
    data
    text
    <p>I'm trying to learn Rails from <a href="http://ruby.railstutorial.org/chapters/beginning" rel="nofollow">this website</a>. I'm on Windows so I used the recommended <a href="http://railsinstaller.org" rel="nofollow">Rails-Installer</a>. I need to have <code>jquery-rails</code> gem version 2.0.0 for the tutorial so in my gem file I have those:</p> <pre><code>source 'https://rubygems.org' gem 'rails', '3.2.3' # Bundle edge Rails instead: # gem 'rails', :git =&gt; 'git://github.com/rails/rails.git' group :development do gem 'sqlite3', '1.3.5' end # Gems used only for assets and not required # in production environments by default. group :assets do gem 'sass-rails', '~&gt; 3.2.4' gem 'coffee-rails', '~&gt; 3.2.2' # See https://github.com/sstephenson/execjs#readme for more supported runtimes # gem 'therubyracer', :platform =&gt; :ruby gem 'uglifier', '&gt;= 1.2.3' end gem 'jquery-rails', '2.0.0' # To use ActiveModel has_secure_password # gem 'bcrypt-ruby', '~&gt; 3.0.0' # To use Jbuilder templates for JSON # gem 'jbuilder' # Use unicorn as the app server # gem 'unicorn' # Deploy with Capistrano # gem 'capistrano' # To use debugger # gem 'ruby-debug19', :require =&gt; 'ruby-debug' </code></pre> <p>As it can be seen, I have <code>gem 'jquery-rails', '2.0.0'</code> line in <code>Gemfile</code>. However, when I run <code>bundle update</code> or <code>bundle install</code> I get this error:</p> <pre><code>bbundle install could not find gem ' jquery-rails (= 2.0.0) x96-mingw32' in any of the gem sources listed in your gemfile. </code></pre>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload