Can't install latest version of YARP with robostack humble packages

[traversaro]

Solution to issue cannot be found in the documentation.

• I checked the documentation.

Issue

The issue is probably related to missing migrations not propagated on the robostack side.

Installed packages

.

Environment info

.

[traversaro]

cc @Nicogene

[Nicogene]

Alongside @martinaxgloria we tried to do:

mamba install -c conda-forge yarp=3.8.1 ros-humble-desktop ros-humble-moveit ros-humble-test-msgs

and we got this error

The following packages are incompatible
├─ ros-humble-desktop   is uninstallable because there are no viable options
│  ├─ ros-humble-desktop 0.10.0 would require
│  │  ├─ ros-humble-demo-nodes-cpp-native   with the potential options
│  │  │  ├─ ros-humble-demo-nodes-cpp-native 0.20.2 would require
│  │  │  │  └─ ros-humble-rmw-fastrtps-cpp   with the potential options
│  │  │  │     ├─ ros-humble-rmw-fastrtps-cpp 6.2.2 would require
│  │  │  │     │  └─ ros2-distro-mutex 0.3.* , which requires
│  │  │  │     │     └─ boost-cpp 1.78.* , which can be installed;
│  │  │  │     └─ ros-humble-rmw-fastrtps-cpp 6.2.2 would require
│  │  │  │        └─ ros-humble-fastrtps   with the potential options
│  │  │  │           ├─ ros-humble-fastrtps 2.6.4 would require
│  │  │  │           │  └─ ros2-distro-mutex 0.3.* , which can be installed (as previously explained);
│  │  │  │           └─ ros-humble-fastrtps 2.6.3 would require
│  │  │  │              └─ openssl >=1.1.1s,<1.1.2a , which can be installed;
│  │  │  └─ ros-humble-demo-nodes-cpp-native 0.20.3 would require
│  │  │     └─ ros2-distro-mutex 0.3.* , which can be installed (as previously explained);
│  │  ├─ ros-humble-image-tools   with the potential options
│  │  │  ├─ ros-humble-image-tools 0.20.2 would require
│  │  │  │  └─ libopencv >=4.6.0,<4.6.1.0a0  with the potential options
│  │  │  │     ├─ libopencv 4.6.0 would require
│  │  │  │     │  └─ harfbuzz [>=4.4.1,<5.0a0 |>=5.0.1,<6.0a0 |>=5.1.0,<6.0a0 |>=5.3.0,<6.0a0 ], which requires
│  │  │  │     │     └─ icu >=70.1,<71.0a0 , which can be installed;
│  │  │  │     └─ libopencv 4.6.0 would require
│  │  │  │        └─ harfbuzz >=6.0.0,<7.0a0  with the potential options
│  │  │  │           ├─ harfbuzz 6.0.0, which can be installed;
│  │  │  │           └─ harfbuzz [4.4.1|5.0.1|...|6.0.0], which can be installed (as previously explained);
│  │  │  └─ ros-humble-image-tools 0.20.3 would require
│  │  │     └─ ros2-distro-mutex 0.3.* , which can be installed (as previously explained);
│  │  ├─ ros-humble-quality-of-service-demo-py   with the potential options
│  │  │  ├─ ros-humble-quality-of-service-demo-py 0.20.2 would require
│  │  │  │  └─ ros-humble-rclpy   with the potential options
│  │  │  │     ├─ ros-humble-rclpy 3.3.5 would require
│  │  │  │     │  └─ ros-humble-rmw-implementation   with the potential options
│  │  │  │     │     ├─ ros-humble-rmw-implementation 2.8.1 would require
│  │  │  │     │     │  └─ ros-humble-rmw-cyclonedds-cpp   with the potential options
│  │  │  │     │     │     ├─ ros-humble-rmw-cyclonedds-cpp 1.3.4 would require
│  │  │  │     │     │     │  └─ ros-humble-cyclonedds   with the potential options
│  │  │  │     │     │     │     ├─ ros-humble-cyclonedds 0.9.1 would require
│  │  │  │     │     │     │     │  └─ openssl >=1.1.1s,<1.1.2a , which can be installed;
│  │  │  │     │     │     │     └─ ros-humble-cyclonedds 0.9.1 would require
│  │  │  │     │     │     │        └─ ros2-distro-mutex 0.3.* , which can be installed (as previously explained);
│  │  │  │     │     │     └─ ros-humble-rmw-cyclonedds-cpp 1.3.4 would require
│  │  │  │     │     │        └─ ros2-distro-mutex 0.3.* , which can be installed (as previously explained);
│  │  │  │     │     └─ ros-humble-rmw-implementation 2.8.2 would require
│  │  │  │     │        └─ ros2-distro-mutex 0.3.* , which can be installed (as previously explained);
│  │  │  │     └─ ros-humble-rclpy 3.3.7 would require
│  │  │  │        └─ ros2-distro-mutex 0.3.* , which can be installed (as previously explained);
│  │  │  └─ ros-humble-quality-of-service-demo-py 0.20.3 would require
│  │  │     └─ ros2-distro-mutex 0.3.* , which can be installed (as previously explained);
│  │  ├─ ros-humble-rviz-default-plugins  , which requires
│  │  │  ├─ ros-humble-resource-retriever  , which requires
│  │  │  │  ├─ ros-humble-libcurl-vendor   with the potential options
│  │  │  │  │  ├─ ros-humble-libcurl-vendor 3.1.0 would require
│  │  │  │  │  │  ├─ libcurl >=7.86.0,<8.0a0  with the potential options
│  │  │  │  │  │  │  ├─ libcurl 7.86.0 would require
│  │  │  │  │  │  │  │  └─ krb5 >=1.19.3,<1.20.0a0 , which can be installed;
│  │  │  │  │  │  │  └─ libcurl [7.86.0|7.87.0|7.88.0|7.88.1] would require
│  │  │  │  │  │  │     ├─ krb5 >=1.20.1,<1.21.0a0  with the potential options
│  │  │  │  │  │  │     │  ├─ krb5 1.20.1, which can be installed;
│  │  │  │  │  │  │     │  └─ krb5 1.20.1 would require
│  │  │  │  │  │  │     │     └─ openssl >=1.1.1s,<1.1.2a , which can be installed;
│  │  │  │  │  │  │     └─ openssl >=1.1.1s,<1.1.2a , which can be installed;
│  │  │  │  │  │  └─ ros2-distro-mutex 0.2.* , which conflicts with any installable versions previously reported;
│  │  │  │  │  └─ ros-humble-libcurl-vendor 3.1.1 would require
│  │  │  │  │     ├─ libcurl >=7.87.0,<8.0a0 , which can be installed (as previously explained);
│  │  │  │  │     └─ ros2-distro-mutex 0.3.* , which can be installed (as previously explained);
│  │  │  │  └─ ros2-distro-mutex [0.2.* |0.3.* ] with the potential options
│  │  │  │     ├─ ros2-distro-mutex 0.3.0, which can be installed (as previously explained);
│  │  │  │     └─ ros2-distro-mutex 0.2.0 conflicts with any installable versions previously reported;
│  │  │  └─ ros2-distro-mutex [0.2.* humble|0.3.* ] with the potential options
│  │  │     ├─ ros2-distro-mutex 0.3.0, which can be installed (as previously explained);
│  │  │     └─ ros2-distro-mutex 0.2.0 conflicts with any installable versions previously reported;
│  │  ├─ ros-humble-turtlesim   with the potential options
│  │  │  ├─ ros-humble-turtlesim 1.4.2 would require
│  │  │  │  └─ qt-main >=5.15.6,<5.16.0a0  with the potential options
│  │  │  │     ├─ qt-main 5.15.6 would require
│  │  │  │     │  ├─ icu >=70.1,<71.0a0 , which can be installed;
│  │  │  │     │  └─ libxcb >=1.13,<1.14.0a0 , which can be installed;
│  │  │  │     ├─ qt-main 5.15.8 would require
│  │  │  │     │  ├─ harfbuzz >=7.3.0,<8.0a0  but there are no viable options
│  │  │  │     │  │  ├─ harfbuzz [7.3.0|8.1.1|8.2.0|8.2.1] would require
│  │  │  │     │  │  │  └─ icu >=73.2,<74.0a0 , which conflicts with any installable versions previously reported;
│  │  │  │     │  │  └─ harfbuzz 7.3.0 conflicts with any installable versions previously reported;
│  │  │  │     │  ├─ icu >=72.1,<73.0a0 , which conflicts with any installable versions previously reported;
│  │  │  │     │  ├─ libxcb >=1.15,<1.16.0a0 , which conflicts with any installable versions previously reported;
│  │  │  │     │  └─ libxml2 >=2.11.4,<2.12.0a0  but there are no viable options
│  │  │  │     │     ├─ libxml2 [2.11.3|2.11.4|2.11.5] would require
│  │  │  │     │     │  └─ icu >=72.1,<73.0a0 , which conflicts with any installable versions previously reported;
│  │  │  │     │     └─ libxml2 2.11.5 would require
│  │  │  │     │        └─ icu >=73.2,<74.0a0 , which conflicts with any installable versions previously reported;
│  │  │  │     ├─ qt-main 5.15.8 would require
│  │  │  │     │  ├─ harfbuzz >=6.0.0,<7.0a0  with the potential options
│  │  │  │     │  │  ├─ harfbuzz 6.0.0, which can be installed;
│  │  │  │     │  │  └─ harfbuzz [4.4.1|5.0.1|...|6.0.0], which can be installed (as previously explained);
│  │  │  │     │  ├─ icu >=72.1,<73.0a0 , which conflicts with any installable versions previously reported;
│  │  │  │     │  ├─ libxcb >=1.13,<1.14.0a0 , which can be installed;
│  │  │  │     │  └─ libxml2 >=2.10.4,<2.11.0a0 , which requires
│  │  │  │     │     └─ icu >=72.1,<73.0a0 , which conflicts with any installable versions previously reported;
│  │  │  │     ├─ qt-main 5.15.8 would require
│  │  │  │     │  ├─ harfbuzz >=6.0.0,<7.0a0  with the potential options
│  │  │  │     │  │  ├─ harfbuzz 6.0.0, which can be installed;
│  │  │  │     │  │  └─ harfbuzz [4.4.1|5.0.1|...|6.0.0], which can be installed (as previously explained);
│  │  │  │     │  ├─ icu >=72.1,<73.0a0 , which conflicts with any installable versions previously reported;
│  │  │  │     │  ├─ libxcb >=1.13,<1.14.0a0 , which can be installed;
│  │  │  │     │  └─ libxml2 >=2.10.3,<2.11.0a0  but there are no viable options
│  │  │  │     │     ├─ libxml2 2.10.4, which cannot be installed (as previously explained);
│  │  │  │     │     └─ libxml2 2.10.3 conflicts with any installable versions previously reported;
│  │  │  │     ├─ qt-main 5.15.8 would require
│  │  │  │     │  ├─ icu >=70.1,<71.0a0 , which can be installed;
│  │  │  │     │  ├─ libxcb >=1.13,<1.14.0a0 , which can be installed;
│  │  │  │     │  └─ libxml2 >=2.10.3,<2.11.0a0  but there are no viable options
│  │  │  │     │     ├─ libxml2 2.10.4, which cannot be installed (as previously explained);
│  │  │  │     │     └─ libxml2 2.10.3 conflicts with any installable versions previously reported;
│  │  │  │     ├─ qt-main 5.15.8 would require
│  │  │  │     │  └─ krb5 >=1.21.1,<1.22.0a0  but there are no viable options
│  │  │  │     │     ├─ krb5 1.21.1 conflicts with any installable versions previously reported;
│  │  │  │     │     └─ krb5 1.21.2 would require
│  │  │  │     │        └─ openssl >=3.1.2,<4.0a0 , which conflicts with any installable versions previously reported;
│  │  │  │     ├─ qt-main 5.15.8 would require
│  │  │  │     │  ├─ harfbuzz >=7.3.0,<8.0a0  but there are no viable options
│  │  │  │     │  │  ├─ harfbuzz [7.3.0|8.1.1|8.2.0|8.2.1], which cannot be installed (as previously explained);
│  │  │  │     │  │  └─ harfbuzz 7.3.0 conflicts with any installable versions previously reported;
│  │  │  │     │  ├─ icu >=72.1,<73.0a0 , which conflicts with any installable versions previously reported;
│  │  │  │     │  └─ libxcb >=1.13,<1.14.0a0 , which can be installed;
│  │  │  │     ├─ qt-main 5.15.8 would require
│  │  │  │     │  ├─ krb5 >=1.21.2,<1.22.0a0 , which cannot be installed (as previously explained);
│  │  │  │     │  └─ openssl >=3.1.2,<4.0a0 , which conflicts with any installable versions previously reported;
│  │  │  │     └─ qt-main 5.15.8 would require
│  │  │  │        ├─ harfbuzz >=7.3.0,<8.0a0  but there are no viable options
│  │  │  │        │  ├─ harfbuzz [7.3.0|8.1.1|8.2.0|8.2.1], which cannot be installed (as previously explained);
│  │  │  │        │  └─ harfbuzz 7.3.0 conflicts with any installable versions previously reported;
│  │  │  │        └─ icu >=72.1,<73.0a0 , which conflicts with any installable versions previously reported;
│  │  │  └─ ros-humble-turtlesim 1.4.2 would require
│  │  │     └─ ros2-distro-mutex 0.3.* , which can be installed (as previously explained);
│  │  └─ ros2-distro-mutex 0.2.* humble, which conflicts with any installable versions previously reported;
│  └─ ros-humble-desktop 0.10.0 would require
│     ├─ ros-humble-depthimage-to-laserscan   with the potential options
│     │  ├─ ros-humble-depthimage-to-laserscan 2.5.0 would require
│     │  │  └─ libopencv >=4.6.0,<4.6.1.0a0 , which can be installed (as previously explained);
│     │  └─ ros-humble-depthimage-to-laserscan 2.5.0 would require
│     │     └─ ros2-distro-mutex 0.2.* , which conflicts with any installable versions previously reported;
│     ├─ ros-humble-pcl-conversions   with the potential options
│     │  ├─ ros-humble-pcl-conversions 2.4.0 would require
│     │  │  └─ pcl >=1.12.1,<1.12.2.0a0  with the potential options
│     │  │     ├─ pcl 1.12.1 would require
│     │  │     │  └─ vtk >=9.1.0,<9.1.1.0a0  with the potential options
│     │  │     │     ├─ vtk [9.1.0|9.2.2] would require
│     │  │     │     │  └─ libxml2 >=2.9.14,<2.11.0a0  but there are no viable options
│     │  │     │     │     ├─ libxml2 2.10.4, which cannot be installed (as previously explained);
│     │  │     │     │     ├─ libxml2 2.10.3 conflicts with any installable versions previously reported;
│     │  │     │     │     ├─ libxml2 [2.10.0|2.10.1|2.10.2] conflicts with any installable versions previously reported;
│     │  │     │     │     └─ libxml2 2.9.14 conflicts with any installable versions previously reported;
│     │  │     │     ├─ vtk [9.1.0|9.2.2] would require
│     │  │     │     │  └─ python_abi 3.7.* *_cp37m, which can be installed;
│     │  │     │     ├─ vtk [9.1.0|9.2.2] would require
│     │  │     │     │  └─ python_abi 3.8.* *_cp38, which can be installed;
│     │  │     │     ├─ vtk [9.1.0|9.2.2] would require
│     │  │     │     │  └─ python_abi 3.9.* *_cp39, which can be installed;
│     │  │     │     └─ vtk 9.1.0 would require
│     │  │     │        └─ libxml2 >=2.9.12,<2.11.0a0  but there are no viable options
│     │  │     │           ├─ libxml2 2.10.4, which cannot be installed (as previously explained);
│     │  │     │           ├─ libxml2 2.10.3 conflicts with any installable versions previously reported;
│     │  │     │           ├─ libxml2 [2.10.0|2.10.1|2.10.2] conflicts with any installable versions previously reported;
│     │  │     │           ├─ libxml2 [2.9.12|2.9.13] conflicts with any installable versions previously reported;
│     │  │     │           └─ libxml2 2.9.14 conflicts with any installable versions previously reported;
│     │  │     ├─ pcl 1.12.1 would require
│     │  │     │  └─ boost-cpp >=1.74.0,<1.74.1.0a0 , which conflicts with any installable versions previously reported;
│     │  │     └─ pcl 1.12.1 would require
│     │  │        └─ vtk >=9.2.2,<9.2.3.0a0  with the potential options
│     │  │           ├─ vtk [9.1.0|9.2.2], which cannot be installed (as previously explained);
│     │  │           ├─ vtk 9.2.2 would require
│     │  │           │  └─ libxml2 >=2.9.14,<2.10.0a0 , which conflicts with any installable versions previously reported;
│     │  │           ├─ vtk 9.2.2 would require
│     │  │           │  └─ libxml2 >=2.10.3,<2.11.0a0  but there are no viable options
│     │  │           │     ├─ libxml2 2.10.4, which cannot be installed (as previously explained);
│     │  │           │     └─ libxml2 2.10.3 conflicts with any installable versions previously reported;
│     │  │           ├─ vtk 9.2.2 would require
│     │  │           │  └─ python_abi 3.11.* *_cp311, which can be installed;
│     │  │           ├─ vtk [9.1.0|9.2.2], which can be installed (as previously explained);
│     │  │           ├─ vtk [9.1.0|9.2.2], which can be installed (as previously explained);
│     │  │           └─ vtk [9.1.0|9.2.2], which can be installed (as previously explained);
│     │  └─ ros-humble-pcl-conversions 2.4.0 would require
│     │     └─ ros2-distro-mutex 0.2.* , which conflicts with any installable versions previously reported;
│     ├─ ros-humble-ros-base   but there are no viable options
│     │  ├─ ros-humble-ros-base 0.10.0 would require
│     │  │  └─ ros-humble-ros-core   but there are no viable options
│     │  │     ├─ ros-humble-ros-core 0.10.0 would require
│     │  │     │  └─ ros-humble-ament-lint-common   but there are no viable options
│     │  │     │     ├─ ros-humble-ament-lint-common 0.12.5 would require
│     │  │     │     │  └─ ros-humble-ament-cmake-uncrustify   but there are no viable options
│     │  │     │     │     ├─ ros-humble-ament-cmake-uncrustify 0.12.5 would require
│     │  │     │     │     │  └─ ros-humble-ament-uncrustify   but there are no viable options
│     │  │     │     │     │     ├─ ros-humble-ament-uncrustify 0.12.5 would require
│     │  │     │     │     │     │  └─ ros-humble-uncrustify-vendor   but there are no viable options
│     │  │     │     │     │     │     ├─ ros-humble-uncrustify-vendor 2.0.2 would require
│     │  │     │     │     │     │     │  └─ python_abi 3.10.* *_cp310, which conflicts with any installable versions previously reported;
│     │  │     │     │     │     │     └─ ros-humble-uncrustify-vendor 2.0.2 would require
│     │  │     │     │     │     │        └─ ros2-distro-mutex 0.2.* , which conflicts with any installable versions previously reported;
│     │  │     │     │     │     └─ ros-humble-ament-uncrustify 0.12.4 would require
│     │  │     │     │     │        └─ ros2-distro-mutex 0.2.* , which conflicts with any installable versions previously reported;
│     │  │     │     │     └─ ros-humble-ament-cmake-uncrustify 0.12.4 would require
│     │  │     │     │        └─ ros2-distro-mutex 0.2.* , which conflicts with any installable versions previously reported;
│     │  │     │     └─ ros-humble-ament-lint-common 0.12.4 would require
│     │  │     │        └─ ros2-distro-mutex 0.2.* , which conflicts with any installable versions previously reported;
│     │  │     └─ ros-humble-ros-core 0.10.0 would require
│     │  │        └─ ros2-distro-mutex 0.2.* humble, which conflicts with any installable versions previously reported;
│     │  └─ ros-humble-ros-base 0.10.0 would require
│     │     └─ ros2-distro-mutex 0.2.* humble, which conflicts with any installable versions previously reported;
│     ├─ ros-humble-rqt-common-plugins   with the potential options
│     │  ├─ ros-humble-rqt-common-plugins 1.2.0 would require
│     │  │  └─ ros-humble-rqt-image-view   with the potential options
│     │  │     ├─ ros-humble-rqt-image-view 1.2.0 would require
│     │  │     │  └─ ros-humble-cv-bridge   with the potential options
│     │  │     │     ├─ ros-humble-cv-bridge 3.2.1 would require
│     │  │     │     │  └─ libopencv >=4.6.0,<4.6.1.0a0 , which can be installed (as previously explained);
│     │  │     │     └─ ros-humble-cv-bridge 3.2.1 would require
│     │  │     │        └─ ros2-distro-mutex 0.2.* , which conflicts with any installable versions previously reported;
│     │  │     └─ ros-humble-rqt-image-view 1.2.0 would require
│     │  │        └─ ros2-distro-mutex 0.2.* , which conflicts with any installable versions previously reported;
│     │  └─ ros-humble-rqt-common-plugins 1.2.0 would require
│     │     └─ ros2-distro-mutex 0.2.* humble, which conflicts with any installable versions previously reported;
│     ├─ ros-humble-rviz-default-plugins  , which can be installed (as previously explained);
│     ├─ ros-humble-rviz2   with the potential options
│     │  ├─ ros-humble-rviz2 11.2.5 would require
│     │  │  ├─ qt-main >=5.15.6,<5.16.0a0  with the potential options
│     │  │  │  ├─ qt-main 5.15.6, which can be installed (as previously explained);
│     │  │  │  ├─ qt-main 5.15.8, which cannot be installed (as previously explained);
│     │  │  │  ├─ qt-main 5.15.8, which cannot be installed (as previously explained);
│     │  │  │  ├─ qt-main 5.15.8, which cannot be installed (as previously explained);
│     │  │  │  ├─ qt-main 5.15.8, which cannot be installed (as previously explained);
│     │  │  │  ├─ qt-main 5.15.8, which cannot be installed (as previously explained);
│     │  │  │  ├─ qt-main 5.15.8, which cannot be installed (as previously explained);
│     │  │  │  ├─ qt-main 5.15.8, which cannot be installed (as previously explained);
│     │  │  │  └─ qt-main 5.15.8, which cannot be installed (as previously explained);
│     │  │  └─ ros-humble-rviz-ogre-vendor   with the potential options
│     │  │     ├─ ros-humble-rviz-ogre-vendor 11.2.5 would require
│     │  │     │  └─ pugixml >=1.11.4,<1.12.0a0 , which can be installed;
│     │  │     └─ ros-humble-rviz-ogre-vendor 11.2.4 would require
│     │  │        └─ ros2-distro-mutex 0.2.* , which conflicts with any installable versions previously reported;
│     │  └─ ros-humble-rviz2 11.2.4 would require
│     │     └─ ros2-distro-mutex 0.2.* humble, which conflicts with any installable versions previously reported;
│     └─ ros2-distro-mutex 0.3.* , which can be installed (as previously explained);
├─ ros-humble-moveit   is installable with the potential options
│  ├─ ros-humble-moveit 2.5.4 would require
│  │  └─ ros-humble-moveit-ros   with the potential options
│  │     ├─ ros-humble-moveit-ros 2.5.4 would require
│  │     │  └─ ros-humble-moveit-ros-visualization   with the potential options
│  │     │     ├─ ros-humble-moveit-ros-visualization 2.5.4 would require
│  │     │     │  └─ qt-main >=5.15.6,<5.16.0a0  with the potential options
│  │     │     │     ├─ qt-main 5.15.6, which can be installed (as previously explained);
│  │     │     │     ├─ qt-main 5.15.8, which cannot be installed (as previously explained);
│  │     │     │     ├─ qt-main 5.15.8, which cannot be installed (as previously explained);
│  │     │     │     ├─ qt-main 5.15.8, which cannot be installed (as previously explained);
│  │     │     │     ├─ qt-main 5.15.8, which cannot be installed (as previously explained);
│  │     │     │     ├─ qt-main 5.15.8, which cannot be installed (as previously explained);
│  │     │     │     ├─ qt-main 5.15.8, which cannot be installed (as previously explained);
│  │     │     │     ├─ qt-main 5.15.8, which cannot be installed (as previously explained);
│  │     │     │     └─ qt-main 5.15.8, which cannot be installed (as previously explained);
│  │     │     └─ ros-humble-moveit-ros-visualization 2.5.4 would require
│  │     │        └─ ros2-distro-mutex 0.2.* humble, which conflicts with any installable versions previously reported;
│  │     └─ ros-humble-moveit-ros 2.5.4 would require
│  │        └─ ros2-distro-mutex 0.2.* humble, which conflicts with any installable versions previously reported;
│  └─ ros-humble-moveit 2.5.4 would require
│     └─ ros2-distro-mutex 0.2.* humble, which conflicts with any installable versions previously reported;
└─ yarp 3.8.1**  is uninstallable because there are no viable options
   ├─ yarp 3.8.1 would require
   │  └─ yarp-cxx [3.8.1 h245b40a_0|3.8.1 h245b40a_1|3.8.1 h245b40a_2|3.8.1 h245b40a_3], which requires
   │     ├─ ffmpeg >=6.0.0,<7.0a0  but there are no viable options
   │     │  ├─ ffmpeg 6.0.0 would require
   │     │  │  └─ libva [>=2.19.0,<3.0a0 |>=2.20.0,<3.0a0 ], which requires
   │     │  │     └─ xorg-libx11 >=1.8.6,<2.0a0 , which requires
   │     │  │        └─ libxcb >=1.15,<1.16.0a0 , which conflicts with any installable versions previously reported;
   │     │  ├─ ffmpeg 6.0.0 would require
   │     │  │  ├─ libass >=0.17.1,<0.17.2.0a0  but there are no viable options
   │     │  │  │  ├─ libass 0.17.1 would require
   │     │  │  │  │  └─ harfbuzz >=8.1.1,<9.0a0 , which cannot be installed (as previously explained);
   │     │  │  │  └─ libass 0.17.1 would require
   │     │  │  │     └─ harfbuzz >=7.2.0,<8.0a0  but there are no viable options
   │     │  │  │        ├─ harfbuzz 7.2.0 conflicts with any installable versions previously reported;
   │     │  │  │        ├─ harfbuzz [7.3.0|8.1.1|8.2.0|8.2.1], which cannot be installed (as previously explained);
   │     │  │  │        └─ harfbuzz 7.3.0 conflicts with any installable versions previously reported;
   │     │  │  └─ libxml2 [>=2.10.4,<2.11.0a0 |>=2.11.4,<2.12.0a0 ], which cannot be installed (as previously explained);
   │     │  └─ ffmpeg 6.0.0 would require
   │     │     ├─ libass >=0.17.1,<0.17.2.0a0 , which cannot be installed (as previously explained);
   │     │     └─ libxml2 >=2.11.3,<2.12.0a0  with the potential options
   │     │        ├─ libxml2 [2.11.3|2.11.4|2.11.5], which cannot be installed (as previously explained);
   │     │        ├─ libxml2 2.11.3, which can be installed;
   │     │        └─ libxml2 2.11.5, which cannot be installed (as previously explained);
   │     └─ qt-main >=5.15.8,<5.16.0a0 , which cannot be installed (as previously explained);
   └─ yarp 3.8.1 would require
      ├─ yarp-cxx [3.8.1 h264dbdb_4|3.8.1 hc95d4b6_5] but there are no viable options
      │  ├─ yarp-cxx 3.8.1 would require
      │  │  └─ libopencv >=4.8.0,<4.8.1.0a0  but there are no viable options
      │  │     ├─ libopencv 4.8.0 would require
      │  │     │  └─ libopenvino-ir-frontend >=2023.0.1,<2023.0.2.0a0 , which requires
      │  │     │     └─ pugixml >=1.13,<1.14.0a0 , which conflicts with any installable versions previously reported;
      │  │     ├─ libopencv [4.8.0|4.8.1] would require
      │  │     │  └─ hdf5 >=1.14.2,<1.14.3.0a0 , which requires
      │  │     │     └─ libcurl >=8.2.1,<9.0a0  but there are no viable options
      │  │     │        ├─ libcurl 8.2.1 would require
      │  │     │        │  └─ krb5 >=1.21.1,<1.22.0a0  but there are no viable options
      │  │     │        │     ├─ krb5 1.21.1 conflicts with any installable versions previously reported;
      │  │     │        │     └─ krb5 1.21.2, which cannot be installed (as previously explained);
      │  │     │        └─ libcurl 8.3.0 conflicts with any installable versions previously reported;
      │  │     └─ libopencv 4.8.0 conflicts with any installable versions previously reported;
      │  └─ yarp-cxx 3.8.1 would require
      │     └─ libopencv >=4.8.1,<4.8.2.0a0  but there are no viable options
      │        ├─ libopencv [4.8.0|4.8.1], which cannot be installed (as previously explained);
      │        └─ libopencv 4.8.1 conflicts with any installable versions previously reported;
      └─ yarp-python >=3.8.1,<3.8.2.0a0  but there are no viable options
         ├─ yarp-python 3.8.1 would require
         │  └─ yarp-cxx [3.8.1 h245b40a_0|3.8.1 h245b40a_1|3.8.1 h245b40a_2|3.8.1 h245b40a_3], which cannot be installed (as previously explained);
         ├─ yarp-python 3.8.1 would require
         │  ├─ openssl >=3.1.2,<4.0a0 , which conflicts with any installable versions previously reported;
         │  └─ yarp-cxx 3.8.1 h264dbdb_4, which cannot be installed (as previously explained);
         └─ yarp-python 3.8.1 would require
            ├─ openssl >=3.1.3,<4.0a0 , which conflicts with any installable versions previously reported;
            └─ yarp-cxx 3.8.1 hc95d4b6_5, which cannot be installed (as previously explained).

