Andrew Bezzub

Happened for me too after going from ruby 2.4.1 to 2.4.5. Did everyone resolve the issue by not using this buildpack?

I can confirm that latest commit (https://github.com/cyberdelia/heroku-geo-buildpack/commit/77fe3e6bb288f0ef8f94c6c2ed3c6a592d79e225) in the buildpack broke the build. Reverting to previous version makes it work.

This brought down our integration, any ETA on resolution?

As a data point, not tracking all database migrations is a dealbreaker for our team and we will have to use another tool instead of `migrate` or write our own....

@sourcec0de we are using goose and that works well enough for our use case

I also need Python 3.4 support. @thenovices can you please explain how you build packages? I see that https://github.com/thenovices/npscipy-binaries mentions using virtual machines, do you have some scripts to do...

No problem. Do you just use VM with Ubuntu of the same version that Heroku uses? Or are there some additional requirements? Thanks

I ended up using conda to install math packages. There was a Python 2 buildpack for conda that I tweaked to work with Python 3: https://github.com/teamupstart/conda-buildpack