Skip to content
This repository has been archived by the owner on Jun 25, 2020. It is now read-only.

rosws init fails when /opt/ros is a symbolic link #22

Closed
moesenle opened this issue Nov 5, 2012 · 0 comments
Closed

rosws init fails when /opt/ros is a symbolic link #22

moesenle opened this issue Nov 5, 2012 · 0 comments

Comments

@moesenle
Copy link

moesenle commented Nov 5, 2012

In our case, /opt/ros is a symbolic link pointing to /work/ros on a different partition. Calling rosws init fails with the following error:

lohr@atbeetz15:~/rosws$ /usr/bin/rosws init . /opt/ros/fuerte/
Using ROS_ROOT: /work/ros/fuerte/
Writing /usr/wiss/lohr/rosws/.rosinstall
(Over-)Writing setup.sh, setup.bash, and setup.zsh in /usr/wiss/lohr/rosws
ERROR in rosinstall: Multiple ros stacks found in config set(['/opt/ros/fuerte/share/ros', '/work/ros/fuerte/share/ros']), Please elimate all but one.
They come from the following sources: {'/opt/ros/fuerte/setup.sh': '/opt/ros/fuerte/share/ros', '/work/ros/fuerte/share/ros': '/work/ros/fuerte/share/ros'}

My guess is that the expansion of links is inconsistent, i.e. sometimes the absoulte path and sometimes the path including the link is used.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants