You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
mdxtinkernick
changed the title
building empty workspace on pi fails in iron image
building empty workspace on pi fails in jazzy image
Nov 30, 2024
mdxtinkernick
changed the title
building empty workspace on pi fails in jazzy image
building workspace on pi generates errors and fails in jazzy image
Nov 30, 2024
have built an image from ubuntu server 2404 then running the turtlebot4_setup.sh on it. This runs colcon build without the error, and rosdep works as well
Hello @mdxtinkernick
Thank you for reaching out on the Turtlebot 4 Github. Apologies on the late reply for this, but it seems you were able to resolve the matter. I just wanted to check in and see if there was anything else we could help with. Looking forward to hearing from you soon.
Best Regards,
Saif
Hello,
This issue is being closed due to inactivity. If you are still experiencing the issue, feel free to reopen this ticket when you are ready to continue the troubleshooting process.
Best Regards,
Saif
Robot Model
Turtlebot4 Lite
ROS distro
Humble
Networking Configuration
Discovery Server
OS
Other Linux
Built from source or installed?
Installed
Package version
testing now with image as provide for jazzy on pi 2.0.1
Type of issue
Other
Expected behaviour
create an empty workspace on pi and successfully run colcon build
Actual behaviour
colcon build fails, and rosdep as well ModuleNotFoundError: No module named 'catkin_pkg.package'
Error messages
ModuleNotFoundError: No module named 'catkin_pkg.package'
To Reproduce
on pi
mkdir ros_ws
cd ros_ws
mkdir src
colcon build
Other notes
tried
sudo apt install python3-catkin-pkg
python3-catkin-pkg is already the newest version (1.0.0-100)
googling this turned up some mentions about condo environments - but don't think the pi image is using that, so don't know how to fix this
The text was updated successfully, but these errors were encountered: