-
Notifications
You must be signed in to change notification settings - Fork 0
unable to roslaunch anything anymore #2
unable to roslaunch anything anymore #2
Comments
Ok, looks like this was actually upstream. That said, I tried using the patched branch and rebuilding/reinstalling ros-melodic-rosgraph, but I get a new error:
I'm wondering if |
Hey I'm the one who created the PR upstream. Looks like this package is based on version 1.14.3 (https://github.com/ros/ros_comm/tree/1.14.3) which is over a year old. I only patched and tested it locally (on Arch with this package installed) and then made the PR, but it looks like more changes are needed. For now you could probably try to just apply the patch on install to this version and then try to get things working with the devel upstream later. Here's the diff for 1.14.3:
|
Really, really appreciate this. I'll take a look later. Just wanted to comment on the version: I'm not even sure why we're on 1.14.3. We use the versions for ROS Melodic, and Edit: well We often end up patching until upstream catches up. Thanks again!! |
@Darnor any suggestions on tracking this down?
Edit: missed a line, and this is with your patch applied. I get the same error (above) using your fork/patched branch as I do with this 1.14.3 patch... It seems like roslaunch is assuming something exists in rosgraph that doesn't. Is this import supposed to provide |
Booo. So, bizarre occurrence.
I'm not sure which of these was the problem, but with a definite rebuild of roslaunch on 1.14.3 and |
Created PR to fix this. |
This morning I went to actually use ROS to get this error:
I suspected it was some buried lib depend on python3.8 somewhere, so I spent a good part of my day and evening rebuilding absolutely every
ros-melodic-*
package from scratch. I still get the error. Can anyone replicate this? I'm usingturtle_tf
as a reproducible example, but the failure happened on one of my work projects.The text was updated successfully, but these errors were encountered: