Doesn't support Ruby 2.1.0 about ruby-buildpack

[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

[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)

[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.

[oppegard]

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

[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

[oppegard]

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

[jordi-pivotal]

@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.

[jordi-pivotal]

Closing this given the buildpack does support ruby 2.1.0