Closed nyurik closed 1 year ago
Binary packaging, such as in Debian, is not under the control of here the upstream project. This should be reported to the Debian PROJ package manintainer. That said you may use the projsync utility to download the grids you need: https://proj.org/apps/projsync.html
@rouault thanks! Would projsync somehow auto-satisfy the dependency on proj-data:arm64
on a x64 environment, so that when i install libproj9
afterwards, it will be like "yep, already have it, no need to install"? Unlikely?
The problem it seems is that libproj9
has proj-data:arm64
as a dependency, instead of depending on proj-data:any
(per stackoverflow response).
Please close this issue, as noted on the pkg-grass-devel list:
The upstream PROJ-data project is for the grid shift files, it is not related to the proj-data package which provides the resource files [0] for libproj.
That post also points out the issue with the unmaintained proj package in Ubuntu and the EOL of xenial.
The Multi-Arch issue was fixed six years ago in proj (4.9.3-2~exp1) which is available in Ubuntu since bionic and in Debian since buster.
When using proj in a multi-architecture environment (compiling cross-platform), the
proj-data
debian package does not exist. Apparently this bug existed at least 5 years ago, see stackoverflow postThe question above has some hacky solutions on how to get around this issue, but clearly it would be better to solve it upstream... not certain if this is the right place.
I was trying to use https://github.com/cross-rs/cross 's docker image, and inside install proj with:
docker run --rm -it ghcr.io/cross-rs/aarch64-unknown-linux-gnu:latest
Thanks!