Bundler refuses to resolve cached gem

[cgriego]

Each time I run bundle install, Bundler insists on updating the i18n gem each time from 0.6.0beta1 to 0.6.0beta1, like 0.6.0beta1 doesn't satisfy the gem requirement. Which means, with the --deployment flag, Bundler refuses to deploy the app (or build it in our CI environment) because it can't find the gem from its vendor cache. Below is the relevant versions in play.

Rubygems 1.3.7 (Engine Yard AppCloud is frozen at 1.3.6 by Engine Yard)
Bundler 1.0.13
Rails ee898e5
i18n 0.6.0beta1
Ruby 1.8.7 (2009-06-12 patchlevel 174) [universal-darwin10.0](using REE in production)

[indirect]

Hmm, weird. Gemfile and other info bits from ISSUES please?

On May 8, 2011, at 8:07 AM, cgriego reply@reply.github.com wrote:

Each time I run bundle install, Bundler insists on updating the i18n gem each time from 0.6.0beta1 to 0.6.0beta1, like 0.6.0beta1 doesn't satisfy the gem requirement. Which means, with the --deployment flag, Bundler refuses to deploy the app (or build it in our CI environment) because it can't find the gem from its vendor cache. Below is the relevant versions in play.

Rubygems 1.3.7 (Engine Yard AppCloud is frozen at 1.3.6 by Engine Yard)
Bundler 1.0.13
Rails ee898e5
i18n 0.6.0beta1
Ruby 1.8.7 (2009-06-12 patchlevel 174) [universal-darwin10.0](using REE in production)

Reply to this email directly or view it on GitHub:
#1158

[cgriego]

I recreated in a reduction. No RVM, same versions as above.

$ bundle init
Writing new Gemfile to /Users/cgriego/tmp/Gemfile
$ echo "gem 'i18n', '~> 0.6.0beta1'" >> Gemfile
$ bundle package
Fetching source index for http://rubygems.org/
Installing i18n (0.6.0beta1) 
Using bundler (1.0.13) 
Your bundle is complete! Use `bundle show [gemname]` to see where a bundled gem is installed.
Updating .gem files in vendor/cache
  * i18n-0.6.0beta1.gem
Removing outdated .gem files from vendor/cache
  * i18n-0.6.0beta1.gem
$ bundle install --deployment
Some gems seem to be missing from your vendor/cache directory.
Could not find i18n-0.6.0beta1 in any of the sources

Gist of a Gemfile and Gemfile.lock: https://gist.github.com/961610

[hone]

I ran your gist and am not running into any issues. What version of rubygems are you running? I uncovered a bug in older versions of rubygems.

[cgriego]

Gist/reduction were done with Rubygems 1.3.7 like above.

[hone]

Oops, sorry didn't see that. This is fixed in rubygems 1.4+ and only affects --pre gems.

[cgriego]

@hone Can you expand on the bug? I've been using prerelease gems with Bundler and Rubygems ~> 1.3.6 successfully so far. Is it something Bundler can workaround or does i18n need to change its version string?

[indirect]

This issue is listed on the bundler/rubygems compatibility page as a known issue: http://gembundler.com/compatibility

The issue will go away as soon as the i18n gem isn't a prerelease anymore. If you'd like to hunt down the problem with rubygems and try to work around it, I'm happy to accept a pull request that doesn't break later versions of Rubygems. Thanks!