vcstools / wstool

A tool for managing a workspace of multiple heterogenous SCM repositories
Other
34 stars 43 forks source link

wstool init fails #10

Closed wjwwood closed 11 years ago

wjwwood commented 11 years ago

This ROS answers question:

http://answers.ros.org/question/57693/wstool-init-fails/

exposes a traceback:

ubuntu:~/overlay_ws/src$ wstool init
Traceback (most recent call last):
  File "/usr/bin/wstool", line 63, in <module>
    sys.exit(wstool.wstool_cli.wstool_main(sys.argv))
  File "/usr/lib/pymodules/python2.7/wstool/wstool_cli.py", line 217, in wstool_main
    'info': cli.cmd_info,
AttributeError: WstoolCLI instance has no attribute 'cmd_info'

And this behavior/command line use of wstool is in this tutorial:

http://ros.org/wiki/catkin/Tutorials/workspace_overlaying#Adding_Packages_to_Your_catkin_Workspace

which may need to be updated if this is an incorrect set of arguments for wstool.

tkruse commented 11 years ago

Cannot reproduce, unless I use wstool>=0.0.3 with rosinstall<0.6.25.

Possibly we could add a versioned dependency check, though up to now we just told users to update when they had this situation, which is easier to maintain (a bad versioned dependency is also not helpful).

On Mon, Mar 11, 2013 at 8:14 PM, William Woodall notifications@github.comwrote:

This ROS answers question:

http://answers.ros.org/question/57693/wstool-init-fails/

exposes a traceback:

ubuntu:~/overlay_ws/src$ wstool init Traceback (most recent call last): File "/usr/bin/wstool", line 63, in sys.exit(wstool.wstool_cli.wstool_main(sys.argv)) File "/usr/lib/pymodules/python2.7/wstool/wstool_cli.py", line 217, in wstool_main 'info': cli.cmd_info, AttributeError: WstoolCLI instance has no attribute 'cmd_info'

And this behavior/command line use of wstool is in this tutorial:

http://ros.org/wiki/catkin/Tutorials/workspace_overlaying#Adding_Packages_to_Your_catkin_Workspace

which may need to be updated if this is an incorrect set of arguments for wstool.

— Reply to this email directly or view it on GitHubhttps://github.com/vcstools/wstool/issues/10 .

davetcoleman commented 11 years ago

I'm having this same issue - I was able to pull the ROS source code down a month or so ago, but now when I run from the Groovy install from source instructions:

wstool init -j8 src http://packages.ros.org/web/rosinstall/generate/raw/groovy/desktop-full

I get:

Traceback (most recent call last):
  File "/usr/bin/wstool", line 63, in <module>
    sys.exit(wstool.wstool_cli.wstool_main(sys.argv))
  File "/usr/lib/pymodules/python2.7/wstool/wstool_cli.py", line 217, in wstool_main
    'info': cli.cmd_info,
AttributeError: WstoolCLI instance has no attribute 'cmd_info'

I'm not sure how to proceed...

wjwwood commented 11 years ago

@davetcoleman Update rosinstall, make sure you don't have rosinstall installed to pip (/usr/local/lib/python...).

wjwwood commented 11 years ago

Also, this is resolved.

wjwwood commented 11 years ago

@davetcoleman see @tkruse's answer to the question on answers.ros.org for more information about removing the pip version of rosinstall if needed.

davetcoleman commented 11 years ago

I have followed his instructions but when I type rosinstall I get:

ERROR: Cannot find required rosinstall library version, check your installation (also of vcstools) is up-to-date. One frequent cause is that rosinstall 0.5 is still installed in /usr/local/lib.
No module named rosinstall.rosinstall_cli

I've tried a lot of other stuff too... I think the problem is I'm not sure the history of this computer's installations (junk left over from previous users)

tkruse commented 11 years ago

Hi Dave,

From your new error message it seems you got rid of the old version of rosinstall, and of the new one too, except for the start script. I'd say run

$ sudo apt-get remove python-vcstools python-rosinstall

and then

$ sudo apt-get install -u python-rosinstall python-vcstools

Maybe also paste the log from the install command, it might tell us more about your system state.

davetcoleman commented 11 years ago

Thanks @tkruse, that was the exact fix that @wjwwood helped me with but I forgot to post the fix here. I just need to uninstall and re-install it!