-
Notifications
You must be signed in to change notification settings - Fork 24
2.12.0 breaking my environment -- how do I downgrade? #540
Comments
I also see this problem... |
Same problem here... |
I had the same problem with the 2.12.0 release. A downgrade however worked with this in my It did not install |
Same problemm here. I solved it by locking the sprocket gem to 2.11.0.
|
I had the same problem too, but locking sprockets wasn't enough. I'm using Slim and it turned out that I needed to lock slim as well:
|
@snoblenet you have a typo "sprokets". Try "sprockets" :-D |
Hi guys. If you are using sass-rails make sure you are using 4.0.2 and this problem will be solved. |
sass-rails 4.0.2 simply downgrades sprockets:
It also downgrades sass to |
sass 3.3 doesn't work with sass-rails unfortunately, so we had to downgrade. |
@ngauthier slap-forehead -- you are right -- sprockets now locked at 2.11.0 -- thanks |
@josh Any plans to address this issue? It seems to be affecting a lot of Rails applications. |
We are working on it. Meanwhile, make sure your rails applications are Sent using mobile Gmail
|
Forcing sass-rails 4.0.2 in my Gemfile worked for me. Thanks! |
I opened #544 asking about why this is not following semver. Hopefully that will help those of you in this thread properly lock your dependencies if we know what happened here. |
- [release notes][1] - [release announcement][2] - [deprecation of db:test:* tasks][3] - Had to update `sass-rails` to 4.0.2 because of an [issue with sprockets 2.12][4] [1]: http://edgeguides.rubyonrails.org/4_1_release_notes.html [2]: http://weblog.rubyonrails.org/2014/3/25/Rails-4-1-rc2/ [3]: rails/rails#13528 [4]: sstephenson/sprockets#540
same problem solved with gem 'rails', '~> 4.1.0.rc2'
group :assets do
gem 'uglifier', '>= 1.0.3'
gem 'sprockets', '2.11.0' # 2.12.0 is broken
gem 'sprockets-rails'
gem 'coffee-rails'
end |
Same problem here. Locked it at 2.11.0 and it works. |
@josh Would you care to explain why this issue was closed? However the issue as is (downgrading to 2.11) is resolved the underlying issue that 2.12 won't work hasn't been addressed (I'm seeing the with ruby 2.1.2, rails 4.0.5 (4.0.8 won't even resolve)) |
Just as an update: simply requiring rails 4.1.2 (current stable) causes sprockets to resolve to 2.11 because sass-rails >= 4.0.2 locks it at 2.11. So If you try to force sprockets to update to 2.12 sass-rails complains. So, this would technically be an issue on sass-rails called "Update to sprockets 2.12". Right now on rails 4.1.2 there really is no issue, everything resolves fine and works fine. @bvogel The fact that 4.0.8 will not resolve with a forced sprockets 2.12 is not an issue unless there is a third gem involved that requires sprockets 2.12 and you have a three way conflict. If 4.0.8 resolves with 2.11 then everything is fine. |
@ngauthier Well the situation is that If I use |
Ah ok. I would suggest filing an issue with rails then? So maybe get a patch into Rails 4.0.9 that locks sprockets down to 2.11? Since Rails depends on sprockets and sass-rails depends on sprockets I don't think sprockets is at fault since it's at the bottom of the dependency tree. |
@ngauthier see sass-rails master |
I'm sorry it sounds like it's fixed, but when trying these solutions, I still get the error. gem 'rails', '4.1.2' gem 'sprockets' , '~> 2.11.0' |
@CzechsMix please paste the output from |
Invalid gemspec in [/var/lib/gems/1.9.1/specifications/ZenTest-4.10.1.gemspec]: Illformed requirement ["< 3.0, >= 1.8"] |
Can you paste the error you're getting too? I thought the error was a bundle error, sorry! |
The error happens when I push to heroku -----> Preparing app for Rails asset pipeline |
@CzechsMix this is a separate issue - you are using sprockets 2.11 and you are seeing a different issue then the OP. Your issue isn't related to 2.12. |
Oh? I'm sorry. It looked in the failure trace like sprockets was the source of the error, and this is one i found prior to downgrading to sprockets 2.11 I had the same version. |
Well sprockets SEEMS TO BE the source of the problem, but as it is a different error than the OP is seeing. You should create a separate issue. |
I fixed it. Looks like I just needed to precompile my assets (namely bootstrap) before pushing. Thanks! |
solved with #540 (comment) |
Is it possible to use |
sprokets 2.12.0 is breaking my environment with the following trace:
How do I downgrade to 2.11.0? Putting
gem "sprockets", "2.11.0"
and typingbundle install
orbundle update
is not working. I get this error:BTW, from my Gemlock file:
The text was updated successfully, but these errors were encountered: