Update sprockets dependency

[connorwarnock]

A number of gems have moved on to sprokets 2.12.0, so capping the gem at 2.11.0 is causing dependency issues.

phyllisstein seems to have it patched here: https://github.com/phyllisstein/sass-rails/commit/36524cf168e7e31b072b71b8282e75c5652da3d3

[rafaelfranca]

This gem doesn't work with sprockets 2.12.0. I don't believe any gem force the 2.12.0 version, so your application should work with sprockets 2.11.0.

For more information follow #192

[yoyos]

on windows I had this message related to sprockets with sass-rails-4.0.3:

Resolving dependencies...
Bundler could not find compatible versions for gem "sprockets":
  In Gemfile:
    sass-rails (>= 0) x86-mingw32 depends on
      sprockets (~> 2.0.0) x86-mingw32

    rails (= 4.1) x86-mingw32 depends on
      sprockets-rails (~> 2.0) x86-mingw32 depends on
        sprockets (2.12.1)

Bundler could not find compatible versions for gem "sprockets-rails":
  In Gemfile:
    sass-rails (>= 0) x86-mingw32 depends on
      sprockets-rails (~> 2.0.0) x86-mingw32

    rails (= 4.1) x86-mingw32 depends on
      sprockets-rails (2.1.3)

Bundler could not find compatible versions for gem "railties":
  In Gemfile:
    sass-rails (>= 0) x86-mingw32 depends on
      railties (~> 3.1.0) x86-mingw32

    rails (= 4.1) x86-mingw32 depends on
      railties (4.1.0)

with gem 'sass-rails','~> 4.0.2'
it's working great though

[dogweather]

    rails (= 4.1.0) ruby depends on
      sprockets-rails (~> 2.0) ruby depends on
        sprockets (2.12.1)

Seem like a dependency on Sprocket 2.12. (?)

[rafaelfranca]

This is output of bundler, but sprockets-rails doesn't enforce any version as you can see here https://github.com/rails/sprockets-rails/blob/v2.1.3/sprockets-rails.gemspec#L11.

[robin850]

@dogweather @yoyos : You need to rm Gemfile.lock and try to run bundle install or bundle update.

[yoyos]

I don't understand, why does it work if I put:

gem 'sass-rails', '~> 4.0.3'

And don't work if I put:

gem 'sass-rails'

Is Not specifying a version number the same as specifying the last version ?

[rafaelfranca]

No, because you are locked in a version. It would work if you call bundle update sass-rails rails

[dogweather]

I'm sorry, I'm still confused. I can recreate the situation like this:

1. rails new (creating a fresh 4.1.0 rails),
2. Remove the '~> 4.0.3' restriction in the Gemfile,
3. bundle update

Bundler then exits with the messages about inability to find compatible versions. I'm confused about what you're saying this means:

1. This this is a Bundler bug. Or alternatively,
2. This is the desired behavior for Bundler, and instead due to the user's incorrect use of the Gemfile.

??

[matthewd]

It's an unfortunate consequence of how gem version dependencies work. Bundler has three choices:

• install the latest sass-rails, and an older sprockets
• install the latest sprockets, and an older sass-rails
• give up, and rely on the user to disambiguate

It's currently choosing door number 3... and I think that's probably best: it has no way of knowing which of the others is better. In principle, it seems that bundler could offer a more comprehensive description of the situation... though even properly recognising it feels likely to be non-trivial. (@Who828?)

[dosbo]

I'm seeing this issue too...why's it marked closed?

[HotShot3150]

I had this issue the other day as well when I tried to move to Rails 4.0.1, issue was resolved by sticking with Rails 4.0.

[klippx]

+1

We are upgrading to Rails 4.0 and during that process we get random spec failures due to ActionView::TemplateError when running the specs on CI (solanolabs). Never locally. This issue is caused by Sprockets gem, and is fixed in the master branch. However it is not available on Sprockets v2.11...

My temporary solution was to backport the master code into my own forked version:
gem 'sprockets', git: 'https://github.com/klippx/sprockets.git', branch: '2.11.0-actionview-template-error-fix'

The better solution would be that this gem doesn't lock down to Sprockets 2.11. What exactly is the issue that needs to be fixed?

Edit: Aha: #192

[justinmanley]

+1
I'm having similar dependency issues when trying to install sass-rails. At first, sass-rails complained about my sprockets 2.12.1 installation, so I removed the sprockets version spec from my Gemfile, deleted my Gemfile.lock, and ran bundle update. Bundler gave the following error:

Bundler could not find compatible versions for gem "activesupport":
  In Gemfile:
    sass-rails (= 4.0.3) ruby depends on
      sprockets-rails (~> 2.0) ruby depends on
        activesupport (>= 3.0) ruby

    rails (= 2.3.15) ruby depends on
      activesupport (2.3.15)

I'm not willing to mess around with activesupport versions just to get sass-rails installed...

[guilleiguaran]

sass-rails isn't compatible with rails 2.3