In the follow-up from the security issue on the ROS build farm last week, the ros-shadow-fixed repository has been replaced with the ros-testing repository.
Note that industrial_ci has already updated their codebase upstream and have patched in a redirection from ros-shadow-fixed to ros-testing for people who are slow to update their configs (like us), which is why we haven't seen any issues yet.
Note also that, since we use the stereolabs/zed:ubuntu1804-cuda10.0-zed2.7 docker image rather than the stereolabs/zed:ubuntu1804-cuda10.0-zed2.7-ros image, we should still be okay with our docker image. Stereolabs still has not updated their docker images, so I suspect the -ros images will have the wrong GPG key for the ROS package servers, but we aren't using these so I believe we will face no issues here.
Pull Request
In the follow-up from the security issue on the ROS build farm last week, the
ros-shadow-fixed
repository has been replaced with theros-testing
repository.Details here: https://discourse.ros.org/t/new-gpg-keys-deployed-for-packages-ros-org/9454
Note that industrial_ci has already updated their codebase upstream and have patched in a redirection from
ros-shadow-fixed
toros-testing
for people who are slow to update their configs (like us), which is why we haven't seen any issues yet.Note also that, since we use the
stereolabs/zed:ubuntu1804-cuda10.0-zed2.7
docker image rather than thestereolabs/zed:ubuntu1804-cuda10.0-zed2.7-ros
image, we should still be okay with our docker image. Stereolabs still has not updated their docker images, so I suspect the-ros
images will have the wrong GPG key for the ROS package servers, but we aren't using these so I believe we will face no issues here.Contribution Checklist
Change Checklist