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
Humble install fails - rosdep microros #65
Comments
updated cache in /home/blm/.ros/rosdep/sources.cache ERROR: the following packages/stacks could not have their rosdep keys resolved to system dependencies: linorobot2_bringup: Cannot locate rosdep definition for [micro_ros_agent] I am facing same problem, how to resolve that ? |
there’s no rosdep keys for micro ros agent you use the skip flag to omit those warnings https://github.com/linorobot/linorobot2#21-install-linorobot2-package |
Thanks for quick reply, But i am trying to follow the ROBOT installation document. where we need install micro_ros_setup right ? if we skip, it is skipping micro_ros_setup installation itself ? can you advice ? |
@grassjelly Finally, I am able to install the ROBOT computer with install script easily. But now I have strange problem.
|
@grassjelly One more point, actually the Teensy firmware was compiled in Foxy setup, but recently i have migrated the ROBOT computer with Humble Setup. But still the old Foxy Teensy firmware will work together with Humble? or is it necessary to recompile the Teensy under Humble as well ? Also there is no branch for Humble yet in the Linorobot2 Hardware repo ? Kindly suggest a way out |
A couple points on the install
updated cache in /home/blm/.ros/rosdep/sources.cache ERROR: the following packages/stacks could not have their rosdep keys resolved to system dependencies: linorobot2_bringup: Cannot locate rosdep definition for [micro_ros_agent]
This was on a fairly vanilla ros2 humble install Ubuntu 22.04 AMD64. Due to the previous fails on steps 1 & 2, it may be that running the install again was an issue but I had deleted all previous workspaces and the repository directory.
The text was updated successfully, but these errors were encountered: