-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Saga plugin installation steps causing Docker build to fail #41
Comments
Isn't it the apt-get step here which is failing, not anything to do with the saga plugin? |
Hi @Robinlovelace I saw your issue in the saga plugin. My guess however is that you're installing QGIS from its ubuntugis repo (tailored to work with ubuntugis-unstable PPA; updated monthly or so), while two days ago GRASS has been updated in the PPA, typically breaking |
But I think you'll have to wait a little longer; latest build there is 2023-09-23. |
I am trying to build the image locally at the moment. And as @nyalldawson already mentionend, SAGA is not the problem. Instead an incompatible version of GRASS should be installed as already suspected by @florisvdh. Currently, I am using ubuntugis-nightly-release repo, let's see if this works out, probably not if the latest build is 2023-09-23. In any case, to avoid this issue in the future, let's switch to the ubuntugis-nightly-release. |
Locally, I could successfully build the container, so closing via 815c5a2. |
I was looking in the wrong place here; that's the URL of Ubuntu-nightly, built against the Ubuntu GDAL etc, not against the PPA. Of course the URL must be https://ubuntugis.qgis.org/ubuntugis-nightly-release/pool/main/q/qgis/?C=M;O=D. Latest build there is from 2023-09-24 17:12 which indeed appears to work with current GRASS already 🚀 . |
Great job all, just checking this after busy day, stoked to see it's fixed. Thank you! |
With the following message:
Source: https://github.com/geocompx/docker/actions/runs/6321057960/job/17164486628#step:8:644
Relevant lines:
docker/qgis/Dockerfile
Lines 48 to 50 in 00f4c90
Any ideas @jannes-m ?
The text was updated successfully, but these errors were encountered: