Bump the GMT version to 6.6.0 in CI

[seisman]

See checklist at #4017.

Previous PR at #2962.

[seisman]

It seems there are conflicts between GMT and contextily.

[weiji14]

It seems there are conflicts between GMT and contextily.

Yes, GMT 6.6.0 was built on GDAL 3.11, and contextily depends on rasterio which doesn't support GDAL 3.11 yet. Need to wait for conda-forge/rasterio-feedstock#332

  error    libmamba Could not solve for environment specs
      The following packages are incompatible
      ├─ contextily =* * is installable with the potential options
      │  ├─ contextily [0.9.0|0.9.2] would require
      │  │  └─ python =2.7 * with the potential options
      │        │  └─ libgdal [>=3.7.2,<3.8.0a0 *|>=3.7.3,<3.8.0a0 *], which can be installed (as previously explained);
      │        ├─ rasterio [1.4.2|1.4.3] would require
      │        │  └─ libgdal-core [>=3.10.0,<3.11.0a0 *|>=3.10.2,<3.11.0a0 *] with the potential options
      │        │     ├─ libgdal-core [3.10.2|3.10.3|3.9.3], which can be installed (as previously explained);
      │        │     ├─ libgdal-core [3.10.0|3.10.1|3.10.2|3.9.2|3.9.3], which can be installed (as previously explained);
      │        │     └─ libgdal-core 3.10.3, which can be installed;
      │        ├─ rasterio 1.4.2 would require
      │        │  └─ libgdal-core >=3.9.3,<3.10.0a0 *, which can be installed (as previously explained);
      │        ├─ rasterio [1.0.23|1.0.24|...|1.1.2] would require
      │        │  └─ libgdal [>=2.4.1,<2.5.0a0 *|>=2.4.2,<2.5.0a0 *|>=2.4.3,<2.5.0a0 *|>=3.0.1,<3.1.0a0 *|>=3.0.2,<3.1.0a0 *] with the potential options
      │        │     ├─ libgdal [2.4.1|2.4.2|2.4.3|3.0.1|3.0.2] would require
      │        │     │  └─ geos >=3.7.2,<3.7.3.0a0 *, which can be installed;
      │        │     ├─ libgdal [2.4.4|3.0.2|3.0.3|3.0.4] would require
      │        │     │  └─ geos >=3.8.0,<3.8.1.0a0 *, which can be installed;
      │        │     └─ libgdal [2.4.4|3.0.4|...|3.2.1] would require
      │        │        └─ geos >=3.8.1,<3.8.2.0a0 *, which can be installed;
      │        ├─ rasterio [1.1.3|1.1.4|1.1.5] would require
      │        │  └─ libgdal [>=2.4.4,<2.5.0a0 *|>=3.0.4,<3.1.0a0 *], which can be installed (as previously explained);
      │        ├─ rasterio [1.1.6|1.1.7|...|1.2.6] would require
      │        │  └─ libgdal [>=3.1.2,<3.2.0a0 *|>=3.1.3,<3.2.0a0 *|>=3.1.4,<3.2.0a0 *|>=3.2.1,<3.3.0a0 *] with the potential options
      │        │     ├─ libgdal [3.1.4|3.2.1|...|3.3.3] would require
      │        │     │  └─ geos >=3.9.1,<3.9.2.0a0 *, which can be installed;
      │        │     ├─ libgdal [2.4.4|3.0.4|...|3.2.1], which can be installed (as previously explained);
      │        │     └─ libgdal [3.1.4|3.2.1] would require
      │        │        └─ geos >=3.9.0,<3.9.1.0a0 *, which can be installed;
      │        ├─ rasterio [1.2.10|1.3.0] would require
      │        │  └─ libgdal >=3.5.0,<3.6.0a0 * with the potential options
      │        │     ├─ libgdal [3.5.3|3.6.3|3.6.4|3.7.0], which can be installed (as previously explained);
      │        │     ├─ libgdal [3.3.3|3.4.1|3.4.2|3.4.3|3.5.0] would require
      │        │     │  └─ geos >=3.10.2,<3.10.3.0a0 *, which can be installed;
      │        │     ├─ libgdal [3.4.3|3.5.3|...|3.6.3], which can be installed (as previously explained);
      │        │     ├─ libgdal [3.5.0|3.5.1|3.5.2|3.5.3|3.6.0] would require
      │        │     │  └─ geos >=3.11.0,<3.11.1.0a0 *, which can be installed;
      │        │     └─ libgdal 3.5.0 would require
      │        │        └─ geos >=3.10.3,<3.10.4.0a0 *, which can be installed;
      │        ├─ rasterio 1.2.10 would require
      │        │  └─ libgdal >=3.4.0,<3.5.0a0 * with the potential options
      │        │     ├─ libgdal [3.3.3|3.4.0|3.4.1] would require
      │        │     │  └─ geos >=3.10.1,<3.10.2.0a0 *, which can be installed;
      │        │     ├─ libgdal [3.3.3|3.4.0] would require
      │        │     │  └─ geos >=3.10.0,<3.10.1.0a0 *, which can be installed;
      │        │     ├─ libgdal [3.3.3|3.4.1|3.4.2|3.4.3|3.5.0], which can be installed (as previously explained);
      │        │     └─ libgdal [3.4.3|3.5.3|...|3.6.3], which can be installed (as previously explained);
      │        ├─ rasterio 1.2.10 would require
      │        │  └─ libgdal >=3.4.1,<3.5.0a0 *, which can be installed (as previously explained);
      │        ├─ rasterio [1.2.10|1.2.6|1.2.7|1.2.8|1.2.9] would require
      │        │  └─ libgdal [>=3.3.0,<3.4.0a0 *|>=3.3.1,<3.4.0a0 *|>=3.3.2,<3.4.0a0 *|>=3.3.3,<3.4.0a0 *], which can be installed (as previously explained);
      │        ├─ rasterio [1.2.4|1.2.5|1.2.6] would require
      │        │  └─ libgdal >=3.2.2,<3.3.0a0 *, which can be installed (as previously explained);
      │        ├─ rasterio [1.3.0.post1|1.3.1|1.3.2|1.3.3] would require
      │        │  └─ libgdal [>=3.5.1,<3.6.0a0 *|>=3.5.2,<3.6.0a0 *|>=3.5.3,<3.6.0a0 *], which can be installed (as previously explained);
      │        └─ rasterio 1.3.4 would require
      │           └─ libgdal >=3.6.0,<3.7.0a0 *, which can be installed (as previously explained);
      └─ gmt =6.6.0 * is not installable because it requires
         ├─ geos >=3.13.1,<3.13.2.0a0 *, which conflicts with any installable versions previously reported;
         ├─ libgdal-core >=3.11.3,<3.12.0a0 *, which requires
         │  └─ openssl >=3.5.1,<4.0a0 *, which conflicts with any installable versions previously reported;
         └─ libglib >=2.84.2,<3.0a0 *, which requires
            └─ pcre2 >=10.45,<10.46.0a0 *, which conflicts with any installable versions previously reported.
  critical libmamba Could not solve for environment specs

