meta.yaml: try to force rebuild against GDAL 3.6.2

[rouault]

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[rouault]

@conda-forge-admin, please rerender

[github-actions]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/qgis-feedstock/actions/runs/3869370353.

[rouault]

hum rebuild attempts still draw GDAL 3.6.1... Probably the version isn't fully "promoted" yet ? Anyway rebuilding QGIS against 3.6.2 aren't strictly required as 3.6.2 is ABI compatible with 3.6.0

[SrNetoChan]

Last time we had to rebuild PostgreSQL first so that 3.6.1 was picked up.

[gillins]

Yeah there will be something that's out of date that needs to be rebuilt to get 3.6.2. I'll try and find time later in the week to track this down.

[rouault]

I'll try and find time later in the week to track this down.

out of curiosity, is there some command line invokation / tool to figure that ?

[gillins]

I don't know of any... I normally have to try every package in turn and see what won't install with the latest gdal.
This may prompt me to do something I've been considering for ages - write a script that runs once a day or so and:
a) notifies me if the latest qgis and gdal won't install together, and
b) tries something like the above in an automated way so we know what package is the problem.

I'm a bit out of the loop with what's happening with conda forge so it could be someone has already done something like this. Qgis can't be the only package with complex dependences that has this kind of problem semi regularly.

[SrNetoChan]

Mamba has some commands to show for a specific package, what it depends of and which itself is a dependency. Maybe useful fo find the culprits.

[gillins]

pyproj won't install with gdal 3.6.2. Attempting fix that now.

[xylar]

@gillins, gdal has migrated to proj 9.1.1. There are issues with pyproj with this version, see conda-forge/pyproj-feedstock#126 and pyproj4/pyproj#1192. So we were hoping to hold off on migrating pyproj to that version.

For now, the easiest solution might be to build gdal 3.6.2 with proj 9.1.0.

[xylar]

conda-forge/gdal-feedstock#713 should hopefully help.

[gillins]

Indeed it does! Creating a new env seems to pick up latest qgis and gdal 3.6.2. Closing.