[GDAL] Bump to v3.7.1

[jeremiahpslewis]

No description provided.

[giordano]

As I said already, it's more likely we want to update compat bounds. For example using HDF5 1.14 would be better, since we compile that one from source.

[jeremiahpslewis]

[ Info: Copying content of bundled in srcdir...
--
  | Updating registry at `/cache/julia-buildkite-plugin/depots/e2fd9734-29d8-45cd-b0eb-59f7104f3131/registries/General.toml`
  | Resolving package versions...
  | ERROR: LoadError: Unsatisfiable requirements detected for package OpenSSL_jll [458c3c95]:
  | OpenSSL_jll [458c3c95] log:
  | ├─possible versions are: 1.1.1-3.0.9 or uninstalled
  | ├─restricted by compatibility requirements with HDF5_jll [0234f1f7] to versions: 3.0.8-3.0.9
  | │ └─HDF5_jll [0234f1f7] log:
  | │   ├─possible versions are: 1.10.5-1.14.0 or uninstalled
  | │   └─restricted to versions 1.14.0 by an explicit requirement, leaving only versions 1.14.0
  | └─restricted by compatibility requirements with LibPQ_jll [08be9ffa] to versions: 1.1.10-1.1.21 — no versions left
  | └─LibPQ_jll [08be9ffa] log:
  | ├─possible versions are: 12.3.0-14.3.0 or uninstalled
  | └─restricted to versions * by an explicit requirement, leaving only versions 12.3.0-14.3.0

Does this mean LibPQ needs to be rebuilt with v3.x OpenSSL?

[giordano]

Yes:

Yggdrasil/L/LibPQ/build_tarballs.jl

Line 75 in 21d0e10

Dependency("OpenSSL_jll"; compat="1.1.10"),

[visr]

Would be great to have a new GDAL build again, thanks for working on this. I see you also make progress in #7053.

Left some comments to include the latest changes.

[visr]

Looks good to me, thanks!

[jeremiahpslewis]

@giordano This should be ready to merge now.

[giordano]

PROJ_jll above had a ~ compat specification. @visr what's the usual thing to do here with this package? Is ^ (the default) enough?

[visr]

Yeah I think this is fine. Since PROJ_jll has the 100x version_offset, I figured in #7366 it's easier to tag it as breaking using that, rather than forcing all dependencies to use ~.

[visr]

Sorry I missed this in review, but this version offset should not have been set back to 0, since now the major version is v300, while the previous one was v301. Should we yank v300.700.200 from the registry and create a new v301 build?

[giordano]

Probably good, yeah