-
-
Notifications
You must be signed in to change notification settings - Fork 5
Migrate to rattler-build and cleanup patches #85
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
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 ( I do have some suggestions for making it better though... For recipe/meta.yaml:
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/15488995589. Examine the logs at this URL for more detail. |
Perfect, the test fail as expected. However, at this point in my experience is difficult to debug issues with conda-build, so even if this is a complex feedstock, it could make sense to first try to migrate to rattler-build. |
@conda-forge-admin please rerender |
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 ( |
…nda-forge-pinning 2025.06.07.01.03.35
I had some problem in importing the old patches in rattler-build, so I normalized them by importing them in git on top of the mujoco 3.3.2 tag with |
Even after the rattler-build conversion, the segfault is still there:
|
Ok, as the rattler-build migration and patches cleanup is something it make sense to merge indipendently from the mjpython investigation and fixes, I will reopen a follow up PR that uncomments the test to continue to investigation. |
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)