Catkin installation fails in CI Docker

Packaging and Release Management Melodic
1

Has anyone seen recently build failures in melodic CI?

Excerpt from step “11. Build Dockerfile - build and install”:

Summary 
**19:38:56** Invoking 'apt-get install -q -y -o Debug::pkgProblemResolver=yes build-essential python3 ros-melodic-catkin ros-melodic-pluginlib ros-melodic-rosconsole ros-melodic-roscpp ros-melodic-roslib ros-melodic-rostest'
**19:38:56** Reading package lists... 
**19:38:57** Building dependency tree... 
**19:38:57** Reading state information... 
**19:38:57** Starting pkgProblemResolver with broken count: 5 
**19:38:57** Starting 2 pkgProblemResolver with broken count: 5 
**19:38:57** Investigating (0) ros-melodic-catkin:amd64 < none -> 0.7.26-1bionic.20200529.204155 @un puN Ib > 
**19:38:57** Broken ros-melodic-catkin:amd64 Depends on python-catkin-pkg:amd64 < none | 0.4.21-100 @un uH > (> 0.4.3) 
**19:38:57** Considering python-catkin-pkg:amd64 1 as a solution to ros-melodic-catkin:amd64 10010 
**19:38:57** Re-Instated tzdata:amd64 
**19:38:57** Re-Instated python-dateutil:amd64 
**19:38:57** Re-Instated sgml-base:amd64 
**19:38:57** Re-Instated xml-core:amd64 
**19:38:57** Re-Instated docutils-common:amd64 
**19:38:57** Re-Instated python-roman:amd64 
**19:38:57** Re-Instated python-docutils:amd64 
**19:38:57** Re-Instated python-pyparsing:amd64 
**19:38:57** Reinst Failed early because of python2:amd64
2

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
3

I was just about to post on the other thread. It was a very similar issue and is resolved by catkin-pkg 0.4.22 which has been imported by the build farms and should be uploading to packages.ros.org shortly.

4

Apologies for repeating myself then, but would there be any way to test for this?

Are there any other packages which could be affected by the same problem?

5

I made a reply in Build/CI failures with ros-testing repository enabled? which I think has more context. I’m not sure what the etiquette is on combining the two threads or discontinuing this one.

1 Like
6

Thanks, it seems to be solved now :wink: