-
-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable ogre-next dependency #45
Conversation
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 ( |
@conda-forge-admin, please rerender |
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/libignition-rendering4-feedstock/actions/runs/2561501673. |
79ccaa6
to
66073ce
Compare
Blocked also by conda-forge/ogre-next-feedstock#1 . |
Build is failing with:
Probably ign-rendering needs to be updated for Ogre-Next 2.3.0 compatibility, until now it has only had only compatibility with Ogre-Next 2.2.*, see Ogre-Next changelog (https://ogrecave.github.io/ogre-next/api/2.3/_ogre23_changes.html):
|
ignition-rendering is migrated to ogre-next 2.3.0 in gazebosim/gz-rendering#553, but that is just for the branch that will become gz-rendering7. I am not sure how easy it will be to backport the change. Probably it may be easier to just produce ogre-next 2.2 binaries and use those here. |
Done in conda-forge/ogre-next-feedstock#3, adding the pin now. |
Once packages merged in conda-forge/staged-recipes#19384 are available, we can start the CI.
Checklist
0
(if the version changed)conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)