> This isn't a bug, and it isn't a problem. Ruby-core decided that gems from
> 1.9.1 would be binary-compatible with 1.9.2 and 1.9.3, so all three of them
> install gems into a folder named 1.9.1. The folder name isn't determined by
> Bundler, it's determined by Ruby, and that's the correct one.

> On Mar 30, 2012, at 11:56 AM, Jodi Showers wrote:

> Greetings,

> When I deploy through capistrano, bundler is building gems in the wrong
> folder:

> /var/www/apps/homestars/shared/bundle/ruby/1.9.1/

> but I'm deploying 1.9.3 (1.9.1 isn't even installed - was a long time ago,
> but removed). Only 1.9.2 and 1.9.3 are installed through rvm, and the
> system is using 1.8.7.

> I'm encountering a crash, and it traces back to the logger.rb gem in the
> 1.9.1 shared bundle dir. My gut is saying this gem is miscompiled - and the
> 1.9.1 dir name just feels wrong.

> .rvmrc references only 1.9.3-p125

> capistrano notes:
> set :rvm_type, :user
> set :rvm_ruby_string, "1.9.3-p125"

> The capistrano deploy log shows only this ruby

> cap shell only references 1.9.3, with no references to other folders for
> other rubies

> I know this could be a capistrano or rvm issue, but hard to know where to
> start.

> I'd appreciate any thoughts - not sure where to start debugging.

> Jodi

> --
> You received this message because you are subscribed to the Google Groups
> "ruby-bundler" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/ruby-bundler/-/7oZUfRBA2FUJ.
> To post to this group, send email to ruby-bundler@googlegroups.com.
> To unsubscribe from this group, send email to
> ruby-bundler+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/ruby-bundler?hl=en.