dstarh has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
chouhoulis has quit [Remote host closed the connection]
maletor has quit []
huoxito has quit [Remote host closed the connection]
maletor has joined #bundler
maletor has quit [Client Quit]
_djbkd has quit [Read error: Connection reset by peer]
_djbkd has joined #bundler
_djbkd has quit [Quit: My people need me...]
khebbie has joined #bundler
khebbie_ has joined #bundler
khebbie has quit [Ping timeout: 250 seconds]
khebbie_ has quit [Remote host closed the connection]
khebbie has joined #bundler
khebbie has quit [Remote host closed the connection]
agis- has joined #bundler
khebbie has joined #bundler
agis- has quit [Remote host closed the connection]
khebbie has quit [Remote host closed the connection]
khebbie has joined #bundler
khebbie has quit [Remote host closed the connection]
khebbie has joined #bundler
relix has joined #bundler
wpp has joined #bundler
Pupeno has joined #bundler
khebbie has quit [Remote host closed the connection]
khebbie has joined #bundler
mrgrieves has joined #bundler
<mrgrieves>
how can I work out which gem version is being used when running bundle exec? Unfortunately there are more than one version installed in the system including the bundled versions
<jhass>
mrgrieves: check your Gemfile.lock, the output of bundle check or if the gem follows conventions, bundle exec ruby -rgem -e "p Gem::Version` with both gem and Gem replaced by the gems name
<jhass>
er, ::VERSION usually actually
<mrgrieves>
jhass: cool, let me try ... it's a mess of a system and I'm trying to work out why I'm getting different results in my workstation
<mrgrieves>
btw, it's a rake task I'm trying to run
<mrgrieves>
bundle exec rake spec
<jhass>
probably because your Gemfile.lock is not in your repo or you're not consistently using bundle exec everywhere
<mrgrieves>
jhass: yes, bundle install is not used consistently everywhere
<jhass>
that's not even important if everything demanded in the .lock is already available
<jhass>
bundle exec is the important bit
<jhass>
and using the same .lock everywhere
<mrgrieves>
bundle exec ruby -rgem -e "p serverspec::VERSION" gives me `require': cannot load such file
<mrgrieves>
oh
<mrgrieves>
ok replace gem and Gem as suggested
<mrgrieves>
You have already activated serverspec 2.16.0, but your Gemfile requires serverspec 2.3.1. Prepending `bundle exec` to your command may solve this. (Gem::LoadError)
<jhass>
wat
<jhass>
how, that's... is your bundle exec a silly stub that does nothing or what?
khebbie has quit [Remote host closed the connection]
khebbie has joined #bundler
Pupeno has quit [Remote host closed the connection]
Pupeno has joined #bundler
Pupeno has joined #bundler
wpp has quit [Ping timeout: 260 seconds]
wpp has joined #bundler
jrafanie has joined #bundler
khebbie has quit [Remote host closed the connection]
<mrgrieves>
jhass: I'm not sure but decided to manually remove the gem that wasn't in the lock and and now starting to get some consisten behaviour
jrafanie has quit [Client Quit]
khebbie has joined #bundler
<mrgrieves>
the Version with the command above now comes back as '2.3.1'
<mrgrieves>
so now my workstation and the server are both reporting 2.3.1 with the bundle command above
jrafanie has joined #bundler
<mrgrieves>
however, they are using rvm ... and just installed a newer version of ruby so both workstation and server are matching
<mrgrieves>
but, now some gems are not being loaded
<mrgrieves>
bundle install for some reason only installed a couple of gems in the cache of the new ruby. How can I force bundler to install in the new ruby and not just in vendor/?