-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lost executable on semantic_point_annotator from debian #30
Comments
Is it possible you installed the package via root/superuser and are trying to execute it from a user without permissions? Could you confirm the permissions your user has and the executable has and post them here? |
It looks like I installed it only to /opt/ros/indigo/bin This means the node is run without rosrun and by calling: sac_inc_ground_removal_node It's deceptive, and most nodes run with rosrun are found in the /opt/ros/indigo/lib path. Do you recommend I change this so it installs to lib instead? |
@thedash You're right! |
@thedash kindly ping to maintainer |
@furushchev I'm no longer maintaining PR2. Do you mind making the change? |
@thedash Yes, until update, we cannot execute the node from roslaunch. |
@thedash ping |
Hi, I tried to use
semantic_point_annotator
package that containssac_inc_ground_removal_node
executable, and installed viaapt-get install ros-indigo-semantic-point-annotator
.However,
rosrun
could not find any executable:rosrun semantic_point_annotator sac_inc_ground_removal_node [rosrun] Couldn't find executable named sac_inc_ground_removal_node below /opt/ros/indigo/share/semantic_point_annotator
I further checked that
install
section inCMakeLists.txt
is written correctly and looked into contents which are installed and found the executable:$ dpkg -L ros-indigo-semantic-point-annotator | grep bin /opt/ros/indigo/bin /opt/ros/indigo/bin/sac_inc_ground_removal_node
So I guess that there is something wrong with releasing process.
@thedash Please could you check if there is any part to change permission of executable file on releasing process?
The text was updated successfully, but these errors were encountered: