Rails asset precompile aborted on Heroku Push - uninitialized constant Rake::DSL - heroku

Question

I've seen this error from a couple years ago when Rake would break Rails, but this seems strange.
I deployed my Rails 3.2.16 app to Heroku just yesterday, but now precompiling assets fails with no changes to any assets. Full error below:
Running: rake assets:precompile
rake aborted!
uninitialized constant Rake::DSL
/tmp/build_96e5edbe-65ff-42fc-a7e8-e59432cc8de0/Rakefile:7:in `<top (required)>'
Curious if there were recent breaking changes or what I'm missing that would all of a sudden change things.
Rake is version 10.1.0. Ruby version 1.9.3 locally and 1.9.2 on Heroku.
Saw this: https://groups.google.com/forum/#!topic/heroku/6yjIiP69NqI (from ~2 years ago), which suggested instead of just include Rake::DSL to use
class Rails::Application
include Rake::DSL
end
Still, no idea why that would change overnight.

Answer 1

I had the same problem just now. I updated it the ruby version to 2.0.0 in the Gemfile (it was 1.9.2) and it deployed successfully after that.
To update the version simply add this under the source line in your Gemfile:
ruby "2.0.0"
I hope this solves your issues as well.

Answer 2

Same issue as the rest of you, just out of the blue went to update the application and push to heroku resulting in this error. If I find anything as I play around will update here.

Answer 3

Huzzah, I was successful running 'git push heroku master' after reinstalling rake and updating the Rakefile for DSL support.
Reinstall Rake:
gem uninstall rake
*I selected to uninstall all versions
gem install rake
Update Bundler:
bundle update
Update Rakefile, adding the require:
require 'rake/dsl_definition'
And Update Rakefile, adding the module:
module ::ApplicationName
class Application
include Rake::DSL
end
end
*Make sure to update ApplicationName to your app name.
Committed to git and ran an update:
git push heroku master
Hope that helps get you guys back up and running, not sure what happened with Heroku but if this corrects your issue #muzcat007 maybe you could update your Heroku ticket to have them look into this odd new DSL requirement.
Cheers