Geek Answers Handbook

Rails bundler: "Could not find tilt-1.3.5 in any of the sources"

I had never encountered this problem before, so I really donโ€™t know where to start looking for answers ... even though Google seems to be an empty road regarding this topic.

When I try to click my application on the hero, I get this message:

-----> Ruby/Rails app detected -----> Installing dependencies using Bundler version 1.3.0.pre.5 Running: bundle install --without development:test --path vendor/bundle --binstubs vendor/bundle/bin --deployment Fetching gem metadata from https://rubygems.org/......... Fetching gem metadata from https://rubygems.org/.. Could not find tilt-1.3.5 in any of the sources ! ! Failed to install gems via Bundler. ! ! Heroku push rejected, failed to compile Ruby/rails app

I destroyed my gemset and started many times, as well as an oblique tilt in my Gemfile, but I'm out of luck, I still get this message.

As I said, until yesterday I did not receive this error and assumed that it was a small error that will be fixed. It seems that this is not the case, and I scratch my head, trying to figure out what needs to be done to fix this problem.

Any suggestions?

EDIT GEMFILE

 source 'https://rubygems.org/' gem 'rails', '3.2.12' gem 'thin' gem 'bcrypt-ruby', '~> 3.0.0' gem 'bootstrap-sass' gem 'will_paginate' gem 'bootstrap-will_paginate' gem 'jquery-rails' gem 'rails_autolink' group :assets do gem 'sass-rails', '~> 3.2.3' gem 'coffee-rails', '~> 3.2.1' gem 'uglifier', '>= 1.0.3' end group :development, :test do gem 'sqlite3' end group :production do gem 'pg', '0.14.1' end
+6
source share
3 answers

I get the same error. Since iRichLau was tagged in this comment , locking works up to 1.3.4 or 1.3.6.

In the gemfile:

 gem 'tilt', '1.3.4' # or '1.3.6' is now out and also works.

Then the bundle:

 bundle update tilt

Make sure the commit message is commensurate with the absurdity of this fantastic mistake .;)

+1
source

bundle update works, and then git add should be fixed before clicking

+1
source

It happened to me when I had 2 different versions of a bright jewel.

New bright bright pearls require a newer version of the package.

So, at the top of my deploy.rb, I made the version of the bright shortcut box be:

 gem 'brightbox', '2.3.8'
0
source

More articles:


All Articles