![[ICO]](/icons/blank.gif){kind=icon}
![[PARENTDIR]](/icons/back.gif){kind=icon}
![[ ]](/icons/unknown.gif){kind=icon}
![[TXT]](/icons/text.gif){kind=icon}
![[ ]](/icons/compressed.gif){kind=icon}
Overview
This package repository provides ROS One packages for Ubuntu releases later than 20.04, which was the last one officially supported by OSRF.The packages available in this repo are built via a github action: https://github.com/ubi-agni/ros-builder-action.
If you want more packages to be included, please file a PR there augmenting the file ros-one.repos.
If a package needs adaptions to be successfully built, these can be hosted as forks with the ROS-O organization: https://github.com/ros-o/ros-o.
Install instructions to use ROS One:
# Configure ROS One apt repository
sudo apt install curl
sudo curl -sSL https://ros.packages.techfak.net/gpg.key -o /etc/apt/keyrings/ros-one-keyring.gpg
echo "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/ros-one-keyring.gpg] https://ros.packages.techfak.net $(lsb_release -cs) main" | sudo tee /etc/apt/sources.list.d/ros1.list
echo "# deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/ros-one-keyring.gpg] https://ros.packages.techfak.net $(lsb_release -cs) main-dbg" | sudo tee -a /etc/apt/sources.list.d/ros1.list
# Install and setup rosdep
# Do not install python3-rosdep2, which is an outdated version of rosdep shipped via the Ubuntu repositories (instead of ROS)!
sudo apt update
sudo apt install python3-rosdep
sudo rosdep init
# Define custom rosdep package mapping
echo "yaml https://ros.packages.techfak.net/ros-one.yaml one" | sudo tee /etc/ros/rosdep/sources.list.d/1-ros-one.list
rosdep update
# Install packages, e.g. ROS desktop
sudo apt install ros-one-desktop
Cutting edge testing repository
In order to use latest builds as soon as they become available, you can use the-testing repository.
Just replace $(lsb_release -cs) above with $(lsb_release -cs)-testing.
Build Schedule and Synchronization
Packages are built nightly by a corresponding CI job and released into the-testing repository. They are synced into the main repository on an irregular basis, roughly every two months.