-
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
rosdep install python3 dependencies when a package has manifest.xml and package.xml #736
Comments
This prevents the install-from-source instructions for Noetic to work. @sloretz FYI |
The package.xml also lists rospack. It seems odd that it coming from a manifest.xml vs a package.xml would change how it's dependencies are evaluated. |
Not really, for the |
But should that affect |
In my case I was using the latest code from the development branch. |
I think #353 (Prefer package.xml in hybrid packages?) is related. Maybe it is time to prefer wet over dry in the meantime, which would probably solve most issues with features introduced in newer |
Issue description
It appears that wrongly rosdep installs python3 version of packages, removing needed python2 packages in the process.
How to reproduce
Trying to build
ros_comm
from source for Melodic:To make the example clearer we'll install
python-catkin-tools
and build the workspace with that Python2 packageThis fails with
catkin tools has been uninstall by rosdep
Additional info
This issue does not happen if the
manifest.xml
from roslisp is not presentPossible reason: roslisp's
manifest.xml
depends onrospack
, rosdep installs all dependencies ofrospack
, regardless of their ROS python versionThe text was updated successfully, but these errors were encountered: