-
Notifications
You must be signed in to change notification settings - Fork 3
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
Gemfile specifying ruby "2.0.0" cannot contain Ruby 2.0 syntax. #100
Comments
To read your Gemfile we need to have ruby on the system, before we can know what version of ruby you've got declared we have to read your Gemfile. Currently this is done with system ruby which is Thanks for reporting the issue, unfortunately no fix for this right now comes to mind. Will keep open to evaluate options. |
No worries. |
Is this problem fixed by Ruby 2.0.0 Now Default on All New Ruby Applications? |
Sadly, not yet :(. We're still on 1.9.2 in the build environment. The only way to fix this would be to use ruby 2.0.0 in the build environment or move to something like |
Going to put this in the "won't fix" category. It won't change easily or any time soon. |
Ruby 2.0 syntax e.g.
%i{list of symbols}
is not supported in Gemfiles, even if they specifyruby "2.0.0"
.The resulting error
Invalid RUBY_VERSION specified
is misleading.If the Gemfile can be detected and parsed as Ruby 2.0, that'd be great.
Short of that, a more correct error message would help.
Example Gemfile:
Buildpack output:
The text was updated successfully, but these errors were encountered: