Skip to content
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

Closed
wep21 opened this issue Feb 11, 2022 · 8 comments · Fixed by ros-tooling/setup-ros-docker#43
Labels
bug Something isn't working

Comments

@wep21
Copy link
Contributor

wep21 commented Feb 11, 2022

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.

  1. Run build ci for rolling
    https://github.com/ros-drivers/gscam/runs/5160230528?check_suite_focus=true

System (please complete the following information)

  • OS: Ubuntu focal
  • ROS 2 Distro: [rolling]

** For ROS 2 bugs - please attach a VCS.repos or Dockerfile if possible to help us reproduce the environment **

Additional context

Some workarounds are

  • adding --os=ubuntu:jammy into rosdep install command for rolling build.
@wep21 wep21 added the bug Something isn't working label Feb 11, 2022
@wep21
Copy link
Contributor Author

wep21 commented Feb 11, 2022

FYI @emersonknapp @nuclearsandwich

@wep21 wep21 changed the title rosdep install for rolling fails because of transition from focal to jammy rosdep install for rolling fails because of the transition from focal to jammy Feb 11, 2022
@emersonknapp
Copy link
Contributor

I noticed on the build you linked, you are running in docker container rostooling/setup-ros-docker:ubuntu-focal-ros-rolling-ros-base-latest - i assume we'll need to update setup-ros-docker to provide ubuntu-jammy-ros-rolling-ros-base-latest instead, yeah? That seems to me like it should solve the immediate problem you've actually pointed out here?

@wep21
Copy link
Contributor Author

wep21 commented Feb 11, 2022

Ah, yes, you're right. I missed it. We need ubuntu-jammy-ros-rolling-ros-base-latest.

@ijnek
Copy link
Contributor

ijnek commented Feb 15, 2022

+1 to this issue, but from using rostooling/setup-ros instead of rostooling/setup-ros-docker.

Action logs from two different repos that started failing recently:

Exact error of CMake failing to find ament_cmake:

  CMake Error at CMakeLists.txt:8 (find_package):
    By not providing "Findament_cmake.cmake" in CMAKE_MODULE_PATH this project
    has asked CMake to find a package configuration file provided by
    "ament_cmake", but CMake did not find one.
  
    Could not find a package configuration file provided by "ament_cmake" with
    any of the following names:
  
      ament_cmakeConfig.cmake
      ament_cmake-config.cmake

    Add the installation prefix of "ament_cmake" to CMAKE_PREFIX_PATH or set
    "ament_cmake_DIR" to a directory containing one of the above files.  If
    "ament_cmake" provides a separate development package or SDK, be sure it
    has been installed.

Edit:

Here's the source of the error, where rosdep fails to find the packages:

  ERROR: the following packages/stacks could not have their rosdep keys resolved
  to system dependencies:
  soccer_vision_msgs: No definition of [vision_msgs] for OS version [focal]

@christophebedard
Copy link
Member

christophebedard commented Feb 15, 2022

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.

@ijnek
Copy link
Contributor

ijnek commented Feb 16, 2022

Got it, I believe these issues should disappear after a while when the transition process is properly complete. Am I right?

The workaround mentioned in the issue works though.

I can confirm that the work around does work.

For detailed reference for others, to implement the work around, add --os=ubuntu:jammy as seen in
ijnek@80974bd

and change your CI to use your commit or branch, ie.

- uses: ros-tooling/action-ros-ci@80974bd48deac3726e28d7b5fc8a1176481479f5

@christophebedard
Copy link
Member

Got it, I believe these issues should disappear after a while when the transition process is properly complete. Am I right?

Yep! I think the binary packages will be available soon.

@nuclearsandwich
Copy link

Yep! I think the binary packages will be available soon.

I'm working on it, though we're hitting bumps in the road

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants