-
Notifications
You must be signed in to change notification settings - Fork 171
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ROS_ETC_DIR inconsistency #582
Comments
@paulbovbel Can you please provide more detailed information: what platform are you on, what are your environment variables set to, exact sequence of steps to reproduce. @allenh1 Since you created the referenced patch can you please look into this. |
@dirk-thomas I can certainly do that -- will give it a go in a container in a little bit and let you know what I get. |
Reproduction on a clean xenial container:
|
Okay, I found something after looking into this.
The environment variable gets set by @dirk-thomas Perhaps a better patch would be to introduce a |
Since the reference PR breaks the behavior of @allenh1 Please feel free to create a follow up PR to allow different locations for the rosdep source files. I just don't want to wait for a patch, testing it, let others comment and review to address the regression. |
That's a fair point -- this is certainly not good. My apologies, I should have tested sourcing I've got a proposed fix up for it, which I will test far more thoroughly. |
The referenced change has been reverted in #584 and a new version |
It appears that this PR (#551) has introduced an issue where
sudo rosdep init
will write to/etc/ros/rosdep/sources.list.d
, whilerosdep update
will try to read from whichever environment is sourced, typically/opt/ros/$ROS_DISTRO/etc/ros/rosdep/sources.list.d
.The text was updated successfully, but these errors were encountered: