ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | Q&A
Ask Your Question

[Bug] Package names clash for arm_kinematics_constraint_aware [closed]

asked 2012-09-20 19:41:16 -0600

updated 2012-09-20 20:29:50 -0600

Looks like there is a name clash for package arm_kinematics_constraint_aware as there are two packages with this name in both arm_navigation and kinematics stacks.

Not sure if it suppose to be the same code in both of them, but at the moment it is different and the one in arm_navigation stack has a bug (see relevant question).

P.S. Could not find better place to post this as it's a cross-stack issue.


arm_kinematics_constraint_aware from arm_navigation stack is actually pointing to a package in kinematics stack. Probably it should be set up as a stack dependency then. However arm_navigation contains the code for this packages as well.

So it might be a different bug (?)

edit retag flag offensive reopen merge delete

Closed for the following reason question is not relevant or outdated by Boris
close date 2015-06-25 07:32:07.508865

2 Answers

Sort by ยป oldest newest most voted

answered 2012-11-23 23:28:44 -0600

dbworth gravatar image

Btw, this confused me too.

The header on the wiki page:
is not pulling in the correct information for the Fuerte release, so it looks like there are two stacks available.

The old kinematics stack, which also contained arm_kinematics_constraint_aware was from Electric. Also there are some old links to packages at so you might have downloaded an old release.

edit flag offensive delete link more

answered 2012-09-20 19:59:28 -0600

bit-pirate gravatar image

Such a clash can easily happen. For example, if you have a stack/package installed via a debian package and additionally downloaded the source code in order to work on it.

Usually you resolve this issue by editing your ROS_PACKAGE_PATH to put the location of the package/stack first which you want to use.

Hence, I don't think this is a bug.

edit flag offensive delete link more


Right, but clash between binary and source distribution of same package is a different story, isn't it?

Boris gravatar image Boris  ( 2012-09-20 20:30:05 -0600 )edit

Maybe I don't understand your problem correctly. What exactly did you install and how? If you installed the arm_navigation stack as a debian package and later download the kinematics stack as source, the package of the stack, which comes first in the ROS_PACKAGE_PATH should automatically be used.

bit-pirate gravatar image bit-pirate  ( 2012-09-20 20:49:04 -0600 )edit

[Offtopic] Are you really in Korea? :-)

bit-pirate gravatar image bit-pirate  ( 2012-09-20 20:53:27 -0600 )edit

I installed everything from sources as I am on Fedora. The arm_kinematics_constraint_aware was installed together with other stuff in arm_navigation stack by roslocate info arm_navigation | rosws merge -.

Boris gravatar image Boris  ( 2012-09-20 21:06:09 -0600 )edit

But roslocate info arm_kinematics_constraint_aware | rosws merge - will pull the code from kinematics stack.

Boris gravatar image Boris  ( 2012-09-20 21:08:18 -0600 )edit

OK, so I played with rosws and roslocate for the first time (cool tools actually!) and set up a test workspace. I didn't get any errors using the commands above. What error/missbehaviour does your clash cause?

bit-pirate gravatar image bit-pirate  ( 2012-09-20 22:39:10 -0600 )edit

Since you added arm_kinematics_constraint_aware from the kinematics stack at last, it becomes your new "default" package. If you want to change that, you could add arm_navigation as second or modify your ROS_PACKAGE_PATH by hand.

bit-pirate gravatar image bit-pirate  ( 2012-09-20 22:41:01 -0600 )edit

Sorry for confusion. I didn't add anything from kinimatics stack, I just noticed that it can be a problem for others if they checkout the package from a 'wrong' stack.

Boris gravatar image Boris  ( 2012-09-20 23:34:18 -0600 )edit

Question Tools


Asked: 2012-09-20 19:41:16 -0600

Seen: 201 times

Last updated: Nov 23 '12