Closed mathias-luedtke closed 2 years ago
Also the official rolling docker images are not available in jammy yet. I don't think this affect industrial_ci tho.
Yesterday the binaries are released, but is seems that rosdep
still has some issues...
example on ros2_control
Does something else should be updated too?
I believe that the mirror did not pick the changes up yet.
Hi @destogl, I have the same issue using the ubuntu jammy docker image, install and setup rosdep through command line. So I think it's more of a rosdep issue atm.
Right now I cannot even run apt update
in a regular ubuntu:jammy
container. It shows plenty of GPG key errors.
I'm only getting GPG errors in apt update
when I include testing
repositories. main
repositories worked fine for me except that rosdep is acting funky and not installing all the dependencies. @mathias-luedtke let me know if I can be helpful in anyway, and I will gladly help. We want to migrate our CI to Rolling + Jammy as soon as possible. and love using industrial_ci.
I'm only getting GPG errors in apt update when I include testing repositories. main repositories worked fine for me
It turned out that this a seccomp issue
docker run -it --rm --security-opt seccomp:unconfined ubuntu:jammy apt update
works
Not sure whats going on with rosdep:
rosdep resolve ament_cmake_python
ERROR: No definition of [ament_cmake_python] for OS version [Jammy Jellyfish]
No definition of [ament_cmake_python] for OS version [Jammy Jellyfish]
rosdep key : ament_cmake_python
OS name : ubuntu
OS version : Jammy Jellyfish
Data:
_is_ros: true
debian:
bullseye:
apt:
packages:
- ros-rolling-ament-cmake-python
osx:
homebrew:
packages:
- ros/rolling/ament_cmake
rhel:
'8':
dnf:
packages:
- ros-rolling-ament-cmake-python
ubuntu:
jammy:
apt:
packages:
- ros-rolling-ament-cmake-python
Strange thing is in Focal rolling rosdep error OS_VERSION
seems to resolve as focal
instead of Focal F.....
. https://github.com/ros-tooling/action-ros-ci/issues/722#issuecomment-1040337895
Seems to a result of https://github.com/ros-infrastructure/rospkg/issues/241
Seems to a result of ros-infrastructure/rospkg#241
https://github.com/ros-infrastructure/rospkg/pull/248 should be coming to a rospkg release near you soon!
rospkg 1.4.0 is uploading now and contains a fix for this issue among other changes.
rolling build is passing again, thank you very much @nuclearsandwich!
774 will fix the configurations, but the repositories are not ready yet.