The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
rosdep is designed to install system dependencies not ros packages. (It can install ros packages which act like system dependencies in some cases helpfully)
Please provide real outputs and instructions to reproduce the problem. I do not get the same behavior as you do.
tfoote@BigFoote:/tmp$ svn checkout http://rtm-ros-robotics.googlecode.com/svn/trunk/rtmros_hironx/hironx_ros_bridge
A hironx_ros_bridge/test
A hironx_ros_bridge/test/test_hironx_moveit.py
A hironx_ros_bridge/test/test-hironx-ros-bridge.py
A hironx_ros_bridge/test/test-hironx-ros-bridge.launch
A hironx_ros_bridge/test/test-hironx.py
A hironx_ros_bridge/test/test-hironx.launch
A hironx_ros_bridge/models
A hironx_ros_bridge/models/HIRONX_controller_config.yaml
A hironx_ros_bridge/models/kawada-hironx.dae
A hironx_ros_bridge/models/kawada-hironx.rviz
A hironx_ros_bridge/models/kawada-hironx.l
A hironx_ros_bridge/models/kawada-hironx.zae
A hironx_ros_bridge/models/kawada-hironx.yaml
A hironx_ros_bridge/conf
A hironx_ros_bridge/conf/nosim.RobotHardware.conf.in
A hironx_ros_bridge/conf/xml.in
A hironx_ros_bridge/conf/nosim.xml.in
A hironx_ros_bridge/conf/conf.in
A hironx_ros_bridge/conf/RobotHardware.conf.in
A hironx_ros_bridge/conf/nosim.conf.in
A hironx_ros_bridge/manifest.xml
A hironx_ros_bridge/robot
A hironx_ros_bridge/robot/rtcdRobotMode.conf.in
A hironx_ros_bridge/robot/robot-basecomponents-install.sh
A hironx_ros_bridge/robot/startJSK.sh.in
A hironx_ros_bridge/robot/NameServer.sh.in
A hironx_ros_bridge/robot/ModelLoader.sh.in
A hironx_ros_bridge/robot/robot-install-conf.sh
A hironx_ros_bridge/robot/reboot-robot.sh
A hironx_ros_bridge/robot/rtcd.sh.in
A hironx_ros_bridge/robot/robot-compile-hrpsys.sh
A hironx_ros_bridge/robot/PDgains.sav
A hironx_ros_bridge/robot/Makefile
A hironx_ros_bridge/robot/restart-controller.sh
A hironx_ros_bridge/robot/Robot.conf.in
A hironx_ros_bridge/setup.py
A hironx_ros_bridge/src
A hironx_ros_bridge/src/hironx_ros_bridge
A hironx_ros_bridge/src/hironx_ros_bridge/__init__.py
A hironx_ros_bridge/src/hironx_ros_bridge/hironx.py
A hironx_ros_bridge/scripts
A hironx_ros_bridge/scripts/hironx.py
A hironx_ros_bridge/catkin.cmake
A hironx_ros_bridge/mainpage.dox
A hironx_ros_bridge/package.xml
A hironx_ros_bridge/launch
A hironx_ros_bridge/launch/hironx_ros_bridge.launch
A hironx_ros_bridge/launch/hironx_startup.launch
A hironx_ros_bridge/launch/hironx_ros_bridge_simulation.launch
A hironx_ros_bridge/CMakeLists.txt
A hironx_ros_bridge/Makefile
Checked out revision 5934.
tfoote@BigFoote:/tmp$ cd hironx_ros_bridge/
tfoote@BigFoote:/tmp/hironx_ros_bridge$ rosaddpwd
tfoote@BigFoote:/tmp/hironx_ros_bridge$ rosdep install hironx_ros_bridgeERROR: the following packages/stacks could not have their rosdep keys resolved
to system dependencies:
hironx_ros_bridge: Missing resource hrpsys_ros_bridge
ROS path [0]=/opt/ros/hydro/share/ros
ROS path [1]=/tmp/hironx_ros_bridge
ROS path [2]=/opt/ros/hydro/share
ROS path [3]=/opt/ros/hydro/stacks
| | 2 | No.2 Revision |
rosdep is designed to install system dependencies not ros packages. (It can install ros packages which act like system dependencies in some cases helpfully)
Please provide real outputs and instructions to reproduce the problem. I do not get the same behavior as you do. Edit:
tfoote@BigFoote:/tmp$ svn checkout http://rtm-ros-robotics.googlecode.com/svn/trunk/rtmros_hironx/hironx_ros_bridge
A This does not work for dry packages in all cases as it can't traverse them cleanly.
This is an extended useage which is not in the design specification, and being for a deprecated system we're not going to spend a lot of time debugging it.You can make it work for wet dependencies using the --from-path argument by renaming the manifest.xml to something else.
It worked for me using your packages by renaming
the| | 3 | No.3 Revision |
rosdep is designed to install system dependencies not ros packages. (It can install ros packages which act like system dependencies in some cases helpfully)
Edit:
This does not work for dry packages in all cases as it can't traverse them cleanly. This is an extended useage which is not in the design specification, and being for a deprecated system we're not going to spend a lot of time debugging it.
You can make it work for wet dependencies using the --from-path argument by renaming the manifest.xml to something else. Related question here
It worked for me using your packages by renaming the manifest.xml
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.