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 |
Changing ownership of the ~/.ros directory is the correct fix. rosdep recently go a fix-permissions verb that does exactly that and improves the error message, but it has not been released yet, so for now it is easiest to do it manually as @mehdi-tlili suggests.
| | 2 | No.2 Revision |
Changing ownership of the ~/.ros directory is the correct fix. rosdep recently go a fix-permissions verb that does exactly that and improves the error message, but it has not been released yet, so for now it is easiest to do it manually as @mehdi-tlili @mehdi tlili suggests.
| | 3 | No.3 Revision |
Changing ownership of the ~/.ros directory is the correct fix. rosdep recently go a fix-permissions verb that does exactly that and improves the error message, but it has not been released yet, so for now it is easiest to do it manually as @mehdi tlili suggests.
Edit: rosdep has been re-released, so if you update it from pip/apt, you shoul have gotten a more useful error message that indicates to run sudo rosdep fix-permissions
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.