[seisman]

rasterio v1.4.4 will be the release that supports GDAL 3.11, but it's unclear when it will come out.

I'm wondering if we should rebuild GMT 6.6 with GDAL 3.10 instead, so that we can at least have a build that can be used in our CI. Of course, we need to rebuild GMT 6.6 again with GDAL 3.11 later.

[seisman]

New GMT 6.6 build in #329 still doesn't work, likely because conflicts with geos or proj

      │        ├─ rasterio 1.4.2 would require
      │        │  ├─ libgdal-core >=3.10.0,<3.11.0a0 * with the potential options
      │        │  │  ├─ libgdal-core [3.10.0|3.10.1|3.10.2|3.9.2|3.9.3], which can be installed (as previously explained);
      │        │  │  ├─ libgdal-core 3.10.3 would require
      │        │  │  │  └─ geos >=3.13.1,<3.13.2.0a0 *, which conflicts with any installable versions previously reported;
      │        │  │  ├─ libgdal-core [3.10.2|3.10.3|3.9.3], which cannot be installed (as previously explained);
      │        │  │  ├─ libgdal-core 3.10.3 would require
      │        │  │  │  ├─ geos >=3.14.0,<3.14.1.0a0 *, which conflicts with any installable versions previously reported;
      │        │  │  │  ├─ pcre2 >=10.46,<10.47.0a0 *, which can be installed;
      │        │  │  │  └─ proj >=9.6.2,<9.7.0a0 *, which conflicts with any installable versions previously reported;
      │        │  │  ├─ libgdal-core 3.10.3 would require
      │        │  │  │  ├─ geos >=3.14.0,<3.14.1.0a0 *, which conflicts with any installable versions previously reported;
      │        │  │  │  └─ proj >=9.6.2,<9.7.0a0 *, which conflicts with any installable versions previously reported;
      │        │  │  └─ libgdal-core 3.10.3 would require
      │        │  │     ├─ geos >=3.14.0,<3.14.1.0a0 *, which conflicts with any installable versions previously reported;
      │        │  │     └─ proj >=9.7.0,<9.8.0a0 *, which conflicts with any installable versions previously reported;
      │        │  └─ proj >=9.5.0,<9.6.0a0 *, which can be installed;

[weiji14]

Tried locally and the resolver worked, just needed to wait for the conda-forge CDN to refresh after merging conda-forge/gmt-feedstock#329 (usually takes an hour or two). I've re-ran the CI jobs and GMT 6.6 seems to be working now with ghostscript 10.04.0 🎉

Let's test on ghostscript 10.05.1, and then 10.06.0.

[weiji14]

Have tested GMT 6.6 with ghostscript 10.05.1 and 10.06.0, no major issues it seems. Test failures are just the usual Windows segfaults.

I'll let you decide @seisman whether to merge this in for PyGMT v0.17.0 or not.