perhaps I'm too ignorant to use this, but I feel like I'm sooo close. I ran into numerous permissions issues with system gems, so I switched to homebrew and rbenv. I ran the following to create a subtheme:
compass create nistaurora -r aurora --using aurora/susy
all went well until the following line:
nistaurora/sass/style.scss (Line 2 of _aurora.scss: File to import not found or unreadable: respond-to.
Not sure where to look to sort that out.

Installed Gems:
*** LOCAL GEMS ***

bigdecimal (1.2.0)
blend-mode (0.0.1)
breakpoint (2.0.5)
bundler (1.3.5)
chunky_png (1.2.8)
color-schemer (0.2.3)
compass (0.12.2)
compass-aurora (1.1.1)
compass-normalize (1.4.3)
fssm (0.2.10)
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)
sass (3.2.8)
sassy-buttons (0.1.4)
sassy-strings (0.3.1)
singularitygs (1.0.8)
test-unit (2.0.0.0)
toolkit (1.0.0)

Any help would be greatly appreciated. This looks like a great theme.

Thanks,
John

Comments

michaelmol’s picture

michaelmol CreditAttribution: michaelmol commented

Having the same issue as above. Any advice how to fix this?

I have followed the steps for using bundler on the project page and it looks like it is fixed now.

Snugug’s picture

Snugug CreditAttribution: Snugug commented
Status: Active » Closed (fixed)

If you need to use a legacy version of the gems for creating current new projects, follow the Using Bundler instructions, but put the Gemfile in your themes directory and call bundle exec compass create… instead of just compass create.

johnnykrisma’s picture

johnnykrisma CreditAttribution: johnnykrisma commented

that worked, thanks a bunch!

sdmaxey’s picture

sdmaxey CreditAttribution: sdmaxey commented
Version: 7.x-2.7 » 7.x-3.1

I have the latest regular release of the Aurora theme and have installed the latest gem (twice). I have created a new subtheme twice. Both times I get the following error message:

Syntax error: File to import not found or unreadable: toolkit.
Load paths:
[...]
on line 13 on /Users/smaxey/Sites/drupal/htdocs/sites/all/themes/sitetheme/sass/partials/global/_base.scss
from line 19 of /Users/smaxey/Sites/drupal/htdocs/sites/all/themes/sitetheme/sass/style.scss

I have double-checked that I am using Aurora 3.1. I have installed the compass-aurora gem twice. I have created the subtheme twice, and I have come up with this same error.

Snugug’s picture

Snugug CreditAttribution: Snugug commented

Did you remember to run bundle install and bundle exec compass watch like the documentation says?

sdmaxey’s picture

sdmaxey CreditAttribution: sdmaxey commented

I created a new subtheme using the information from the online documentation instead of the PDF bundled with the theme.

When I run bundle install everything is okay:
bundle install
Fetching gem metadata from https://rubygems.org/..........
Fetching gem metadata from https://rubygems.org/..
Resolving dependencies...
Enter your password to install the bundled RubyGems to your system:
[...}
Using toolkit (1.0.0)
Using compass-aurora (3.0.6)
Your bundle is complete!

When I run bundle show toolkit after bundle install, all is well:
bundle show toolkit
/Library/Ruby/Gems/1.8/gems/toolkit-1.0.0

But when I use bundle exec compass watch toolkit can't be found:
bundle exec compass watch
/Users/smaxey/.compass/extensions/breakpoint/lib/breakpoint.rb:6: warning: already initialized constant VERSION
/Users/smaxey/.compass/extensions/breakpoint/lib/breakpoint.rb:7: warning: already initialized constant DATE
/Users/smaxey/.compass/extensions/singularitygs/lib/singularitygs.rb:7: warning: already initialized constant VERSION
/Users/smaxey/.compass/extensions/singularitygs/lib/singularitygs.rb:8: warning: already initialized constant DATE
>>> Change detected at 05:29:40 to: print.scss
error sass/print.scss (Line 15 of sass/partials/global/_base.scss: File to import not found or unreadable: toolkit.
Load paths:
/Users/smaxey/Sites/ninestone/htdocs-spark/sites/all/themes/sitetheme/sass
/Library/Ruby/Gems/1.8/gems/compass-0.12.2/frameworks/blueprint/stylesheets
[...]
Compass::SpriteImporter)
overwrite stylesheets/print.css

What am I missing?

Snugug’s picture

Snugug CreditAttribution: Snugug commented

run gem list. I want to see what gems you have installed

sdmaxey’s picture

sdmaxey CreditAttribution: sdmaxey commented

gem list

*** LOCAL GEMS ***

addressable (2.3.5)
breakpoint (2.0.6)
bundler (1.3.5)
chunky_png (1.2.8)
color-schemer (0.2.5)
compass (0.12.2)
compass-aurora (3.0.8, 3.0.6)
compass-blend-modes (0.0.2)
compass-normalize (1.4.3)
css_parser (1.3.5)
fssm (0.2.10)
sass (3.2.10)
sassy-buttons (0.2, 0.1.4)
sassy-strings (1.0.0)
singularitygs (1.1.2, 1.0.8)
toolkit (1.3.7, 1.0.0)

Snugug’s picture

Snugug CreditAttribution: Snugug commented

What is in your Gemfile, and where are you running bundle exec compass compile from?

sdmaxey’s picture

sdmaxey CreditAttribution: sdmaxey commented

Gemfile contents:
==========
# 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'
gem 'css_parser', '~>1.3.4'

# Now that you're using Bundler, you need to run `bundle exec compass watch` instead of simply `compass watch`.
==========

Running bundle exec compass compile from
/Users/smaxey/Sites/ninestone/htdocs-spark/sites/all/themes/sitetheme
(the same directory where the gemfile resides)

Just for kicks, ls results on that same directory:
Gemfile config.rb sitetheme.info template.php
Gemfile.lock sass stylesheets templates

sdmaxey’s picture

sdmaxey CreditAttribution: sdmaxey commented

Note: I updated to the latest version of the Compass-Aurora gem (the one that came out after my comments here and that generates a gemfile using less-than-next-major-release verson numbers in the gemfile, and this resolved the problem). Whatever changes you made beyond switching from the -> approach to the < approach to gem dependency version numbers, it has worked to resolve my "gem not found" problem on "bundle exec compass watch"