-
Notifications
You must be signed in to change notification settings - Fork 48
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
Generate again conda package for walking-controllers and fix conda metapackages generation #1583
Conversation
|
robotology-distro-all generation still fails:
|
Trying to solve the env:
locally I have a more clear error:
In a nutshell, for sure we need to bump at least cppad |
Fixing cppad and removing walking-controllers, we still have errors:
the problems goes away removing the proxsuite pin, so probably it is just a missing rebuilt of casadi with the latest proxsuite. |
Actually it is again a problem on our side, proxsuite should be updated to 0.6.1 . |
But the latest is actually proxsuite 0.6.3, so I also asked for a rebuild on casadi side: conda-forge/casadi-feedstock#100) |
While indeed the lagging behind of proxsuite and cppad could be a bit a problem in robotology-superbuild and a bit a lack of pinning for these two libraries in conda-forge-pinning, in general we do not care too much about the version of these libraries, even if they are tracked in latest.releases.yaml . Probably we could consider to just avoid adding them to the version listed in robotology-distro and robotology-distro-all . |
new test build: https://github.com/robotology/robotology-superbuild/actions/runs/7695901115 . |
Build successful, let's merge. |
Fix #1577 .
In a rush to actually generate conda packages and fix #1572, we disabled walking-controllers generation, as it was failing on Linux. However, the generation was failing as the latest bipedal-locomotion-framework was compiled against ipopt 3.14.14, while icub-main was still building with 3.14.13 . This was happening as:
robotology-superbuild/.github/workflows/generate-conda-packages.yaml
Line 179 in d5c49b8
We fixed this in #1578 by manually pinning ipopt to 3.14.14 in the robotology conda packages generation CI. This can be removed once ipopt 3.14.14 abi migration is completed at the conda-forge level.
To understand how to avoid this in the future:
cc @GiulioRomualdi