libsdformat v12.2.0

[regro-cf-autotick-bot]

It is very likely that the current package version for this feedstock is out of date.
Notes for merging this PR:

1. Feel free to push to the bot's branch to update this PR if needed.
2. The bot will almost always only open one PR per version.
   Checklist before merging this PR:

• Dependencies have been updated if changed: see upstream
• Tests have passed
• Updated license if changed and license_file is packaged

Note that the bot will stop issuing PRs if more than 3 Version bump PRs generated by the bot are open. If you don't want to package a particular version please close the PR.

NEW: If you want these PRs to be merged automatically, make an issue with @conda-forge-admin,please add bot automerge in the title and merge the resulting PR. This command will add our new bot automerge feature to your feedstock!

Closes: #51

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 @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. If you would like a local version of this bot, you might consider using rever. Rever is a tool for automating software releases and forms the backbone of the bot's conda-forge PRing capability. Rever is both conda (conda install -c conda-forge rever) and pip (pip install re-ver) installable.
Finally, feel free to drop us a line if there are any issues!
This PR was generated by https://github.com/regro/autotick-bot/actions/runs/1497251194, please use this URL for debugging}

Dependency Analysis

Please note that this analysis is highly experimental. The aim here is to make maintenance easier by inspecting the package's dependencies. Importantly this analysis does not support optional dependencies, please double check those before making changes. If you do not want hinting of this kind ever please add bot: inspection: false to your conda-forge.yml. If you encounter issues with this feature please ping the bot team conda-forge/bot.

Analysis of the source code shows a discrepancy between the library's imports and the package's stated requirements in the meta.yaml.

Packages found by inspection but not in the meta.yaml:

• psutil

[conda-forge-linter]

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.

[github-actions]

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

I considered the following status checks when analyzing this PR:

• linter: passed
• travis: failed
• azure: failed

Thus the PR was not passing and not merged.

[Tobias-Fischer]

Might potentially need conda-forge/libignition-tools-feedstock#12 but I'm not sure whether that'll fix it ..

[Tobias-Fischer]

This is failing on Linux with the same error as described in gazebosim/gz-tools#67. In that PR, a change was introduced that uses the full path to the backward tools library for OSX. This seems to work fine as tests are passing there. Should we simply patch ign-tools to always use the full path, on all platforms?

What do you think @traversaro?

Best, Tobi

[traversaro]

This is failing on Linux with the same error as described in ignitionrobotics/ign-tools#67. In that PR, a change was introduced that uses the full path to the backward tools library for OSX. This seems to work fine as tests are passing there. Should we simply patch ign-tools to always use the full path, on all platforms?

What do you think @traversaro?

I do not know why it is necessary, but if it works that's ok!

[Tobias-Fischer]

Hmm this is very odd. The new build of ign-tools was pulled in, but it still fails at the same place. I am sure it worked locally yesterday, just running another build to check.

[Tobias-Fischer]

Test is passing locally. Should we just skip the one failing test?

[github-actions]

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

Commits were made to this PR after the automerge label was added. For security reasons, I have disabled automerge by removing the automerge label. Please add the automerge label again (or ask a maintainer to do so) if you'd like to enable automerge again!

[traversaro]

Test is passing locally. Should we just skip the one failing test?

Yes, I suspect that tests were also passing locally without conda-forge/libignition-tools-feedstock#14 . In any case, skippoing the tests make sense.