Question

Bundler version 1.0.22

Deploying to RedHat Linux 6

Ruby 1.9.3p0

Rails 3.2.1

---

I read the Bundler docs and took these steps…

• Got everything set on dev workstation so all the gems are installed and the app works and tests pass.

• Checked Gemfile and Gemfile.lock into source control. Made sure not to check .bundle into source control.

I ran $ cap deploy. Now my code is on the production server.

Following the instructions in the docs, I log in, cd to my app root, and run…

$ bundle install --development

This is the result…

$ bundle install --deployment
Fetching source index for https://rubygems.org/
Could not find capistrano-2.11.1 in any of the sources

Does anyone have any idea why this error is occurring?

Any idea how I can persuade Bundler to install my required gems?

I tried to find a clue from what Bundler considers to be the gem environment…

$ bundle exec gem environment
Could not find rake-0.9.2.2 in any of the sources

I looked at the Bundler troubleshooting page and followed the instructions there to delete a bunch of stuff…

# remove user-specific gems and git repos
rm -rf ~/.bundle/ ~/.gem/

# remove system-wide git repos and git checkouts
rm -rf $GEM_HOME/bundler/ $GEM_HOME/cache/bundler/

# remove project-specific settings and git repos
rm -rf .bundle/

# remove project-specific cached .gem files
rm -rf vendor/cache/

# remove the saved resolve of the Gemfile
#
# For now, did not delete this. If I understand the Bundler docs correctly,
# this file is sort of the whole point of Bundler. If I delete it, my deployed
# dependencies won't be the same as in development.
# rm -rf Gemfile.lock

# try to install one more time
bundle install

Bundler still says…

$ bundle install --deployment
Fetching source index for https://rubygems.org/
Could not find capistrano-2.11.1 in any of the sources

OK, fine. I’ll remove Gemfile.lock…

$ bundle install --deployment
The --deployment flag requires a Gemfile.lock. Please make sure you have checked 
    your Gemfile.lock into version control before deploying.

I would be grateful for any help with this.

Answer 1

That version of Capistrano was yanked and is no longer available from rubygems.org. You can see that on the versions page https://rubygems.org/gems/capistrano/versions