-
Notifications
You must be signed in to change notification settings - Fork 53
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
rosdep install for rolling fails because of the transition from focal to jammy #722
Comments
I noticed on the build you linked, you are running in docker container |
Ah, yes, you're right. I missed it. We need |
+1 to this issue, but from using Action logs from two different repos that started failing recently:
Exact error of CMake failing to find ament_cmake:
Edit: Here's the source of the error, where rosdep fails to find the packages:
|
Looks like Focal was removed as a valid Ubuntu distro for Rolling: https://github.com/ros/rosdistro/pull/32036/files#diff-a79d50d14101a47dfc4ea7b0dd7b9446f34b544807d8f0c48cc6a8f07fc3b36aR11. So you need to use Jammy (or build from source on Focal), but the binary packages are currently not available on Jammy: http://packages.ros.org/ros2/ubuntu/dists/jammy/main/binary-amd64/Packages. The workaround mentioned in the issue works though. |
Got it, I believe these issues should disappear after a while when the transition process is properly complete. Am I right?
I can confirm that the work around does work. For detailed reference for others, to implement the work around, add and change your CI to use your commit or branch, ie.
|
Yep! I think the binary packages will be available soon. |
I'm working on it, though we're hitting bumps in the road |
Description
rosdep install for rolling fails because of the transition from focal to jammy.
ros/rosdistro#32036
Expected Behavior
pass build ci for rolling
Actual Behavior
fails build ci for rolling
To Reproduce
** Steps to reproduce the behavior, e.g.
https://github.com/ros-drivers/gscam/runs/5160230528?check_suite_focus=true
System (please complete the following information)
** For ROS 2 bugs - please attach a VCS.repos or Dockerfile if possible to help us reproduce the environment **
Additional context
Some workarounds are
--os=ubuntu:jammy
intorosdep install
command for rolling build.The text was updated successfully, but these errors were encountered: