I just started noticing these as well.
Seemingly unrelated to whatever the CI was supposed to test.
I’m wondering whether it is something to Build/CI failures with ros-testing repository enabled?.
@nuclearsandwich is something up with Catkin this time?
Example failure:
Invoking 'apt-get install -q -y -o Debug::pkgProblemResolver=yes build-essential python3 ros-melodic-catkin libboost-all-dev ros-melodic-geometry-msgs ros-melodic-joint-state-publisher-gui ros-melodic-message-generation ros-melodic-moveit-core ros-melodic-moveit-kinematics ros-melodic-moveit-ros-planning ros-melodic-pluginlib ros-melodic-robot-state-publisher ros-melodic-roscpp ros-melodic-rviz ros-melodic-std-msgs ros-melodic-tf-conversions ros-melodic-urdf ros-melodic-xacro'
Reading package lists...
Building dependency tree...
Reading state information...
Starting pkgProblemResolver with broken count: 5
Starting 2 pkgProblemResolver with broken count: 5
Investigating (0) ros-melodic-catkin:amd64 < none -> 0.7.26-1bionic.20200529.204155 @un puN Ib >
Broken ros-melodic-catkin:amd64 Depends on python-catkin-pkg:amd64 < none | 0.4.21-100 @un uH > (> 0.4.3)
Considering python-catkin-pkg:amd64 1 as a solution to ros-melodic-catkin:amd64 10038
Re-Instated tzdata:amd64
Re-Instated python-dateutil:amd64
Re-Instated sgml-base:amd64
Re-Instated xml-core:amd64
Re-Instated docutils-common:amd64
Re-Instated python-roman:amd64
Re-Instated python-docutils:amd64
Re-Instated python-pyparsing:amd64
Reinst Failed early because of python2:amd64