On Tuesday, July 19, 2011 5:48:02 PM UTC-7, Matt Aimonetti wrote: > > are you sure that after you created the gemset, you did $ rvm gemset use > <name> ?
Of course I wasn't! I though I was, but between all the different terminals and all, it looks like i was still using the old gemset. So, this time around when I changed to my project directory it asked me to verify the .rvmrc (which is really basic, it just contains calls rvm 1.9.2@project-name). Here it is: $ gem list --local *** LOCAL GEMS *** bundler (1.0.15) rake (0.9.2) $ gem update --system $ gem list --local *** LOCAL GEMS *** bundler (1.0.15) rake (0.9.2) rubygems-update (1.8.5) $ rvm info ruby-1.9.2-p290@locum: (locum is my project name, so it looks like we are were we want). $ bundle install > Are you using any C extensions? > Yes, some gems do have native extensions: Installing json (1.5.3) with native extensions Installing bcrypt-ruby (2.1.4) with native extensions Installing eventmachine (0.12.10) with native extensions Installing hpricot (0.8.4) with native extensions Installing linecache19 (0.5.12) with native extensions Installing nokogiri (1.5.0) with native extensions Installing ruby-debug-base19 (0.11.25) with native extensions Installing sqlite3 (1.3.3) with native extensions Installing thin (1.2.11) with native extensions So far, my new gemset looks fine and my rake and thin don't seem to be complaining. I'll report back tomorrow. Thanks for the help! -- Ylan -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby
