I’m not entirely sure this already ‘deserves’ a post here, but I’m seeing increased build failures (and CI failures) for builds which use the
ros-testing repository. Regular builds (ie: using the main
ros repository) succeed.
Example of buildfarm build which failed: Kbin_uX64__abb_driver__ubuntu_xenial_amd64__binary. Test PR with Travis CI build which fails when
ros-testing repository is enabled: ros-industrial/ur_msgs#3.
In both cases errors about “broken packages” are reported. From the buildfarm build (log):
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-kinetic-industrial-robot-client : Depends: ros-kinetic-actionlib but it is not going to be installed Depends: ros-kinetic-industrial-utils but it is not going to be installed Depends: ros-kinetic-robot-state-publisher but it is not going to be installed Depends: ros-kinetic-urdf but it is not going to be installed E: Unable to correct problems, you have held broken packages.
I don’t know whether there are any other builds failing on the buildfarm, as I can’t get any tabs other than the manage tab to load.
Other builds with similar failures:
swarmros failure log seems to point to something having to do with Python 2 and
35 'Broken ros-kinetic-roslib:amd64 Depends on ros-kinetic-rospack [ amd64 ] < none -> 2.4.5-1xenial-20191214-014035+0000 > ( misc )' 02:16:20 36 ' Considering ros-kinetic-rospack:amd64 -1 as a solution to ros-kinetic-roslib:amd64 9998' 02:16:20 37 ' Reinst Failed early because of python2:amd64' 02:16:20 38 ' Reinst Failed because of python-rospkg-modules:amd64' 02:16:20 39 ' Reinst Failed because of python-rosdistro-modules:amd64' 02:16:20 40 ' Reinst Failed because of python-rosdistro:amd64' 02:16:20 41 ' Reinst Failed because of python-rosdep:amd64'