Sprockets locked by Sass and stale compass-rails breaking Susy?

[reconstructions]

The problem I am having is similar to this closed issue, however the solution fixed some Susy problems while creating others.

The entire stack of Sass, Compass, Blueprint and Susy seems to be becoming really unreliable. Compass was one of the last gems to be Rails 4 ready. Like others I have had to [lock my Sprockets[(https://github.com/sstephenson/sprockets/issues/540) just to keep Sass working, which is bound to cause increasing problems for all the downstream frameworks, now that they are all working with stale dependencies.

I am getting a Undefined mixin 'susy-grid-background'. when I use @include susy-grid-background;. Before changing all my gems as described above susy-grid-background worked fine and I got an undefined mixin error when using @include span(). So a whole day of work swapping gems around traded one problem for another.

This set gave me the Undefined mixin error with suzy-grid-background:

gem 'susy', '2.1.2'
gem 'sprockets', '2.11.0'
gem 'sass-rails', '4.0.0'
gem 'breakpoint', '2.4.2'
gem 'compass-rails', '~> 1.1.7'
gem 'compass', '~> 1.0.0.alpha.19'

This set game me the Undefined mixin error with span:

#gem 'susy', '~> 1.0.5'
#gem 'sprockets', '2.11.0'
#gem 'sass-rails', '4.0.2'
#gem 'breakpoint', '2.0.7'
#gem 'compass-rails', '~> 1.1.7'

I understand that this is a problem caused by sass-rails and compass-rails not making the changes needed to keep up with Rails 4. I was very reluctant to take chances by using Compass with Rails 4, since it seemed insufficiently maintained, but if this whole branch can't get caught up, all the "downstream" gems will go stale as well.

[reconstructions]

Looks like Sass-Rails 4.0.3 finally fixes this, and apparently so will Compass 2.0, which is days away. Until then, Susy won't work, but perhaps all these gems are close to working in Rails 4.