Hi,
I tried to build the ROS2 packages, but it failed because of a GPG error. I've read the old key has been revoked as part of the measures to deal with a recent security incident with build.ros.org.
Do you have any suggestions how to fix this?
Thanks for your help.
$ docker-compose up build
[...]
Get:17 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages [11.3 MB]
Err:7 http://packages.ros.org/ros/ubuntu bionic InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY F42ED6FBAB17C654
Err:8 http://packages.ros.org/ros2/ubuntu bionic InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY F42ED6FBAB17C654
[...]
Reading package lists...
W: GPG error: http://packages.ros.org/ros/ubuntu bionic InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY F42ED6FBAB17C654
E: The repository 'http://packages.ros.org/ros/ubuntu bionic InRelease' is not signed.
W: GPG error: http://packages.ros.org/ros2/ubuntu bionic InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY F42ED6FBAB17C654
E: The repository 'http://packages.ros.org/ros2/ubuntu bionic InRelease' is not signed.
ERROR: Service 'build' failed to build: The command '/bin/sh -c apt-get update && apt-get install --no-install-recommends -y ${PYTHON}-rosdep ${PYTHON}-rosinstall ${PYTHON}-vcstools && rm -rf /var/lib/apt/lists/*' returned a non-zero code: 100
Hi, I tried to build the ROS2 packages, but it failed because of a GPG error. I've read the old key has been revoked as part of the measures to deal with a recent security incident with build.ros.org. Do you have any suggestions how to fix this?
Thanks for your help.
$ docker-compose up build
[...][...]