After running a gem update, I got errors when running 'compass watch':

>>> Change detected at 23:01:58 to: style.scss
    error sass/style.scss (Line 2 of _aurora.scss: File to import not found or unreadable: respond-to.
Load paths:
[...]

Finally, I was able to trace it down to this commit in the toolkit gem: https://github.com/Team-Sass/toolkit/commit/eba47f2075d94ec3e76833ac9e36.... It seems that Aurora is failing now that toolkit no longer requires respond-to and susy. After adding require 'respond-to' to ~/.gem/ruby/2.0.0/gems/compass-aurora-1.1.1/lib/aurora.rb, compass started complaining File to import not found or unreadable: susy.. Once I also added the line require 'susy' to the same file, all errors were gone.

I'm not sure where this should be fixed, and I'm not even sure if I'm posting this in the correct issue queue. Please let me know if you want me to report this elsewhere.

I am marking this as critical because breaking 'compass watch' is pretty devastating for a sass-and-compass based (sub)theme.

Comments

Snugug’s picture

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

This is by design. Please check individual gem's changes before updating them, as they may break compatibility with what you have been using. You can mitigate this by using Bundler to lock your theme into specific versions of gems to ensure you do not break them with gem updates. Documentation for using Bundler has been added to the main document.

marcvangend’s picture

marcvangend
he/him
Primary language Dutch
Location Amsterdam
CreditAttribution: marcvangend commented

OK, thanks for the explanation and for updating the documentation.

When I start working on a new project, I like to get my gems up-to-date first. Meanwhile I expect the older stuff to remain working, but I'd rather not sift through change logs and commit diffs every time I update some gems. As you say, Bundler seems to get you the best of both worlds. Wouldn't it make sense to add Gemfile (and Gemfile.lock?) to the base theme and, more importantly, to the subtheme templates in compass-aurora?

Snugug’s picture

Snugug CreditAttribution: Snugug commented

A good rule of thumb when looking at projects is if there is a new full version release (0.x-1.x, 2.x-3.x), chances are there are non-backwards-compatible changes that have been made.

While it doesn't make sense to include a Gemfile in Aurora itself, it does make sense to include one in the next version of the Gem so when you build a new Aurora subtheme you get the Gemfile. It's something we're in the process of building right now.

marcvangend’s picture

marcvangend
he/him
Primary language Dutch
Location Amsterdam
CreditAttribution: marcvangend commented

Your rule of thumb sounds usable (even though the upgrade from toolkit-0.2.6 to toolkit-0.3.1 wasn't major by that definition :-)) I'm looking forward to the next version. Thanks again.