Closed smcoll closed 9 years ago
More context:
# .buildpacks
https://github.com/heroku/heroku-buildpack-python.git#v55
https://github.com/cyberdelia/heroku-geo-buildpack.git#1.3
# .env
export BUILDPACK_URL=https://github.com/ddollar/heroku-buildpack-multi.git
Put the geo buildpack first, and the python buildpack last in your .buildpack
file, this should help.
@cyberdelia interestingly, the reason the buildpacks are in that order is because otherwise it was building but without GIS support:
>>> from django.contrib.gis import gdal
>>> gdal.HAS_GDAL
False
i presumed that was because the multi-buildpack only uses the release configuration from the latter buildback (i mentioned this in a comment here: https://github.com/cyberdelia/heroku-geo-buildpack/issues/23#issuecomment-77044811)
Turns out the issue had to do with a cached progrium/buildstep image. This solved it:
$ docker pull progrium/buildstep
i was able to build from this buildback for months until yesterday. Here's what happens when i try, and following is the output from 'docker version'.
My procfile:
i'm running this on Ubuntu 14.10, with 3.13.0-46-generic as the kernel. If there's any additional info needed, let me know.