[traversaro]

Just to clarify, this issue is similar to:

• Install both conda-provided dependencies and ros noetic in conda result in dependency error  robotology/robotology-superbuild#1230
• Fail to load gazebo ros plugins due to undefined symbol RoboStack/ros-noetic#415

Basically, what happens is that in conda-forge there are ABI migration (https://conda-forge.org/blog/posts/2019-12-06-cfep09/) to automatically migrate all packages in conda-forge to a new version of a dependency. RoboStack packages are not included in this migrations, so it can happen that it uses oldr version of dependencies w.r.t. to the packages in conda-forge, i.e. forcing to use older packages in conda-forge that are compatible with the older version of its dependencies.

The immediate workaround is to compile YARP from source, it should be simple to do that (check

yarp-feedstock/recipe/build_cxx.sh

Line 29 in af3c941

cmake ${CMAKE_ARGS} -GNinja .. \

for the exact options used to build the conda package).

On the robostack side, this is tipically solved by a rebuild.

Possible longer term solutions are:

• Split yarp in different packages, possible putting in different packages the plugin that depends on opencv and the tools that depend on qt-main (that I guess are the most problematic dependencies)
• Build yarp also with robostack version of dependencies
• Implement migrations or something similar also on the robostack side.

[traversaro]

This will be fixed by RoboStack/ros-humble#155 .

[traversaro]

This will be fixed by RoboStack/ros-humble#155 .

Unfortunately this in the end required a conda-build fix conda/conda-build#5202, so it may take some time.