-
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
Conda Package Generation failure Late November 2021 #927
Comments
For some reason, boa 0.5.0 gets installed instead of the latest one. |
I think this was just a problem that the latest boa was not compatible with the latest mamba, and so an old boa with the wrong mamba dependency constraint was pulled instead. xref mamba-org/boa#220 . |
Probably this was fixed by conda-forge/boa-feedstock#35 . |
The long term solution for this would be a repodata patch with a pr to https://github.com/conda-forge/conda-forge-repodata-patches-feedstock for fixing the dependency compatibility information for boa 0.5.0 . |
I launched a new conda package build in https://github.com/robotology/robotology-superbuild/actions/runs/1506648161, but I guess it will now work as for packages that depend on gazebo we may need to bump the cos version used from 6 to 7 due to the latest mesalib dependency, see #929 and conda-forge/conda-forge.github.io#1436 . |
That build worked successfully for mac and Windows, but it fails for Linux with error:
However, now we are back to the fact that an old boa version is installed because a new mamba minor release was released. |
I tried to add a workaround to the fact that boa 0.8 and mamba 0.19 get installed together, but installing 0.8 and 0.18 failed on Windows with error:
While using 0.7 and 0.17 worked fine. |
This was solved by #937 (fixing boa and mamba to known versions) but now we are back to the internal compiler error in gazebo-yarp-plugins:
I have to think a bit how to handle this. |
I tried to add a workaround in #937, let's hope it works. |
It does not. Let's try a more deterministic approach. I took the latest successful build, and let's see the difference in the build and host environment. Build env diff:
Host env diff:
The build env is almost identical, while a possible relevant difference is gazebo 11.8 vs 11.9 . We can try to pin Gazebo to 11.8 . |
Manually pinning gazebo to 11.8 avoid the problem, see: https://github.com/robotology/robotology-superbuild/runs/4411667208?check_suite_focus=true . |
Error:
Diff between latest working version:
The text was updated successfully, but these errors were encountered: