gemfile

I've created a gem, and for some reason this one keeps bugging me, and refuses to install properly through bundler. Here's the Gemfile : source 'https://rubygems.org' gem 'rails', '3.2.9' gem "switch_access-rails", "~> 1.1.6" bundle install fails with: Could not find gem 'switch_access-rails (~> 1.1.6) ruby' in the gems available on this machine. This works: gem install switch_access-rails -v 1.1.6 And the gem is here on rubygems: https://rubygems.org/gems/switch_access-rails/versions/1.1.6 I even tried bumping from version 1.1.5 to 1.1.6 just to see if that helped. Installing version 1.1.4 in

What is the purpose of "Gemfile.lock" in Rails? I have been searching around for but could not find a satisfactory answer. You should read all the documentation from the bundler gem: http://gembundler.com/ THE GEMFILE.LOCK When you run bundle install, Bundler will persist the full names and versions of all gems that you used (including dependencies of the gems specified in the Gemfile(5)) into a file called Gemfile.lock. Bundler uses this file in all subsequent calls to bundle install, which guarantees that you always use the same exact code, even as your application moves across machines.

The gemspec semantic versioning operator ~> (aka twiddle-wakka , aka pessimistic operator) allows a gem version to be constrained yet allow some upgrades. I have often seen that it can be read as: "~> 3.1" => "Any version 3.x, but at least 3.1" "~> 3.1.1" => "Any version 3.1.x, but at least 3.1.1" But with one number, this rule breaks down: "~> 3" => "Any version x, but at least 3" *NOT TRUE!* "~> 3" => "Any version 3.x" *True. But why?* If I wanted "Any version 3.x", I could just use "~> 3.0", which is consistent. As it stands, this change of operation at one number is inconsistent and

I'm trying to push to heroku using git push heroku master It gets stuck when trying to access rubygems: -> Heroku receiving push -----> Removing .DS_Store files -----> Ruby/Rails app detected -----> Installing dependencies using Bundler version 1.1.rc.5 Running: bundle install --without development:test --path vendor/bundle --binstubs bin/ Fetching gem metadata from http://rubygems.org/....... /app/slug-compiler/lib/utils.rb:62:in `block (2 levels) in spawn': command='/app/slug-compiler/lib/../buildpacks/ruby/bin/compile /tmp/build_38k3w88w3yxzg /app/tmp/repo.git/.cache' exit_status=0 out=''

I get the following error message when starting the rails server: Your bundle is locked to rake (12.0.0), but that version could not be found in any of the sources listed in your Gemfile. If you haven't changed sources, that means the author of rake (12.0.0) has removed it. You'll need to update your bundle to a different version of rake (12.0.0) that hasn't been removed in order to install. I specified gem 'rake', '12.0.0' in the gemfile but that doesn't fix it. I tried bundle update rake , deleting the Gemfile.lock and generating it with bundle exec bundle install . I also prepended `bundle

If there are two gems, A and B . A1.0.0 depends on B1.0.0 . In my Gemfile: gem 'A', '~> 1.0.0' Then run bundle . It will generate a Gemfile.lock like: A (1.0.0) B (1.0.0) But if I want to force A to use B1.0.1 , what's the best practice? Moreover, if the B1.0.1 is not release but a github tag? You'll need to explicitly specify the B gem in your Gemfile to use a git repository or another version. As long as A 1.0.0 is compatible with B 1.0.1 you'll be fine. If it is only compatible with B 1.0.0 then you'll have to create your own fork of the A gem and upgrade the gemspec to be compatible with B