Comments (6)
I see now. Thanks!
I have resolved it!
from heroku-geo-buildpack.
@edmorley That surely makes things clearer from the docs. Thanks!
from heroku-geo-buildpack.
The buildpack works for me:
$ mkdir testcase && cd $_
$ git init && touch test && git add -A && git commit -m 'Initial commit'
...
$ h create --buildpack https://github.com/heroku/heroku-geo-buildpack
Creating app... done, ⬢ afternoon-refuge-50608
Setting buildpack to https://github.com/heroku/heroku-geo-buildpack... done
https://afternoon-refuge-50608-646c324cc8d9.herokuapp.com/ | https://git.heroku.com/afternoon-refuge-50608.git
$ git push heroku main
...
remote: -----> Building on the Heroku-22 stack
remote: -----> Using buildpack: https://github.com/heroku/heroku-geo-buildpack
remote: -----> Geo Packages (GDAL/GEOS/PROJ) app detected
remote: -----> Installing GDAL-3.5.0
remote: -----> Installing GEOS-3.10.2
remote: -----> Installing PROJ-8.2.1
remote: -----> Discovering process types
remote: Procfile declares types -> (none)
remote:
remote: -----> Compressing...
remote: Done: 22.3M
remote: -----> Launching...
remote: Released v3
From the error message I see you are using Heroku-18. The Heroku-18 stack is EOL and can no longer be used on Heroku:
https://devcenter.heroku.com/changelog-items/2583
I presume you are using the Geo buildpack via another means (eg Dokku)? (In the future, including the full build log and any other relevant details like the platform on which it is being run would be helpful.)
If so, you'll need to update to a newer stack (Heroku-20 or Heroku-22).
Lastly, you'll also need the latest version of this buildpack, so that you have:
c452e72
from heroku-geo-buildpack.
Thanks for the timely response!
Indeed I am using Dokku and I have been using the buildpack for a couple of years now(initially with Heroku, then a year now with Dokku) and never had an issue except today. I initially had GDAL_VERSION 2.4.2 and thought that was the issue but switching to 3.5.0 raises the same error. Here's the build log:
-----> Building reservations from herokuish
-----> Adding BUILD_ENV to build environment...
-----> Warning: Multiple default buildpacks reported the ability to handle this app. The first buildpack in the list below will be used.
Detected buildpacks: multi python
-----> Multipack app detected
=====> Downloading Buildpack: https://github.com/heroku/heroku-geo-buildpack.git
=====> Detected Framework: Geo Packages (GDAL/GEOS/PROJ)
-----> Installing GDAL-3.5.0
! Requested GDAL Version (3.5.0) is not available for this stack (heroku-18).
! See: https://github.com/heroku/heroku-geo-buildpack#available-versions
! Aborting.
I see that there hasn't been an update to the library recently so I am wondering why the build is suddenly not working. My last successful build was about a week ago
from heroku-geo-buildpack.
The binaries for EOL stacks were removed recently (since they are unused on Heroku, since it's not possible to build on these stacks there), so you will need to update to a newer stack:
From the error message I see you are using Heroku-18. The Heroku-18 stack is EOL and can no longer be used on Heroku:
https://devcenter.heroku.com/changelog-items/2583
from heroku-geo-buildpack.
In #46 I've removed the leftover Heroku-18 references in the README to make the lack of Heroku-18 support clearer.
from heroku-geo-buildpack.
Related Issues (20)
- heroku-buildpack-python overwrites GEOS and GDAL exports HOT 1
- Add support for Heroku-20 HOT 4
- Set {GDAL,GEOS,PROJ4}_LIBRARY_PATH in export too HOT 4
- Auto-detection of library locations not working HOT 1
- Interaction with the APT buildpack can cause "libblas.so.3: cannot open shared object file"
- Pip installation of GDAL fails with GCC undeclared identifer errors HOT 1
- Remove support for Heroku-16
- Which GDAL versions are available ? HOT 2
- OSError: libkmldom.so.1: cannot open shared object file: No such file or directory HOT 1
- Install PROJ-8.2.1 HOT 1
- PROJ 7.2.0 or above HOT 1
- GDAL 3.5.0 fails to compile with `PROJ 6 symbols not found` HOT 1
- ERROR 4: Unable to open EPSG support file gcs.csv. Try setting the GDAL_DATA environment variable to point to the directory containing EPSG csv files. HOT 4
- error in GDAL setup command: use_2to3 is invalid HOT 1
- Troubles with Heroku 22 HOT 4
- heroku-22 stack - error: [Errno 2] No such file or directory: 'gdal-config' HOT 4
- gdal_merge.py support? HOT 5
- libkml build failing HOT 1
- Building newer GDAL fails due to removal of autoconf support
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from heroku-geo-buildpack.