Skip to content

Conversation

@traversaro
Copy link
Member

@traversaro traversaro commented May 2, 2025

We stopped producing binaries for osx-64 (Intel) in #1712, so it does not make sense that we continue to test them, and we should test osx-arm64 binaries now.

@traversaro
Copy link
Member Author

@traversaro
Copy link
Member Author

The problem is still there:

Could not solve for environment specs
The following packages are incompatible
├─ mamba >=2.0.8 * is installable and it requires
│  └─ libmamba [==2.0.8 h10bde34_0|==2.0.8 h10bde34_1|...|==2.1.0 ha117084_1], which requires
│     └─ libarchive >=3.7.7,<3.8.0a0 *, which requires
│        └─ libxml2 [>=2.13.5,<2.14.0a0 *|>=2.13.7,<2.14.0a0 *] with the potential options
│           ├─ libxml2 [2.13.5|2.13.6|2.13.7] would require
│           │  └─ icu >=75.1,<76.0a0 *, which can be installed;
│           └─ libxml2 [2.13.5|2.13.6|2.13.7] would require
│              └─ icu <0.0a0 *, which can be installed;
├─ pin on python 3.12.* =* * is installable and it requires
│  └─ python =3.12 *, which can be installed;
└─ wb-toolbox =* * is not installable because there are no viable options
   ├─ wb-toolbox 5.6.0 would require
   │  └─ icub-main >=2.2.1,<2.2.2.0a0 *, which requires
   │     └─ python >=3.10,<3.11.0a0 *, which conflicts with any installable versions previously reported;
   ├─ wb-toolbox [5.6.0|5.6.1] would require
   │  └─ icub-main [>=2.3.0,<2.3.1.0a0 *|>=2.4.0,<2.4.1.0a0 *|>=2.4.1,<2.4.2.0a0 *] but there are no viable options
   │     ├─ icub-main [2.2.1|2.3.0|2.4.0|2.4.1|2.5.0], which cannot be installed (as previously explained);
   │     ├─ icub-main [2.3.0|2.4.0|2.4.1|2.5.0] would require
   │     │  └─ python >=3.11,<3.12.0a0 *, which conflicts with any installable versions previously reported;
   │     ├─ icub-main [2.3.0|2.4.0|2.4.1|2.5.0] would require
   │     │  └─ python >=3.8,<3.9.0a0 *, which conflicts with any installable versions previously reported;
   │     └─ icub-main [2.3.0|2.4.0|2.4.1|2.5.0] would require
   │        └─ python >=3.9,<3.10.0a0 *, which conflicts with any installable versions previously reported;
   └─ wb-toolbox 5.6.1 would require
      └─ icub-main >=2.5.0,<2.5.1.0a0 * but there are no viable options
         ├─ icub-main [2.2.1|2.3.0|2.4.0|2.4.1|2.5.0], which cannot be installed (as previously explained);
         ├─ icub-main [2.3.0|2.4.0|2.4.1|2.5.0], which cannot be installed (as previously explained);
         ├─ icub-main [2.3.0|2.4.0|2.4.1|2.5.0], which cannot be installed (as previously explained);
         ├─ icub-main [2.3.0|2.4.0|2.4.1|2.5.0], which cannot be installed (as previously explained);
         └─ icub-main 2.5.0 would require
            └─ libopencv >=4.9.0,<4.9.1.0a0 *, which requires
               └─ harfbuzz [>=8.3.0,<9.0a0 *|>=8.4.0,<9.0a0 *|>=8.5.0,<9.0a0 *], which requires
                  └─ icu >=73.2,<74.0a0 *, which conflicts with any installable versions previously reported.

probably we just need a new build of wb-toolbox to be compatible with the version of mamba and python installed by default in miniforge. However, either we start building against an older casadi, or we fix #1844 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants