I have set up a test site on MAMP and I've installed Aurora and Magic. I've gone through the bundle install instructions and updated the Gemlock file, followed by the bundle install.

However, I can't get past the creation of the subtheme.

I've been inside the root directory, the sites/all/themes directory and the sites/all/themes/aurora directory, and I've punched into Terminal:
compass create hrslgc -r aurora --using aurora

I get the following error:

/Library/Ruby/Site/2.0.0/rubygems/core_ext/kernel_require.rb:135:in `require': cannot load such file -- sass/script/node (LoadError)
	from /Library/Ruby/Site/2.0.0/rubygems/core_ext/kernel_require.rb:135:in `rescue in require'
	from /Library/Ruby/Site/2.0.0/rubygems/core_ext/kernel_require.rb:144:in `require'
	from /Library/Ruby/Gems/2.0.0/gems/compass-0.12.2/lib/compass/sass_extensions/monkey_patches/browser_support.rb:1:in `<top (required)>'
	from /Library/Ruby/Site/2.0.0/rubygems/core_ext/kernel_require.rb:73:in `require'
	from /Library/Ruby/Site/2.0.0/rubygems/core_ext/kernel_require.rb:73:in `require'
	from /Library/Ruby/Gems/2.0.0/gems/compass-0.12.2/lib/compass/sass_extensions/monkey_patches.rb:2:in `block in <top (required)>'
	from /Library/Ruby/Gems/2.0.0/gems/compass-0.12.2/lib/compass/sass_extensions/monkey_patches.rb:1:in `each'
	from /Library/Ruby/Gems/2.0.0/gems/compass-0.12.2/lib/compass/sass_extensions/monkey_patches.rb:1:in `<top (required)>'
	from /Library/Ruby/Site/2.0.0/rubygems/core_ext/kernel_require.rb:73:in `require'
	from /Library/Ruby/Site/2.0.0/rubygems/core_ext/kernel_require.rb:73:in `require'
	from /Library/Ruby/Gems/2.0.0/gems/compass-0.12.2/lib/compass/sass_extensions.rb:9:in `<top (required)>'
	from /Library/Ruby/Site/2.0.0/rubygems/core_ext/kernel_require.rb:73:in `require'
	from /Library/Ruby/Site/2.0.0/rubygems/core_ext/kernel_require.rb:73:in `require'
	from /Library/Ruby/Gems/2.0.0/gems/compass-0.12.2/lib/compass.rb:5:in `block in <top (required)>'
	from /Library/Ruby/Gems/2.0.0/gems/compass-0.12.2/lib/compass.rb:4:in `each'
	from /Library/Ruby/Gems/2.0.0/gems/compass-0.12.2/lib/compass.rb:4:in `<top (required)>'
	from /Library/Ruby/Site/2.0.0/rubygems/core_ext/kernel_require.rb:73:in `require'
	from /Library/Ruby/Site/2.0.0/rubygems/core_ext/kernel_require.rb:73:in `require'
	from /Library/Ruby/Gems/2.0.0/gems/compass-0.12.2/bin/compass:20:in `block in <top (required)>'
	from /Library/Ruby/Gems/2.0.0/gems/compass-0.12.2/bin/compass:8:in `fallback_load_path'
	from /Library/Ruby/Gems/2.0.0/gems/compass-0.12.2/bin/compass:19:in `<top (required)>'
	from /usr/bin/compass:23:in `load'
	from /usr/bin/compass:23:in `<main>'

I've run a gem query --local and I have:

*** LOCAL GEMS ***

addressable (2.3.5)
blend-mode (0.0.1)
breakpoint (2.0.5)
bundler (1.3.5)
CFPropertyList (2.2.4, 2.2.0)
chunky_png (1.2.9, 1.2.8)
color-schemer (0.2.3)
compass (0.12.2)
compass-aurora (3.0.6)
compass-normalize (1.4.3)
css_parser (1.3.5)
ffi (1.9.3)
fssm (0.2.10)
libxml-ruby (2.7.0, 2.6.0)
listen (1.1.6)
mini_portile (0.5.2)
nokogiri (1.6.0, 1.5.6)
rb-fsevent (0.9.3)
rb-inotify (0.9.2)
rb-kqueue (0.2.0)
rubygems-update (2.1.11, 2.1.10)
sass (3.3.0.rc.2, 3.2.12, 3.2.8)
sassy-buttons (0.1.4)
sassy-strings (0.3.1)
singularitygs (1.0.8)
sqlite3 (1.3.8, 1.3.7)
susy (1.0.9)
toolkit (1.0.0)

