Revision history [back]

First off, not all ROS packages have great tab autocomplete support. For example rosrun, roslaunch, rospack, and rosmsg all have good support while tools like rosdep and rosinstall do not. So the fact that your rosdep tab autocomplete is not working is not actually a problem.

Likely the original issue that you faced was that some package you installed with apt-get conflicted with some subset or ROS packages. You didn't read the command line output when installing the conflicting package, and you gave the okay to uninstall some subset of ROS packages. Note that ros-kinetic-desktop-full is really just a metapackage that depends on a bundled set of ROS packages. If you uninstall any of these dependencies, then the desktop-full package is also automatically removed. However, other dependencies of desktop-full are not automatically removed (this is what apt-get autoremove is for). Thus, this could explain how you ended up with a partially-installed ROS Kinetic distribution. This would also explain why running sudo apt-get install ros-kinetic-desktop-full would actually end up installing a bunch of packages (but perhaps not all of the dependent packages if you already had some of them installed). Note that if you really want to get to the bottom of what happened /var/log/apt contains a history.log and many older history.log.XX.gz files. These files include all apt-get commands that were run and summaries of which packages were modified as a result. Looking through these files could tell you exactly what originally conflicted, what ROS packages were uninstalled, and show how installing desktop full re-installed the removed packages.

If you were able to run sudo apt-get install ros-kinetic-desktop-full with no issues, then I'd say your ROS system is installed correctly.

First off, not all ROS packages have great tab autocomplete support. For example rosrun, roslaunch, rospack, and rosmsg all have good support while tools like rosdep and rosinstall do not. So the fact that your rosdep tab autocomplete is not working is not actually a problem.

Likely the original issue that you faced was that some package you installed with apt-get conflicted with some subset or of ROS packages. You didn't read the command line output when installing the conflicting package, and you gave the okay to uninstall some subset of ROS packages. Note that ros-kinetic-desktop-full is really just a metapackage that depends on a bundled set of ROS packages. If you uninstall any of these dependencies, then the desktop-full package is also automatically removed. However, other dependencies of desktop-full are not automatically removed (this is what apt-get autoremove is for). Thus, this could explain how you ended up with a partially-installed ROS Kinetic distribution. This would also explain why running sudo apt-get install ros-kinetic-desktop-full would actually end up installing a bunch of packages (but perhaps not all of the dependent packages if you already had some of them installed). Note that if you really want to get to the bottom of what happened /var/log/apt contains a history.log and many older history.log.XX.gz files. These files include all apt-get commands that were run and summaries of which packages were modified as a result. Looking through these files could tell you exactly what originally conflicted, what ROS packages were uninstalled, and show how installing desktop full re-installed the removed packages.

If you were able to run sudo apt-get install ros-kinetic-desktop-full with no issues, then I'd say your ROS system is installed correctly.

First off, not all ROS packages have great tab autocomplete support. For example rosrun, roslaunch, rospack, and rosmsg all have good support while tools like rosdep and rosinstall do not. So the fact that your rosdep tab autocomplete is not working is not actually a problem.

Likely the original issue that you faced was that some package you installed with apt-get conflicted with some subset of ROS packages. You didn't read the command line output when installing the conflicting package, and you gave the okay to uninstall some subset of ROS the conflicting packages. Note that The ros-kinetic-desktop-full is really just a metapackage that depends on a bundled set of ROS packages. If you uninstall any of these dependencies, then the desktop-full package is also automatically removed. However, other dependencies of desktop-full are not automatically removed (this is what apt-get autoremove is for). Thus, this could explain how you ended up with a partially-installed ROS Kinetic distribution. This would also explain why running sudo apt-get install ros-kinetic-desktop-full would actually end up installing a bunch of packages (but perhaps not all of the dependent packages if you already had some of them installed). Note that if you really want to get to the bottom of what happened /var/log/apt contains a history.log and many older history.log.XX.gz files. These files include all apt-get commands that were run and summaries of which packages were modified as a result. Looking through these files could tell you exactly what originally conflicted, what ROS packages were uninstalled, and show how installing desktop full re-installed the removed packages.

If you were able to run sudo apt-get install ros-kinetic-desktop-full with no issues, then I'd say your ROS system is installed correctly.

First off, not all ROS packages have great tab autocomplete support. For example rosrun, roslaunch, rospack, and rosmsg all have good support while tools like rosdep and rosinstall do not. So the fact that your rosdep tab autocomplete is not working is not actually a problem.

Likely the original issue that you faced was that some package you installed with apt-get conflicted with some subset of ROS packages. You didn't read the command line output when installing the conflicting package, and you gave the okay to uninstall the conflicting packages. The ros-kinetic-desktop-full package is really just a metapackage that depends on a bundled set of ROS packages. If you uninstall any of these dependencies, then the desktop-full package is also automatically removed. However, other dependencies of desktop-full are not automatically removed (this is what apt-get autoremove is for). Thus, this could explain how you ended up with a partially-installed ROS Kinetic distribution. This would also explain why running sudo apt-get install ros-kinetic-desktop-full would actually end up installing a bunch of packages (but perhaps not all of the dependent packages if you already had some of them installed). Note that if you really want to get to the bottom of what happened /var/log/apt contains a history.log and many older history.log.XX.gz files. These files include all apt-get commands that were run and summaries of which packages were modified as a result. Looking through these files could tell you exactly what originally conflicted, what ROS packages were uninstalled, and show how installing desktop full re-installed the removed packages.

If you were able to run sudo apt-get install ros-kinetic-desktop-full with no issues, then I'd say your ROS system is installed correctly.