Open TSoli opened 2 months ago
Ah gosh, it seems like we got it wrong - again :(. Any ideas on how to best proceed @traversaro? It's such a pain that we can use pip
for everything.
I think this is another problem I noticed while reviewing patches. There are a bunch of patches that just rename executables/scrips, probably to avoid clobbering when executables/scripts were not installed in package-specific location. However, now that they are, I guess we can just drop this patches, for example https://github.com/RoboStack/ros-humble/blob/main/patch/ros-humble-demo-nodes-py.patch . As a workaround one can call
ros2 run demo_nodes_py demo_listener
Until the issue is fixed.
Other similar patches that we can just drop:
I think this is another problem I noticed while reviewing patches. There are a bunch of patches that just rename executables/scrips, probably to avoid clobbering when executables/scripts were not installed in package-specific location. However, now that they are, I guess we can just drop this patches, for example https://github.com/RoboStack/ros-humble/blob/main/patch/ros-humble-demo-nodes-py.patch . As a workaround one can call
ros2 run demo_nodes_py demo_listener
Until the issue is fixed.
Amazing! Thanks so much for the extremely quick replies. This seems to work. To confirm, this won't likely cause problems with building my own python packages?
I think this is another problem I noticed while reviewing patches. There are a bunch of patches that just rename executables/scrips, probably to avoid clobbering when executables/scripts were not installed in package-specific location. However, now that they are, I guess we can just drop this patches, for example https://github.com/RoboStack/ros-humble/blob/main/patch/ros-humble-demo-nodes-py.patch . As a workaround one can call
ros2 run demo_nodes_py demo_listener
Until the issue is fixed.
Amazing! Thanks so much for the extremely quick replies. This seems to work. To confirm, this won't likely cause problems with building my own python packages?
It should not.
Ah awesome, that's good news, thanks a lot for clarifying @traversaro! Have removed the patches; will be fixed after the next rebuild :)
Solution to issue cannot be found in the documentation.
Issue
Hi, I followed the getting started guide to install ros-humble with mamba however it seems that the demo python packages are not working (I have not tried with building my own yet so can't confirm if it is all python packages). The cpp example packages do work though. For the below, I made a mamba environment called test which I then activated. Now when I try the example from the ros2 humble docs:
The output from terminal 2 is "No executable found".
If I install ros-humble normally (without robostack in a mamba env) then the demos work correctly.
I think this is likely related to #41 but I can't tell if this was supposed to be fixed or there was a good workaround.
Installed packages
Environment info