ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

answered 2012-09-03 12:33:25 -0500

joq gravatar image

Did you run these commands?

$ sudo rosdep init
$ rosdep update

(Please respond by editing your question.)

Is this the tutorial you are running?

Did you run these commands?

$ sudo rosdep init
$ rosdep update

(Please respond by editing your question.)

Is this the tutorial you are running?

Did you run these commands?

$ sudo rosdep init
$ rosdep update

(Please respond by editing your question.)

UPDATE: you seem to have an old rosdep version installed somewhere. What does this show?

$ which rosdep

If it says something like /usr/local/bin/rosdep, then you need to uninstall the pip or easy_install version you had previously installed. That's simple with pip:

$ sudo pip uninstall rosdep

If you used easy_install, you'll have to find and remove all the relevant files by hand.

Is this the tutorial you are running?

Did you run these commands?

$ sudo rosdep init
$ rosdep update

(Please respond by editing your question.)

UPDATE: you seem to have an old rosdep version installed somewhere. What does this show?

$ which rosdep

If it says something like /usr/local/bin/rosdep, then you need to uninstall the pip or easy_install version you had previously installed. That's simple with pip:

$ sudo pip uninstall rosdep

If you used easy_install, you'll have to find and remove all the relevant files by hand.

UPDATE #2: The uninstall was to remove the pip version in /usr/local/bin/rosdep. Then, it will use the correct, up-to-date /usr/bin/rosdep automatically installed via apt-get from the python-rosdep package. After uninstalling, "which rosdep" should show that one.

The pip version is deprecated, because it leads to exactly this kind of problem.

Is this the tutorial you are running?

Did you run these commands?

$ sudo rosdep init
$ rosdep update

(Please respond by editing your question.)

UPDATE: you seem to have an old rosdep version installed somewhere. What does this show?

$ which rosdep

If it says something like /usr/local/bin/rosdep, then you need to uninstall the pip or easy_install version you had previously installed. That's simple with pip:

$ sudo pip uninstall rosdep

If you used easy_install, you'll have to find and remove all the relevant files by hand.

UPDATE #2: The uninstall was to remove the pip version in /usr/local/bin/rosdep. Then, it will use the correct, up-to-date /usr/bin/rosdep automatically installed via apt-get from the python-rosdep package. After uninstalling, "which rosdep" should show that one.

The pip version is deprecated, because it leads to exactly this kind of problem.

UPDATE #3: somehow your Debian APT database has gotten screwed up. That is not normal. Does the list of files printed here include /usr/bin/rosdep? Does that file exist?

$ dpkg -L python-rosdep

If not, try uninstalling python-rosdep and then reinstalling it again:

$ sudo apt-get remove python-rosdep
$ sudo apt-get install python-rosdep

Is this the tutorial you are running?

Did you run these commands?

$ sudo rosdep init
$ rosdep update

(Please respond by editing your question.)

UPDATE: you seem to have an old rosdep version installed somewhere. What does this show?

$ which rosdep

If it says something like /usr/local/bin/rosdep, then you need to uninstall the pip or easy_install version you had previously installed. That's simple with pip:

$ sudo pip uninstall rosdep

If you used easy_install, you'll have to find and remove all the relevant files by hand.

UPDATE #2: The uninstall was to remove the pip version in /usr/local/bin/rosdep. Then, it will use the correct, up-to-date /usr/bin/rosdep automatically installed via apt-get from the python-rosdep package. After uninstalling, "which rosdep" should show that one.

The pip version is deprecated, because it leads to exactly this kind of problem.

UPDATE #3: somehow your Debian APT database has gotten screwed up. That is not normal. Does the list of files printed here include /usr/bin/rosdep? Does that file exist?

$ dpkg -L python-rosdep

If not, try uninstalling python-rosdep and then reinstalling it again:

$ sudo apt-get remove python-rosdep
$ sudo apt-get install python-rosdep

UPDATE #4: you are not doing anything wrong, this is just a messy problem. I experienced it, too, when the pip version was replaced by the python-rosdep package.

I think the which command problem was caused by the shell. It keeps a hash table of commands it has found in the search path. When we deleted /usr/local/bin/rosdeps, it got confused.

