Skip to content

Doesn't support Ruby 2.1.0 #8

Closed

Description

@andypiper
-----> Downloaded app package (52K)
-----> Downloaded app buildpack cache (6.1M)
 !
 !     Invalid RUBY_VERSION specified: ruby-2.1.0
 !     Valid versions: ruby-1.9.3, ruby-1.9.2, ruby-1.8.7, ruby-2.0.0
 !

Using the latest Heroku Ruby buildpack https://github.com/heroku/heroku-buildpack-ruby does work. Sync with upstream?

Activity

  1. cf-gitbot commented on Mar 11, 2014

    @cf-gitbot

    We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: http://www.pivotaltracker.com/story/show/67296488

  2. karlkfi commented on Mar 24, 2014

    @karlkfi

    Great idea! We actually just spun up a Buildpacks team to deal with this kind of thing. We'll let them know.

    CF Community Pair (@karlkfi & @jfmyers9)

  3. danielgrippi commented on Mar 24, 2014

    @danielgrippi

    Dan from the buildpacks team here.

    We intend on re-forking Heroku's Ruby buildpack and going from there. This issue should be covered once we re-patch their master branch again.

  4. oppegard commented on Apr 2, 2014

    @oppegard

    Looking forward to this as well (specifically Ruby 2.1.1). /cc @thewoolleyman

  5. thewoolleyman commented on Apr 23, 2014

    @thewoolleyman

    Hi,

    What's the status on this?

    It looks like the original linked tracker story (http://www.pivotaltracker.com/story/show/67296488) has been deleted.

    However, there's another story "Make Heroku Ruby buildpack work offline for MRI" (https://www.pivotaltracker.com/story/show/67964992) which is marked as "accepted".

    Did the latter story address this issue? If so, can you give some details about how (e.g. where the new fork lives)?

    Thanks,
    -- Chad

  6. oppegard commented on May 16, 2014

    @oppegard

    Pinging on this issue. Any ETA on when the new buildpack will be available on PWS and PCF?

  7. jordi-pivotal commented on May 30, 2014

    @jordi-pivotal
    Contributor

    @thewoolleyman @oppegard sorry didn't see this. Our buildpack has been merged into cf-release so should be on PWS soon. You can also point to the buildpack repo on github in your manifest and it should use that one instead of the default one in PWS.

  8. jordi-pivotal commented on Jun 3, 2014

    @jordi-pivotal
    Contributor

    Closing this given the buildpack does support ruby 2.1.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions