ament_cmake_ros: Cannot locate rosdep definition for [domain_coordinator]
minggangw opened this issue · 4 comments
Bug report
Required Info:
-
Operating System:
- Ubuntu 18.04
-
Installation type:
Steps to reproduce issue
Execute:
`rosdep install --from-paths ros2-linux/share --ignore-src --rosdistro dashing -y --skip-keys "console_bridge fastcdr fastrtps libopensplice67 libopensplice69 osrf_testing_tools_cpp poco_vendor rmw_connext_cpp rosidl_typesupport_connext_c rosidl_typesupport_connext_cpp rti-connext-dds-5.3.1 tinyxml_vendor tinyxml2_vendor urdfdom urdfdom_headers"
`
Expected behavior
Actual behavior
Step 17/21 : RUN rosdep install --from-paths $ROS2_WS/ros2-linux/share --ignore-src --rosdistro dashing -y --skip-keys "console_bridge fastcdr fastrtps libopensplice67 libopensplice69 osrf_testing_tools_cpp poco_vendor rmw_connext_cpp rosidl_typesupport_connext_c rosidl_typesupport_connext_cpp rti-connext-dds-5.3.1 tinyxml_vendor tinyxml2_vendor urdfdom urdfdom_headers"
---> Running in c1e24ef38e83
ERROR: the following packages/stacks could not have their rosdep keys resolved
to system dependencies:
ament_cmake_ros: Cannot locate rosdep definition for [domain_coordinator]
See detailed https://travis-ci.org/RobotWebTools/rclnodejs/jobs/583689046#L13773
Additional information
This started to happen about one week ago, I haven't changed the configuration of the Docker.
domain_coordinator
is a package that should be part of the archive, so rosdep shouldn't have a problem to find it (the package is in this repo https://github.com/ros2/ament_cmake_ros/).
The link of the archive you share is broken, please share an updated one, and I will try to reproduce the error if it's still happening.
@pbaughman @wjwwood The package doesn't install its manifest file which breaks this use case.
Please file an issue on that repository (or move this one there), perhaps @pbaughman can fix that if he has time.
@pbaughman @wjwwood The package doesn't install its manifest file which breaks this use case.
I realized of that after writing my comment, see #6.