I've looked for help here in the issues forum, but I can't see anyone having the same error as me.

I'm following the online documentation, not the PDF.

Any help is greatly appreciated.

Comments

Spanners’s picture

Spanners CreditAttribution: Spanners commented

Anyone? Help. I'm at a dead end here. Tried it on a fresh Drupal install and I get the same thing.

Spanners’s picture

Spanners CreditAttribution: Spanners commented

I think my issue may have something to do with Mavericks. The default ruby is version 2.0.

Has anyone successfully got Sass and Compass working with MAMP on Mavericks?

iamcarrico’s picture

iamcarrico CreditAttribution: iamcarrico commented

Spanners--- I have been running ruby 2.0 on my machine for a while, and have not run into this yet.

Sorry, we have been under the gun for other work. I will try and go through the issue queue better over the holidays.

Spanners’s picture

Spanners CreditAttribution: Spanners commented

Hey ChinggizKhan! Thanks for responding. Are you on Mountain Lion or Mavericks?

Snugug’s picture

Snugug CreditAttribution: Snugug commented

I am on Mavericks. If you upgraded from a previous operating system (instead of a clean install), you will now have two Ruby environments on your computer, 1.8 and 2.0. I assume you are using System ruby. If so, you have two options: either uninstall Ruby 1.8 from your computer and all of your current gems and reinstall the gems you need under 2.0 (which should be easy assuming you're following our advice and using Gemfiles for everything), or you can install a ruby version management system (such as rvm, rbenv, or chruby; only one may be installed on a machine at a time) and reinstalling your gems under a managed ruby environment.

If you are unsure how to uninstall Ruby 1.8 from your computer or are afraid of damaging your system by removing the wrong files, I'd suggest the ruby version management approach, although there is a learning curve with those.

iamcarrico’s picture

iamcarrico CreditAttribution: iamcarrico commented

I am on maverics. I also use rbenv.

Spanners’s picture

Spanners CreditAttribution: Spanners commented

This is all extremely helpful. Thanks very much. I did upgrade from ML to Mavericks. I'll uninstall 1.8, uninstall and reinstall my gems and see how I go. If I butcher my machine, I'll fresh install.

I'll post my results here.

Spanners’s picture

Spanners CreditAttribution: Spanners commented

Still getting owned over here. Here's an update.

And by the way, there was only Ruby 2.0.0-p247 installed. Nothing from the previous Mountain Lion install.

Here's where I'm at. Terminal commands in italics, results in bold. Bigger results and errors in the code block.

Installed RVM (and JewelryBox, but I've been doing everything via Terminal with the RVM website instructions.

ruby -v gave me ruby 2.0.0p247 (2013-06-27 revision 41674) [universal.x86_64-darwin13]

rvm use 2.0.0 --default gave me ruby-2.0.0-p353 is not installed. To install do: 'rvm install ruby-2.0.0-p353

So I tried to set the default to the ruby I know is installed. rvm use 2.0.0-p247 --default

Using /Users/SimonAOM/.rvm/gems/ruby-2.0.0-p247
Warning! Executable 'ruby' missing, something went wrong with this ruby installation!
Warning! Executable 'gem' missing, something went wrong with this ruby installation!
Warning! Executable 'irb' missing, something went wrong with this ruby installation!

So I installed the latest stable ruby. rvm install ruby-2.0.0-p353

That all installed fine, however it did say at the very beginning No binary rubies available for: osx/10.9/x86_64/ruby-2.0.0-p353.

rvm use 2.0.0 gave me Using .../.rvm/gems/ruby-2.0.0-p353

Local gems at this stage are...

bigdecimal (1.2.0)
bundler (1.3.5)
bundler-unload (1.0.2)
executable-hooks (1.2.6)
io-console (0.4.2)
json (1.7.7)
minitest (4.3.2)
psych (2.0.0)
rake (0.9.6)
rdoc (4.0.0)
rubygems-bundler (1.4.2)
rvm (1.11.3.8)
test-unit (2.0.0.0)

Started the install process for compass again - sudo gem install compass

Fetching: sass-3.2.12.gem (100%)
Successfully installed sass-3.2.12
Fetching: chunky_png-1.2.9.gem (100%)
Successfully installed chunky_png-1.2.9
Fetching: fssm-0.2.10.gem (100%)
Successfully installed fssm-0.2.10
Fetching: compass-0.12.2.gem (100%)
Successfully installed compass-0.12.2
Parsing documentation for chunky_png-1.2.9
Installing ri documentation for chunky_png-1.2.9
Parsing documentation for compass-0.12.2
Installing ri documentation for compass-0.12.2
Parsing documentation for fssm-0.2.10
Installing ri documentation for fssm-0.2.10
Parsing documentation for sass-3.2.12
Installing ri documentation for sass-3.2.12
4 gems installed

Aaaaand this is where I'm stuck, and in fact, was stuck before (I was getting this error before trying to install the subtheme when I first created this post).

sudo gem install compass-aurora

ERROR:  While executing gem ... (Gem::ImpossibleDependenciesError)
    compass-0.12.2 requires sass (~> 3.1) but it conflicted:
  Activated sass-3.2.12 instead of (~> 3.3.0.rc.2) via:
    breakpoint-2.4.0, singularitygs-1.1.2, toolkit-1.3.8, compass-aurora-3.0.8

I found Snugug's post on https://github.com/Team-Sass/toolkit/issues/47 and thought I'd try sudo gem install breakpoint

That did it's thing, so I tried sudo gem install compass-aurora again. I ended up adding to the error...

ERROR:  While executing gem ... (Gem::ImpossibleDependenciesError)
    compass-aurora-3.0.8 requires compass (>= 0.12.2) but it conflicted:
  Activated compass-1.0.0.alpha.17 instead of (~> 0.12) via:
    color-schemer-0.2.7, toolkit-1.3.8, compass-aurora-3.0.8
  Activated compass-0.12.2 instead of (~> 1.0.0.alpha.13) via:
    breakpoint-2.4.0, singularitygs-1.1.2, toolkit-1.3.8, compass-aurora-3.0.8

My current gems for this ruby are...

bigdecimal (1.2.0)
breakpoint (2.4.0)
bundler (1.3.5)
bundler-unload (1.0.2)
chunky_png (1.2.9)
compass (1.0.0.alpha.17, 0.12.2)
compass-core (1.0.0.alpha.16)
compass-import-once (1.0.1)
executable-hooks (1.2.6)
ffi (1.9.3)
fssm (0.2.10)
io-console (0.4.2)
json (1.7.7)
listen (1.1.6)
minitest (4.3.2)
multi_json (1.8.2)
psych (2.0.0)
rake (0.9.6)
rb-fsevent (0.9.3)
rb-inotify (0.9.3)
rb-kqueue (0.2.0)
rdoc (4.0.0)
rubygems-bundler (1.4.2)
rvm (1.11.3.8)
sass (3.3.0.rc.2, 3.2.12)
sassy-maps (0.3.1)
test-unit (2.0.0.0)

And this is where I'm at. So pumped to use Aurora but just can't.

Where am I going wrong?

Snugug’s picture

Snugug CreditAttribution: Snugug commented

You've got too many gems all going on at once. What you need to do, while still under RVM control, create a Gemfile for Bundler containing Compass Aurora gem. Bundle install into RVM (you don't want to be using local gems if you're using RVM), then run the compass create command through bundler (bundle exec). THEN you'll get a Gemfile in your new subtheme and bundle install tehre and run that through Bundler as well.

Jeff Burnz’s picture

Jeff Burnz CreditAttribution: Jeff Burnz commented

Lord oh lord I have this issue also, for regardless of using bundler, rvm etc I had to remove sass 3.3.0.rc.2, then this problem went away. This is super huge pita for me since I need to be using/testing with susy alpha 6 for my next project, I posted a cry for help here: https://github.com/ericam/susy/issues/264

Spanners’s picture

Spanners CreditAttribution: Spanners commented

OK, I bit the bullet and did a fresh install of Mavericks 10.9. Set up MAMP PRO and a fresh Drupal 7.24. Follow the online documentation, got to gem install compass-aurora...

ERROR:  While executing gem ... (Gem::DependencyError)
    Unable to resolve dependencies: breakpoint requires compass (~> 1.0.0.alpha.13); sassy-maps requires compass (~> 1.0.0.alpha.13); sass requires listen (~> 1.1.0)

My friend replicated this error with a fresh install of Mavericks.

I'm sorry to say, but for now, Mavericks and Aurora just doesn't play nice. Not by following the online documentation, anyway.

My gems are:

CFPropertyList (2.2.0)
chunky_png (1.2.9)
compass (0.12.2)
fssm (0.2.10)
libxml-ruby (2.6.0)
nokogiri (1.5.6)
sass (3.2.12)
sqlite3 (1.3.7)

Ruby straight out of a Mavericks fresh install is currently:

ruby 2.0.0p247 (2013-06-27 revision 41674) [universal.x86_64-darwin13]

Snugug, I also tried the gemfile/Bundler approach, but I think I was just too much of a noob to get it working.

As a side note, I got the subtheme working on another ML Mac.

Looks like back to Mountain Lion I go.

Spanners’s picture

Spanners CreditAttribution: Spanners commented

Wai-wai-wait!

My friend and I had another go at the bundler method from Snugug at https://drupal.org/comment/8284925#comment-8284925

We got it working!

Here's what we did. And this is without RVM installed - remember that I have a fresh install of Mavericks 10.9.

Installed Bundler, then created the subtheme folder next to the aurora folder (eg. sites/all/themes/test)

In Terminal, cd'd into our new subtheme directory and:
bundle init

I then opened the Gemfile in a text editor and copied in the text from the Using Bundler section of the Aurora Project page (https://drupal.org/project/aurora). My Gemfile looks like this:

# A sample Gemfile
source "https://rubygems.org"

# Pull gems from RubyGems
source 'https://rubygems.org'
# ~> Refers to all versions of the given gem on the current full version number, so it will be able to use any version of Compass Aurora until Compass Aurora 4.x.x. For a specific version of a gem, remove the ~>
gem 'compass-aurora', '~>3.0.0'
gem 'toolkit', '~>1.0.0'
gem 'singularitygs', '~>1.0.7'
gem 'breakpoint', '~>2.0.2'
gem 'sassy-buttons', '~>0.1.4'
gem 'compass-normalize', '~>1.4.3'
# Now that you're using Bundler, you need to run `bundle exec compass watch` instead of simply `compass watch`.

# gem "rails"

Saved the Gemfile, of course.

Whilst still in the subtheme directory:
bundle install

Got an error:

Errno::EACCES: Permission denied - /Library/Ruby/Gems/2.0.0/build_info/sass-3.2.13.info
An error occurred while installing sass (3.2.13), and Bundler cannot continue.
Make sure that `gem install sass -v '3.2.13'` succeeds before bundling.

So I did:
sudo bundle install

And it worked. I then did:
bundle exec compass create test -r aurora --using aurora

This created a subtheme in my subtheme (sites/all/themes/test/test). So I renamed the first subtheme (test1) and dragged the newly created sub-subtheme into the themes folder. I deleted the renamed theme.

In the Drupal Appearance admin, my new subtheme is there to be enabled and set to default.

I cd'd into my new subtheme and:
bundle exec compas watch

And we're polling!

I've documented this so heavily here in this post so I can go home and try to repeat all of this on the iMac there (*EEK!*).

I really hope this helps someone out.

Snugug’s picture

Snugug CreditAttribution: Snugug commented
Status: Active » Fixed

Great, glad that Bundler wound up being the solution in the end (like it so often is when it comes to gem issues).

One thing, you never want to sudo Bundler commands. Instead, do one of the following:

Assuming you have Homebrew installed (you're probably going to need to uninstall all of your current gems for this solution to work BTW, but it's worth it), add the following line to your .bash_profile (or zshconfig) and restart your terminal:

export GEM_HOME=$(brew --prefix)

Otherwise, when running bundle install, add --path vendor to the end to install the gems to the current directory into a folder called vendor. Don't commit that folder into version control.

Marking this as fixed as Bundler solves this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

orcaman’s picture

orcaman CreditAttribution: orcaman commented

had the same issue after upgrading to Mavericks.

Solution: for me it was because I got a the sass-3.3.0.rc.2 version of Sass, while in order for compass to work I had to use version 3.2.12.

so I uninstalled my current version and installed the correct one:
sudo gem uninstall sass
sudo gem install sass -v 3.2.12

this solved the issue for me.

iamcarrico’s picture

iamcarrico CreditAttribution: iamcarrico commented

So, the issues stems from versioning and issues with new versions of Compass/Sass not being perfectly backwards compatible. Especially since we have a lot of gems that we use here.

There is a PR in to fix these issues-- https://github.com/Snugug/Aurora/pull/42 and once some proper testing has been done we will merge it in and push a new update to the gem.

scott.whittaker’s picture

scott.whittaker CreditAttribution: scott.whittaker commented

Thanks orcaman, that saved me a lot of hassle.

iamcarrico’s picture

iamcarrico CreditAttribution: iamcarrico commented

The issue should be resolved across the board with the latest version of the gem 3.0.9.

https://rubygems.org/gems/compass-aurora/versions/3.0.9

djbobbydrake’s picture

djbobbydrake CreditAttribution: djbobbydrake commented

@Spanners, you are a life-saver. Thank you.