Install both conda-provided dependencies and ros noetic in conda result in dependency error

[traversaro]

Seamless installation of both ROS and robotology dependencies in the same environment is a key selling point of using conda-forge based packages. However, at the moment if one installs both ROS1 Noetic and robotology-superbuild dependencies, this result in an error, for example via:

mamba create -n HDE -c conda-forge -c robostack -c robostack-experimental python ros-noetic-desktop compilers cmake pkg-config make ninja colcon-common-extensions catkin_tools ace asio assimp boost eigen freetype gazebo glew glfw glm graphviz gsl ipopt irrlicht libjpeg-turbo libmatio libode libxml2 nlohmann_json opencv pkg-config portaudio sdl sdl2 sqlite tinyxml spdlog lua soxr qt-main

The problem that emerges is that we still did not have a rebuild of ROS Noetic with qt 5.15 (i.e. the only version for which qt-main exists). So, a possible solution is to remove qt-main from the list of installed packages, and you install qt instead (a package that exists for both qt 5.12 and 5.15), everything should work, even if you will get a slightly older version of qt:

mamba create -n HDE -c conda-forge -c robostack -c robostack-experimental python ros-noetic-desktop compilers cmake pkg-config make ninja colcon-common-extensions catkin_tools ace asio assimp boost eigen freetype gazebo glew glfw glm graphviz gsl ipopt irrlicht libjpeg-turbo libmatio libode libxml2 nlohmann_json opencv pkg-config portaudio sdl sdl2 sqlite tinyxml spdlog lua soxr qt

The problem is this is untested in CI. The proper fix for this problem is to do a global rebuild of ROS Noetic packages on the RoboStack/ros-noetic side.

[traversaro]

This is fixed by the new rebuild of ros-noetic packages that use qt-main and that are available in the robostack-staging channel: RoboStack/ros-noetic#295 .