ended up installing ruby via homebrew. Install homebrew first: http://brew.sh then execute brew install ruby after that it worked flawlessly. It has something to do with the native ruby installation.
I just had a similar situation and there is something else missing from @corroded answer. Since @Matt Lynn is downgrading, he needs to uninstall the existing version of compass. $ sudo gem uninstall compass $ sudo gem install compass –version versionnumber Otherwise you will end up with two different versions of compass.
Using the Vagrant plugin vagrant-omnibus worked great for me: vagrant plugin install vagrant-omnibus You can then simply configure your chef version in the Vagrantfile before doing the provisioning: config.omnibus.chef_version = :latest You can also specify a specific version: config.omnibus.chef_version = ‘11.6.0’
The mkmf.log file can be found under the gem’s installation directory. rvm If you are using RVM, then look for a directory similar to ~/.rvm/gems/ruby-1.9.3-p194/gems/some-cool-gem-name/ext/mkmf.log You can list all the mkmf.log files available with this command: find ~/.rvm -name mkmf.log rbenv find ~/.rbenv -name mkmf.log
Here is the way I fix the “invalid date format in specification” error: 1.) Go to the specifications folder located at: /usr/local/lib/ruby/gems/1.8/specifications/ 2.) Find the spec that is causing the problem. 3.) Change s.date = %q{2011-05-21 00:00:00.000000000Z} to s.date = %q{2011-05-21} That’s a WIN for me! Good Luck
You don’t need to build the gem locally. In your gemfile you can specify a github source with a ref, branch or tag. gem ‘rails’, git: ‘git://github.com/rails/rails.git’, ref: ‘4aded’ gem ‘rails’, git: ‘git://github.com/rails/rails.git’, branch: ‘2-3-stable’ gem ‘rails’, git: ‘git://github.com/rails/rails.git’, tag: ‘v2.3.5’ Then you run bundle install or the short form is just bundle. Read more … Read more
I had almost precisely the same error, and was able to completely fix it simply by running: gem install bundler It’s possible your bundler installation is corrupt or missing – that’s what happened in my case. Note that if the above fails you can try: sudo gem install bundler …but generally you can do it … Read more
You first need to uninstall the ruby installed by Ubuntu with something like sudo apt-get remove ruby. Then reinstall ruby using rbenv and ruby-build according to their docs: cd $HOME sudo apt-get update sudo apt-get install git-core curl zlib1g-dev build-essential libssl-dev libreadline-dev libyaml-dev libxml2-dev libxslt1-dev libcurl4-openssl-dev libffi-dev git clone https://github.com/rbenv/rbenv.git ~/.rbenv echo ‘export PATH=”$HOME/.rbenv/bin:$PATH”‘ >> … Read more
That depends on the project in question. Some projects have a *.gemspec file in their root directory. In that case, it would be: gem build GEMNAME.gemspec gem install gemname-version.gem Other projects have a rake task, called gem or build or something like that. In that case you have to invoke rake <taskname>, but that depends … Read more