Cannot locate rosdep definition for [joint_state_publisher]

asked 2013-05-22 20:25:34 -0500

2062 ●24 ●47 ●55

updated 2013-05-23 14:08:08 -0500

One of my packages has a run dependency on the joint state publisher (cfrom a roslauncher). Checking the dependencies with rosdep gives me this error:

$ rosdep check robosem_meta
All system dependencies have been satisified
ERROR[robosem_meta]: Cannot locate rosdep definition for [joint_state_publisher]
        rosdep key : joint_state_publisher
        OS name    : ubuntu
        OS version : precise
        Data: <no data>

I have the joint_state_publisher installed and I can use it without problems. So this is not a real problem, but I would still like to fix it. Anyone knows how?

PS: Unfortunately the link for filing issue tickets on the wiki is not existent or broken, otherwise I would have used that for problems like this one here. Maybe the maintainer could move the code to Github or Bitbucket?

/edit: My package is a catkin package and the dependency on the joint_state_publisher is defined like this:

<run_depend>joint_state_publisher</run_depend>

edit retag flag offensive close merge delete

Comments

What happens when you do "rosdep install joint_state_publisher"?

You could try installing urdf_tools from http://www.ros.org/wiki/urdf_tools/ which comes with the joint_state_publisher node.

sobotacm ( 2013-05-23 00:24:15 -0500 )edit

@sobotacm The joint_state_publisher is installed and working. The only issue is that rosdep does not recognise it.

bit-pirate ( 2013-05-23 14:03:20 -0500 )edit

add a comment

4

answered 2013-05-23 14:19:04 -0500

William

17335 ●101 ●182 ●262 http://wjwwood.io/

According to:

http://ros.org/debbuild/groovy.html

joint_state_publisher is part of the robot_model_visualization stack which is dry (rosbuild). caktin packages cannot depend on rosbuild packages.

edit flag offensive delete link

Comments

1

So that's the reason why rosdep complains?

bit-pirate ( 2013-05-23 14:52:25 -0500 )edit

2

Yes. Since catkin can't resolve it, the dependency is passed along to rosdep. That has some advantages, but frequently generates confusing error messages.

joq ( 2013-05-23 16:46:47 -0500 )edit

2

@joq is correct. All catkin dependencies are passed to rosdep for processing. rosdep has no knowledge of dry (rosbuild) packages so when you list a dry package as a dependency of a wet package, rosdep doesn't know what to do with it.

William ( 2013-05-23 17:26:25 -0500 )edit

Thanks for the clarification!

bit-pirate ( 2013-05-23 18:04:23 -0500 )edit

add a comment

1

answered 2013-05-23 01:38:35 -0500

Martin Günther

11816 ●82 ●159 ●198 https://www.dfki.de/en...

In your manifest.xml, you probably have the following line:

<rosdep name="joint_state_publisher"/>

This is incorrect; instead, change it to:

<depend package="joint_state_publisher"/>

The reason is that rosdep checks for system dependencies (i.e., non-ROS software that is available as a debian package, like libmesa or qt4-qmake). On the other hand, rospack (which is invoked by the depend tag) is responsible for finding ROS package dependencies.

edit flag offensive delete link

Comments

I forgot to mention, that my package is a catkin package and the dependency is defined as <run_depend>joint_state_publisher</run_depend>. I have added this information to my question. Any idea what could cause this error in a catkin package?

bit-pirate ( 2013-05-23 14:09:58 -0500 )edit

All right, I assumed you were using rosbuild. William's answer is correct.

Martin Günther ( 2013-05-23 23:10:40 -0500 )edit

add a comment

Cannot locate rosdep definition for [joint_state_publisher]

Comments

2 Answers

Comments

Comments

Question Tools

Stats

Related questions

Cannot locate rosdep definition for [joint_state_publisher] edit

Comments

2 Answers

Comments

Comments

Question Tools

Stats

Related questions

Cannot locate rosdep definition for [joint_state_publisher]