Unable to activate susy-2.1.1, because sass-3.2.17

Question

I have installed the latest versions of compass, sass and susy. But still I am getting this error:

Unable to activate susy-2.1.1, because sass-3.2.17 conflicts with sass (~> 3.3.0)

Anyone knows how this Ruby thing works?

This is the list of my installed gems:

*** LOCAL GEMS ***

CFPropertyList (2.2.0)
chunky_png (1.3.0)
compass (0.12.4)
compass-core (1.0.0.alpha.19)
compass-import-once (1.0.4)
compass-rails (1.1.3)
fssm (0.2.10)
libxml-ruby (2.6.0)
multi_json (1.9.2)
nokogiri (1.5.6)
rb-fsevent (0.9.4)
rubygems-update (2.2.2)
sass (3.3.4, 3.3.3, 3.2.17)
sqlite3 (1.3.7)
susy (2.1.1)

Answer 1

https://teamtreehouse.com/forum/cant-make-susy-211-working

User: Iago Wandalsen Prates

gem uninstall compass

gem uninstall sass

gem uninstall susy

gem install susy

gem install compass --pre

Answer 2

gem install compass --pre

if you ended up uninstalling the sass 3.3.0 gem you should reinstall that first.

Answer 3

The best way without a doubt is to install Susy via the Compass Susy Plugin. This will avoid conflicts with other Compass projects that require the current version.

Commands:

gem install compass
gem install compass-susy-plugin

Answer 4

If you use Bundler, it will ensure that the gems in your Gemfile are the ones used by your project. So your Gemfile should specify "susy", "~>2.1.1" and "sass", "~>3.3.2", plus any other that you require, such as "breakpoint", "~>2.4.1". It then won't matter what versions are installed inside your Ruby gems folder. When you then do a 'bundle install', Bundler ensures that your project will only use the correct dependencies. This is, of course, a CLI instruction through the terminal. Alternatively, simply do a 'sudo gem uninstall sass -v 3.2.17', if you don't want to use Bundler.

Answer 5

I'm using Ubuntu server 14.04 and I had the same problem and this is what I have done

• Remove all my gems with gem uninstall gemname
• Install bundler with sudo apt-get install bundler
• Create a Gemfile as @Remy said before. Here is a Getting Started With Bundler Guide
• And finally bundle install

After that, bundler create a Gemfile.lock where are specified all the needed gems and its versions, so you can use it safely.