I have seen this problem with those pyshared files not getting unpacked into /usr/lib/python2.7 properly, but I can't remember exactly how I resolved it.

It might help to reboot.

Is this the tutorial you are running?

Did you run these commands?

$ sudo rosdep init
$ rosdep update

(Please respond by editing your question.)

UPDATE: you seem to have an old rosdep version installed somewhere. What does this show?

$ which rosdep

If it says something like /usr/local/bin/rosdep, then you need to uninstall the pip or easy_install version you had previously installed. That's simple with pip:

$ sudo pip uninstall rosdep

If you used easy_install, you'll have to find and remove all the relevant files by hand.

UPDATE #2: The uninstall was to remove the pip version in /usr/local/bin/rosdep. Then, it will use the correct, up-to-date /usr/bin/rosdep automatically installed via apt-get from the python-rosdep package. After uninstalling, "which rosdep" should show that one.

The pip version is deprecated, because it leads to exactly this kind of problem.

UPDATE #3: somehow your Debian APT database has gotten screwed up. That is not normal. Does the list of files printed here include /usr/bin/rosdep? Does that file exist?

$ dpkg -L python-rosdep

If not, try uninstalling python-rosdep and then reinstalling it again:

$ sudo apt-get remove python-rosdep
$ sudo apt-get install python-rosdep

UPDATE #4: you are not doing anything wrong, this is just a messy problem. I experienced it, too, when the pip version was replaced by the python-rosdep package.

I think the which command problem was caused by the shell. It keeps a hash table of commands it has found in the search path. When we deleted /usr/local/bin/rosdeps, it got confused.

I have seen this problem with those pyshared files not getting unpacked into /usr/lib/python2.7 properly, but I can't remember exactly how I resolved it.

It might help to reboot.

UPDATE #5: OK, make sure there is no old version anywhere in /usr/local:

$ find /usr/local -name rosdep2

If that finds anything at all, delete it. Then, try reinstalling the scripts again:

$ sudo apt-get remove python-rosdep
$ sudo apt-get install python-rosdep

Is this the tutorial you are running?

Did you run these commands?

$ sudo rosdep init
$ rosdep update

(Please respond by editing your question.)

UPDATE: you seem to have an old rosdep version installed somewhere. What does this show?

$ which rosdep

If it says something like /usr/local/bin/rosdep, then you need to uninstall the pip or easy_install version you had previously installed. That's simple with pip:

$ sudo pip uninstall rosdep

If you used easy_install, you'll have to find and remove all the relevant files by hand.

UPDATE #2: The uninstall was to remove the pip version in /usr/local/bin/rosdep. Then, it will use the correct, up-to-date /usr/bin/rosdep automatically installed via apt-get from the python-rosdep package. After uninstalling, "which rosdep" should show that one.

The pip version is deprecated, because it leads to exactly this kind of problem.

UPDATE #3: somehow your Debian APT database has gotten screwed up. That is not normal. Does the list of files printed here include /usr/bin/rosdep? Does that file exist?

$ dpkg -L python-rosdep

If not, try uninstalling python-rosdep and then reinstalling it again:

$ sudo apt-get remove python-rosdep
$ sudo apt-get install python-rosdep

UPDATE #4: you are not doing anything wrong, this is just a messy problem. I experienced it, too, when the pip version was replaced by the python-rosdep package.

I think the which command problem was caused by the shell. It keeps a hash table of commands it has found in the search path. When we deleted /usr/local/bin/rosdeps, it got confused.

I have seen this problem with those pyshared files not getting unpacked into /usr/lib/python2.7 properly, but I can't remember exactly how I resolved it.

It might help to reboot.

UPDATE #5: OK, make sure there is no old version anywhere in /usr/local:

$ find /usr/local -name rosdep2

If that finds anything at all, delete it. Then, try reinstalling the scripts again:

$ sudo apt-get remove python-rosdep
$ sudo apt-get install python-rosdep

UPDATE #6: I have no expectation that uninstalling everything would help. This is not Windows.

But, if you want to try that, this should remove all of ROS (note the single-quote characters):

$ sudo apt-get remove python-rosdep 'ros-fuerte-*'