Rebuild for libgdal38

[regro-cf-autotick-bot]

This PR has been triggered in an effort to update libgdal38.

Notes and instructions for merging this PR:

1. Please merge the PR only after the tests have passed.
2. Feel free to push to the bot's branch to update this PR if needed.

Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.

---

If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase code>@<space/conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

_{This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/6881445924, please use this URL for debugging.}

[conda-forge-webservices[bot]]

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.

[traversaro]

Build is failing with:

Solving environment (_test_env): ...working... failed
WARNING: failed to get install actions, retrying.  exception was: Invalid spec 'ogre[version='>=1.10.12,>=1.10.12,<1.11.0a0',build_number=3]': Libmamba only supports a subset of the MatchSpec interface for now. You can only use ('name', 'version', 'build', 'channel', 'subdir'), but you tried to use ('build_number',).
Reloading output folder: ...working... done
Solving environment (_test_env): ...working... failed
Reloading output folder: ...working... done
Solving environment (_test_env): ...working... failed
Reloading output folder: ...working... done
Solving environment (_test_env): ...working... failed
ERROR: Failed to get install actions, max retries exceeded.

InvalidMatchSpec: Invalid spec 'ogre[version='>=1.10.12,>=1.10.12,<1.11.0a0',build_number=3]': Libmamba only supports a subset of the MatchSpec interface for now. You can only use ('name', 'version', 'build', 'channel', 'subdir'), but you tried to use ('build_number',).

Something changed recently?

[traversaro]

Last build with libmamba 1.4.9 in https://dev.azure.com/conda-forge/84710dde-1620-425b-80d0-4cf5baca359d/_apis/build/builds/816864/logs/31 was working fine.

[Tobias-Fischer]

/cc @conda-forge/libmamba

[AntoinePrv]

I haven't met this error before, but as it states, Mamba's match specs are currently not complete...

[Tobias-Fischer]

Should we submit a repodata patch for build numbers 0, 1, 2 @traversaro? The easiest would probably be to mark them as broken?

[Tobias-Fischer]

@conda-forge-admin, please rerender

[traversaro]

@conda-forge-admin, please rerender

[traversaro]

I suspect this was a regression of conda-smithy 3.28.0 ( https://github.com/conda-forge/conda-smithy/releases/tag/v3.28.0 ) that changed the build tool from conda mambabuild to conda build with solver libmamba. However, conda create -n gazebo gazebo with libmamba solver installs without problem the latest gazebo with the ogre >=1.10.12[build_number=3] run constraint, so I am not sure why this problem happens only using conda build.

[traversaro]

I am not sure why this problem happens only using conda build.

By the way, the problem is not happening with conda build locally, so I hope that a recent version of conda/conda-build/libmamba not sure what solved it.

[github-actions[bot]]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• azure: passed

Thus the PR was passing and merged! Have a great day!