Rails 3.1rc4 asset pipeline broke after Ruby update? How to re-activate/configure it?

Question

Somehow this is related but I\'m not sure how/why?

Just upgraded from Ruby 1.9.2-p180 to 1.9.2-p290 via RVM\'s rvm upgrade command...and now my asset pi

Answer 1

I ended up just blowing out the whole problematic gemset and starting anew. Lesson learned:

Don't trust rvm upgrade. Install the new Ruby w/in RVM. Then manually rebuild (or bundle install) your gemsets.

Answer 2

It seems that version 2.0.0.beta.11 of sprockets broke the assets pipeline. Putting

gem 'sprockets', '= 2.0.0.beta.10'

into your Gemfile seems to fix the problem (it worked for me). Rails seems to automatically use the most recent version of the beta for whatever reason so if you just started your project recently or updated all your gems it probably broke it.

Note that this info isn't mine originally, I got the fix from http://groups.google.com/group/rubyonrails-core/browse_thread/thread/59d8c7813b4d1bbe?pli=1

He explains the problem for ver. 2.0.0.beta.11 but I was using ver. 2.0.0.beta.12 with the same results so it seems that they haven't fixed it yet.

EDIT: It seems that upgrading your rails to 3.1.rc5 also fixes the problem