Install Ros1-Bridge on Foxy is Failing
Edit: text version of the error log:
root@7e18fbc1e12c:/# apt install ros-foxy-ros1-bridge
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
ros-foxy-ros1-bridge : Depends: ros-noetic-actionlib-msgs but it is not installable
Depends: ros-noetic-catkin but it is not installable
Depends: ros-noetic-common-msgs but it is not installable
Depends: ros-noetic-gazebo-msgs but it is not installable
Depends: ros-noetic-geometry-msgs but it is not installable
Depends: ros-noetic-nav-msgs but it is not installable
Depends: ros-noetic-rosbash but it is not installable
Depends: ros-noetic-roscpp but it is not installable
Depends: ros-noetic-roscpp-tutorials but it is not installable
Depends: ros-noetic-roslaunch but it is not installable
Depends: ros-noetic-rosmsg but it is not installable
Depends: ros-noetic-rospy-tutorials but it is not installable
Depends: ros-noetic-sensor-msgs but it is not installable
Depends: ros-noetic-std-msgs but it is not installable
Depends: ros-noetic-std-srvs but it is not installable
Depends: ros-noetic-stereo-msgs but it is not installable
Depends: ros-noetic-tf but it is not installable
Depends: ros-noetic-tf2-msgs but it is not installable
Depends: ros-noetic-trajectory-msgs but it is not installable
Depends: ros-noetic-visualization-msgs but it is not installable
E: Unable to correct problems, you have held broken packages.
In the future, mind posting the text instead of an image of text? Text is searchable, so it will help you and others find this same question again in the future.
Smart ! Will do next time.
@maxime: because there is already an answer here, I won't do it, but according to the support guidelines, we should've closed your question and you would've had to replace the screenshot with actual text.
My bad I faced the exact same issue when this was posted so I replied without looking at the question closely. @maxime I took the liberty of updating your question with the console output I had when I ran into the same issue