New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Ruby 2.0.0 #11
Comments
Ouch, that hurt. I've just updated my Gemfile to My Gemfile had
Update 1: I also see this in the deploy log -- Update 2: I resolved this by setting a specific revision of the buildpack --
|
Swap to Heroku's ruby buildpack
|
fixed in a new push, uses 1.7.4, but not 2.0 mode |
will be fixed with issue #12 |
Thanks for trying to fix this issue, and realize it has impacts on other uses hence the revert and new issue #12 I took your commit, forked the repository and applied the same changes from you repository (341891f) on on my fork acds@c7a4b63. All seem to be OK I then ran into the following issues:
When reverting to your build pack I get the same errors. I also get this if I try and do anything on Heroku
Also looking at the code my project does not use postgress (in favor of mongoid) as mentioned in the compile precompile_assets function. Not sure is this is a side effect ? Finally for those that want to lock their Heroku build pack to a specific commit can do this
Any help or thoughts greatly appreciated ! |
Seem the problem is after the "first" OK issues is not directly with assets precompile but with the temp storage used for gems git repositories when defined as such in the gemfile. What I pick up is that its referring to 1.9 not 2.0 compatibility or the JRuby 1.7.9 ! I create a new Heroku app and all (mostly) worked as expected I set up your build pack locked at he commit before you reverted.
and push the code:
Seems there is some issues with rdoc-data and then with precompiling assets. I manually compile the assets locally.
commit them to git and re push and get the same issue.
I create a new app on Heroku again and all is good. here is the heroku app config
I'm now completely lost... |
You had "ruby '2.0.0'" in your Gemfile. In your first repo/app you didn't have the "JRUBY_OPTS=--2.0" thing, but in the second you did, therefore you didn't you get "Bundler::RubyVersionMismatch: Your Ruby version is 1.9.3, but your Gemfile specified 2.0.0" there. Yes, this will be fixed with #12 On Tuesday 23 July 2013 at 23:34, acds wrote:
|
This is now fixed, see #12 and the updated readme |
What would it take to be able to support ruby 2.0.0 since 1.7.4 JRuby 1.7.4 already includes experimental Ruby 2.0 support. We need to be able to test this stuff out right ?
I'm not sure how to fork and configure this in combination with other options ?
The text was updated successfully, but these errors were encountered: