New Packages for Noetic 2023-03-02

[sloretz]

We’re happy to announce 13 new packages and 110 updates are now available in ROS Noetic. This sync was tagged as noetic/2023-03-02.

This is also the final sync with Debian Buster support, as that platform reached it’s end of life. ros/rosdistro PRs are still being held in preparation for a final snapshot for Debian Buster.

Thank you to every maintainer and contributor who made these updates available!

Package Updates for ROS Noetic

Added Packages [13]:

• ros-noetic-cras-docs-common: 2.1.2-1
• ros-noetic-depthai-ros-driver: 2.6.1-2
• ros-noetic-flatland: 1.3.3-1
• ros-noetic-flatland-msgs: 1.3.3-1
• ros-noetic-flatland-plugins: 1.3.3-1
• ros-noetic-flatland-server: 1.3.3-1
• ros-noetic-flatland-viz: 1.3.3-1
• ros-noetic-image-transport-codecs: 2.1.2-1
• ros-noetic-lanelet2-matching: 1.2.0-2
• ros-noetic-moveit-task-constructor-core: 0.1.1-1
• ros-noetic-moveit-task-constructor-msgs: 0.1.1-1
• ros-noetic-rviz-marker-tools: 0.1.1-1
• ros-noetic-rviz-tool-path-display: 0.1.1-1

Updated Packages [110]:

• ros-noetic-ackermann-steering-controller: 0.21.0-1 → 0.21.1-1
• ros-noetic-bosch-locator-bridge: 1.0.7-1 → 1.0.8-1
• ros-noetic-costmap-cspace: 0.11.8-1 → 0.12.0-1
• ros-noetic-costmap-cspace-msgs: 0.8.0-1 → 0.12.0-1
• ros-noetic-cras-cpp-common: 2.0.10-2 → 2.1.2-1
• ros-noetic-cras-py-common: 2.0.10-2 → 2.1.2-1
• ros-noetic-cras-topic-tools: 2.0.10-2 → 2.1.2-1
• ros-noetic-depthai: 2.19.1-1 → 2.20.2-1
• ros-noetic-depthai-bridge: 2.5.3-1 → 2.6.1-2
• ros-noetic-depthai-examples: 2.5.3-1 → 2.6.1-2
• ros-noetic-depthai-ros: 2.5.3-1 → 2.6.1-2
• ros-noetic-depthai-ros-msgs: 2.5.3-1 → 2.6.1-2
• ros-noetic-diff-drive-controller: 0.21.0-1 → 0.21.1-1
• ros-noetic-dingo-control: 0.2.0-1 → 0.3.0-1
• ros-noetic-dingo-description: 0.2.0-1 → 0.3.0-1
• ros-noetic-dingo-msgs: 0.2.0-1 → 0.3.0-1
• ros-noetic-dingo-navigation: 0.2.0-1 → 0.3.0-1
• ros-noetic-effort-controllers: 0.21.0-1 → 0.21.1-1
• ros-noetic-eigenpy: 2.8.1-1 → 2.9.2-1
• ros-noetic-executive-smach: 2.5.0-1 → 2.5.1-1
• ros-noetic-force-torque-sensor-controller: 0.21.0-1 → 0.21.1-1
• ros-noetic-forward-command-controller: 0.21.0-1 → 0.21.1-1
• ros-noetic-four-wheel-steering-controller: 0.21.0-1 → 0.21.1-1
• ros-noetic-foxglove-bridge: 0.3.0-1 → 0.4.1-1
• ros-noetic-graceful-controller: 0.4.5-1 → 0.4.6-1
• ros-noetic-graceful-controller-ros: 0.4.5-1 → 0.4.6-1
• ros-noetic-gripper-action-controller: 0.21.0-1 → 0.21.1-1
• ros-noetic-imu-sensor-controller: 0.21.0-1 → 0.21.1-1
• ros-noetic-joint-state-controller: 0.21.0-1 → 0.21.1-1
• ros-noetic-joint-trajectory-controller: 0.21.0-1 → 0.21.1-1
• ros-noetic-joystick-interrupt: 0.11.8-1 → 0.12.0-1
• ros-noetic-lanelet2: 1.1.1-1 → 1.2.0-2
• ros-noetic-lanelet2-core: 1.1.1-1 → 1.2.0-2
• ros-noetic-lanelet2-examples: 1.1.1-1 → 1.2.0-2
• ros-noetic-lanelet2-io: 1.1.1-1 → 1.2.0-2
• ros-noetic-lanelet2-maps: 1.1.1-1 → 1.2.0-2
• ros-noetic-lanelet2-projection: 1.1.1-1 → 1.2.0-2
• ros-noetic-lanelet2-python: 1.1.1-1 → 1.2.0-2
• ros-noetic-lanelet2-routing: 1.1.1-1 → 1.2.0-2
• ros-noetic-lanelet2-traffic-rules: 1.1.1-1 → 1.2.0-2
• ros-noetic-lanelet2-validation: 1.1.1-1 → 1.2.0-2
• ros-noetic-laser-ortho-projector: 0.3.3-1 → 0.4.0-1
• ros-noetic-laser-scan-matcher: 0.3.3-1 → 0.4.0-1
• ros-noetic-laser-scan-sparsifier: 0.3.3-1 → 0.4.0-1
• ros-noetic-laser-scan-splitter: 0.3.3-1 → 0.4.0-1
• ros-noetic-map-organizer: 0.11.8-1 → 0.12.0-1
• ros-noetic-map-organizer-msgs: 0.8.0-1 → 0.12.0-1
• ros-noetic-message-filters: 1.15.15-1 → 1.16.0-1
• ros-noetic-microstrain-inertial-driver: 3.0.0-1 → 3.0.1-1
• ros-noetic-microstrain-inertial-examples: 3.0.0-1 → 3.0.1-1
• ros-noetic-microstrain-inertial-msgs: 3.0.0-1 → 3.0.1-1
• ros-noetic-microstrain-inertial-rqt: 3.0.0-1 → 3.0.1-1
• ros-noetic-ncd-parser: 0.3.3-1 → 0.4.0-1
• ros-noetic-neonavigation: 0.11.8-1 → 0.12.0-1
• ros-noetic-neonavigation-common: 0.11.8-1 → 0.12.0-1
• ros-noetic-neonavigation-launch: 0.11.8-1 → 0.12.0-1
• ros-noetic-neonavigation-msgs: 0.8.0-1 → 0.12.0-1
• ros-noetic-novatel-oem7-driver: 4.0.0-1 → 4.1.0-1
• ros-noetic-novatel-oem7-msgs: 4.0.0-1 → 4.1.0-1
• ros-noetic-obj-to-pointcloud: 0.11.8-1 → 0.12.0-1
• ros-noetic-paho-mqtt-c: 1.3.11-1 → 1.3.12-1
• ros-noetic-pinocchio: 2.6.14-1 → 2.6.17-1
• ros-noetic-planner-cspace: 0.11.8-1 → 0.12.0-1
• ros-noetic-planner-cspace-msgs: 0.8.0-1 → 0.12.0-1
• ros-noetic-polar-scan-matcher: 0.3.3-1 → 0.4.0-1
• ros-noetic-position-controllers: 0.21.0-1 → 0.21.1-1
• ros-noetic-pybind11-catkin: 2.5.0-1 → 2.10.3-2
• ros-noetic-rgbd-launch: 2.3.0-1 → 2.4.0-1
• ros-noetic-rm-common: 0.1.15-1 → 0.1.17-1
• ros-noetic-rm-control: 0.1.15-1 → 0.1.17-1
• ros-noetic-rm-dbus: 0.1.15-1 → 0.1.17-1
• ros-noetic-rm-gazebo: 0.1.15-1 → 0.1.17-1
• ros-noetic-rm-hw: 0.1.15-1 → 0.1.17-1
• ros-noetic-rm-msgs: 0.1.15-1 → 0.1.17-1
• ros-noetic-robotraconteur: 0.15.5-1 → 0.16.0-2
• ros-noetic-ros-comm: 1.15.15-1 → 1.16.0-1
• ros-noetic-ros-controllers: 0.21.0-1 → 0.21.1-1
• ros-noetic-ros-industrial-cmake-boilerplate: 0.3.1-1 → 0.4.0-1
• ros-noetic-rosbag: 1.15.15-1 → 1.16.0-1
• ros-noetic-rosbag-storage: 1.15.15-1 → 1.16.0-1
• ros-noetic-roscpp: 1.15.15-1 → 1.16.0-1
• ros-noetic-rosgraph: 1.15.15-1 → 1.16.0-1
• ros-noetic-roslaunch: 1.15.15-1 → 1.16.0-1
• ros-noetic-roslisp: 1.9.24-1 → 1.9.25-1
• ros-noetic-roslz4: 1.15.15-1 → 1.16.0-1
• ros-noetic-rosmaster: 1.15.15-1 → 1.16.0-1
• ros-noetic-rosmsg: 1.15.15-1 → 1.16.0-1
• ros-noetic-rosnode: 1.15.15-1 → 1.16.0-1
• ros-noetic-rosout: 1.15.15-1 → 1.16.0-1
• ros-noetic-rosparam: 1.15.15-1 → 1.16.0-1
• ros-noetic-rospy: 1.15.15-1 → 1.16.0-1
• ros-noetic-rosservice: 1.15.15-1 → 1.16.0-1
• ros-noetic-rostest: 1.15.15-1 → 1.16.0-1
• ros-noetic-rostopic: 1.15.15-1 → 1.16.0-1
• ros-noetic-roswtf: 1.15.15-1 → 1.16.0-1
• ros-noetic-rqt-joint-trajectory-controller: 0.21.0-1 → 0.21.1-1
• ros-noetic-rviz-satellite: 3.0.3-1 → 3.1.0-1
• ros-noetic-safety-limiter: 0.11.8-1 → 0.12.0-1
• ros-noetic-safety-limiter-msgs: 0.8.0-1 → 0.12.0-1
• ros-noetic-scan-to-cloud-converter: 0.3.3-1 → 0.4.0-1
• ros-noetic-scan-tools: 0.3.3-1 → 0.4.0-1
• ros-noetic-smach: 2.5.0-1 → 2.5.1-1
• ros-noetic-smach-msgs: 2.5.0-1 → 2.5.1-1
• ros-noetic-smach-ros: 2.5.0-1 → 2.5.1-1
• ros-noetic-topic-tools: 1.15.15-1 → 1.16.0-1
• ros-noetic-track-odometry: 0.11.8-1 → 0.12.0-1
• ros-noetic-trajectory-tracker: 0.11.8-1 → 0.12.0-1
• ros-noetic-trajectory-tracker-msgs: 0.8.0-1 → 0.12.0-1
• ros-noetic-velocity-controllers: 0.21.0-1 → 0.21.1-1
• ros-noetic-xmlrpcpp: 1.15.15-1 → 1.16.0-1

Removed Packages [0]:

Thanks to all ROS maintainers who make packages available to the ROS community. The above list of packages was made possible by the work of the following maintainers:

• Adam Serafin
• Atsushi Watanabe
• Bence Magyar
• Carlos
• Fabian Immel
• Gayane Kazhoyan
• Isaac I. Y. Saito
• Ivan Dryanovski
• Jan-Hendrik Pauls
• John Hurliman
• John Wason
• Joseph Duchesne
• Justin Carpentier
• Levi Armstrong
• Martin Pecka
• Masaru Morita
• Michael Carroll
• Michael Ferguson
• Michael Goerner
• Michael Ripperger
• NovAtel Support
• Piyush Khandelwal
• Qiayuan Liao
• Rob Fisher
• Robert Haschke
• Sachin Chitta
• Sachin Guruswamy
• Stefan Laible
• Tim Clephas
• Tony Baltovski
• Vincent Rousseau
• Wolfgang Merkt
• qiayuan
• sachin

[akrauch]

The new packages don’t seem to be available yet. Testing this with a ros:noetic-ros-base docker image, the added package ros-noetic-flatland is not found:

$ docker run -it --pull always  --rm ros:noetic-ros-base bash -c "apt update && apt-cache policy ros-noetic-flatland"
noetic-ros-base: Pulling from library/ros
Digest: sha256:6544ba22bf4108def2c59cdb4666a2c4078185797809ba439bfda18151da7e31
Status: Image is up to date for ros:noetic-ros-base
Get:1 http://archive.ubuntu.com/ubuntu focal InRelease [265 kB]
Get:2 http://security.ubuntu.com/ubuntu focal-security InRelease [114 kB]     
Get:3 http://packages.ros.org/ros/ubuntu focal InRelease [4679 B]                        
Get:4 http://packages.ros.org/ros/ubuntu focal/main amd64 Packages [763 kB]                          
Get:5 http://archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB]                           
Get:6 http://security.ubuntu.com/ubuntu focal-security/multiverse amd64 Packages [28.5 kB]
Get:7 http://archive.ubuntu.com/ubuntu focal-backports InRelease [108 kB]             
Get:8 http://security.ubuntu.com/ubuntu focal-security/universe amd64 Packages [1015 kB]         
Get:9 http://archive.ubuntu.com/ubuntu focal/restricted amd64 Packages [33.4 kB]      
Get:10 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages [11.3 MB]             
Get:11 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 Packages [1998 kB]                                   
Get:12 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages [2539 kB]       
Get:13 http://archive.ubuntu.com/ubuntu focal/multiverse amd64 Packages [177 kB]             
Get:14 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages [1275 kB]                   
Get:15 http://archive.ubuntu.com/ubuntu focal-updates/restricted amd64 Packages [2134 kB]     
Get:16 http://archive.ubuntu.com/ubuntu focal-updates/multiverse amd64 Packages [31.2 kB]
Get:17 http://archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages [1310 kB]
Get:18 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages [3014 kB]
Get:19 http://archive.ubuntu.com/ubuntu focal-backports/universe amd64 Packages [28.6 kB]
Get:20 http://archive.ubuntu.com/ubuntu focal-backports/main amd64 Packages [55.2 kB]
Fetched 26.4 MB in 5s (5045 kB/s)    
Reading package lists... Done
Building dependency tree       
Reading state information... Done
3 packages can be upgraded. Run 'apt list --upgradable' to see them.
N: Unable to locate package ros-noetic-flatland

[peci1]

You’re right, http://packages.ros.org/ros/ubuntu/pool/main/r/ros-noetic-flatland-viz returns 404.

The other added packages also aren’t available. However, packages from the recent Melodic sync are there.

[sloretz]

Looking into this now.

[nuclearsandwich]

Thanks for the reports. After the sync ran successfully, the job uploading the updated main repository to the primary ROS mirrors in OSUOSL failed. upload_main #272 [Jenkins]

Normally I see these failures, investigate, and resolve them without difficulty but I missed this one.
I’ve manually triggered a new upload and now it has completed upload_main #273 [Jenkins]

There is a secondary replication between OSUOSL mirrors which can become desynchronized as well and I lost some time because I investigated that first as the more common culprit rather than doing my diligence and checking that our upload reported successful first.

I’ve just checked all OSUOSL mirrors and the new packages appear to be everywhere now.