Closed jtcass01 closed 2 years ago
Apologies for the late reply! I think one issue is that moveit_resources doesn't have a foxy branch. In that case, the Debian should be used, newer versions could easily produce issues with the MoveIt 2 foxy branch. What was listed inside Universal_Robots_ROS2_Driver/moveit2.repos
? Without a workspace snapshot it's hard to tell what's going on. In general, old distro branches should always work with an empty workspace, simply depending on the released Debians. Since our goal is to keep API's stable, we're clearing the repos files as soon as possible. Only on development targets like main
it really makes sense to source dependencies since there might be changes that haven't been released yet.
Description
Foxy Branch is missing proper moveit2 repos file. Had to replace with my own file to get it to properly build.
Your environment
Steps to reproduce
I ran the following commands on my jetson nano after updating to Ubuntu 20.04:
Writing the following inside of moveit2.repos:
Finishing build with moveit2
Expected behavior
The package should have built.
Actual behavior
It produced errors when sourcing from srdfdom. When using apt-get install srdfdom, it was unable to produce a path claiming all joints were in collision. Fixed by rebuilding with new moveit2.repos file.