-
-
Notifications
You must be signed in to change notification settings - Fork 23
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 OSX arm64 - attempt 2 #75
Conversation
…a-forge-pinning 2021.08.22.15.08.21
…nda-forge-pinning 2022.02.15.20.00.46
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 ( |
All builds except for Windows now succeed. @conda-forge/help-osx-arm64 @conda-forge/mumps @traversaro - could you please have a look? |
Random guess: |
Actually I installed locally and even if I installed the same version used in https://github.com/conda-forge/mumps-feedstock/runs/3253545563 (last successful build) I do not have any |
We could try to pass |
conda-forge/conda-forge-repodata-patches-feedstock#226 should fix it |
Great, thanks! |
An explanation is given in mamba-org/mamba#897 (comment) . TL;DR: It is related to a difference in how conda and mamba resolve packages, and now mamba is used by default. |
@conda-forge/mumps - this is ready for review. The windows build fail should be resolved by a restart of the CI in a few hours. |
Thanks for the hints @traversaro @isuruf ! |
@conda-forge-admin, please restart ci |
The Windows build is now ok. |
@Tobias-Fischer @traversaro Should I merge? |
Yes, thanks! |
Yes please :) |
@conda-forge-admin, rerender |
…nda-forge-pinning 2022.03.10.18.35.59
I think we can merge this @dalcinl |
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)