New packages and patch release for Jazzy Jalisco 2026-06-18

ROS ROS Announcements and News
, , ,
1

We’re happy to announce 97 new packages and 608 updates are now available on Ubuntu Noble on amd64 for Jazzy Jalisco.

This sync was tagged as jazzy/2026-06-18 .

:jazzy::jazzy::jazzy:

Package Updates for jazzy

Note that dbgsym packages have been filtered out from the list below

Added Packages [97]:

Updated Packages [608]:

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:

  • “Aarav Gupta”
  • “Adam Dabrowski”
  • “Adam Serafin”
  • “Aditya Pande”
  • “Alejandro Hernandez Cordero”
  • “Anas M’chichou”
  • “Bence Magyar”
  • “Bernd Pfrommer”
  • “Błażej Sowa”
  • “Carlos Mastalli”
  • “Chris Iverach-Brereton”
  • “Christian Eichmann”
  • “Christian Henkel”
  • “Christian Rauch”
  • “Christoph Hellmann Santos”
  • “Daan Wijffels”
  • “Daniel Trugman”
  • “David V. Lu!!”
  • “David Wong”
  • “Davide Faconti”
  • “Denis Stogl”
  • “Dharini Dutia”
  • “Emerson Knapp”
  • “Enrique Fernandez”
  • “Felix Exner”
  • “Felix Ruess”
  • “Fictionlab”
  • “Foxglove”
  • “Fumiya Watanabe”
  • “FusionCore”
  • “Geoffrey Biggs”
  • “Guilhem Saurel”
  • “Hilary Luo”
  • “Hung Pham”
  • “Husarion”
  • “Ivan Paunovic”
  • “Jacob Perron”
  • “Jian Kang”
  • “John Wason”
  • “Jonas Otto”
  • “Jose Luis Blanco-Claraco”
  • “Jose Mastrangelo”
  • “Jose-Luis Blanco-Claraco”
  • “Joseph Mirabel”
  • “José Luis Blanco-Claraco”
  • “Justin Carpentier”
  • “Kosuke Takeuchi”
  • “Kyoichi Sugahara”
  • “Lovro Ivanov”
  • “Luis Camero”
  • “Mamoru Sobue”
  • “Manan Kharwar”
  • “Marc Alban”
  • “Markus Bader”
  • “Marq Rasmussen”
  • “Masahiro Sakamoto”
  • “Matevz Morato”
  • “Maxime CLEMENT”
  • “Maxime Clement”
  • “Mete Fatih Cırıt”
  • “Mitsuhiro Sakamoto”
  • “Natesh Narain”
  • “Piotr Jaroszek”
  • “Ryohsuke Mitsudome”
  • “Satoshi OTA”
  • “Satoshi Ota”
  • “Southwest Research Institute”
  • “Stephen Williams”
  • “Taiki Tanaka”
  • “Takagi, Isamu”
  • “Takahiro Ishikawa-Aso”
  • “Takamasa Horibe”
  • “Takayuki Murooka”
  • “Takumi Odashima”
  • “Timo Röhling”
  • “Tom Moore”
  • “Tony Baltovski”
  • “Tyler Weaver”
  • “William Woodall”
  • “Xingang Liu”
  • “Yamato Ando”
  • “Yoshi Ri”
  • “Yuki Takagi”
  • “Yukihiro Saito”
  • “Yukinari Hisaki”
  • “Zulfaqar Azmi”
  • “amc-nu”
  • “bmagyar”
  • “mitsudome-r”
  • “xingang liu”
  • Adam Dabrowski
  • Addisu Z. Taddese
  • Aditya Pande
  • Alberto Tudela
  • Alejandro Hernandez Cordero
  • Alexey Merzlyakov
  • Audrow Nash
  • Automatika Robotics
  • Bence Magyar
  • Bernd Pfrommer
  • Brandon Ong
  • Brett Aldrich
  • Brian Wilcox
  • CNU Robotics CHRISLab
  • Carl Delsey
  • Carlos Orduno
  • Chris Lalancette
  • Christian Rauch
  • Christophe Bedard
  • David V. Lu!!
  • David Wong
  • Davide Faconti
  • Dharini Dutia
  • Esteve Fernandez
  • Felix Exner
  • Fictionlab
  • Foxglove
  • Gary Cross
  • Geoff Sokoll
  • Geoffrey Biggs
  • Gerardo Puga
  • Jacob Perron
  • Kenji Brameld
  • LibRealSense ROS Team
  • Maik Knof
  • Marc Alban
  • Matej Vargovcik
  • Max Schmeller
  • Michael Goerner
  • Michael Jeronimo
  • Michael Orlov
  • Michael v4hn Goerner
  • Miguel Ángel González Santamarta
  • Mohammad Haghighipanah
  • Nathan Dunkelberger
  • Nick Hortovanyi
  • Pyo
  • RAI Institute
  • ROS Tooling Working Group
  • Robert Haschke
  • Robotics and AI Institute LLC dba RAI Institute
  • STEREOLABS
  • Scott K Logan
  • Shane Loretz
  • Stefan Fabian
  • Steve Macenski
  • Steven Lovegrove
  • Steven! Ragnarök
  • Tomoya Fujita
  • Tully Foote
  • Vincent Rabaud
  • Víctor Mayoral-Vilches
  • bmagyar
  • geoff
  • steve

Enjoy!

:jazzy:

3 Likes
Preparing for Jazzy sync and patch release 2026-06-08
ROS News for the Week of June 22nd, 2026
ROS PMC Minutes for July 14, 2026
2

Question to the community: What is the recommended way of dealing with package sync when aiming to have a stabe base platform?

We use jazzy and rely on ROS packages. However, these syncs tend to break our system or at least the build when rolled out. The packages in the apt repo are updated without leaving the previous versions available, essentially forcing the new versions onto us. In this specific example the bump of `pinocchio` from 3.9 to 4.0 broke our build. From our investigation we noticed that the old version of the package in the apt repository are not available anymore, making it impossible for us to pin the version and decide the point in time when we want to migrate. Any system that claims to be production ready should definitely allow this kind of control, but until now it has evaded us how this is expected to be done with ROS2. Any insights are appreciated!

3

Search for snapshot repositories.

1 Like
4

I understand that the breaks can be a bit frustrating.

For a stable distribution like Jazzy, the maintainers treat the core packages (basically ros-desktop-full) as locked down for breaking changes and strive not to introduce ABI/API breaking changes into a released distribution.

However, the packages that are in the repository are a combination of the core packages and the whole ecosystem of packages contributed by people from the larger ecosystem. People who maintain these ecosystem packages may have their own opinions and strategies about how they maintain their software. It may be worth following up with the pinocchio maintainers on why they chose to bump a major version in the older LTS versions.

There are probably as many ways to manage this as there are organizations out there. There have been several ROSCon talks about ways of managing the software stack for production robots if you are interested. Broadly, the general guidance would fall in either the way @peci1 suggested above by creating a snapshot repository using a tool like aptly or if you are heavily dependent on a specific set of versions to build from source in that configuration.

5

For what it’s worth, the transition from Pinocchio 3.9 to 4.0 is pretty seamless, having gone through it myself. It’s mostly updating some deprecated headers / function calls that have been warning for a while.

6

Thank you for elaborating. For us it’s one of the many “surprising” angles of using ROS. As a software engineer at heart it gives me a headache if the default is to “update without user interaction”. It essentially means there is as many people out there as there are non-core packages that have the ability to impact our development by breaking our build system. I guess we’ll go in the route of using `aptly` or similar to have our own mirror. While building from source is an option, it is yet again more infrastructure to manage.

7

Thank you for your comment! I’m aware it is not very hard, especially as the maintainers provide a migration guide. The underlying issue here is that we cannot control it nor plan for it. The package sync is announced and then ~1-2 weeks later executed without a good communication mechanism. If I happen to not monitor this message board and compare it with all the packages that we use I’ll miss it, which then results in a broken build for us, forcing us to immediately focus on the issue. Something like a package upgrade is not something our engineering or wants to be forced to do unless it’s a CVE.

8

Have you thought about running CI against the testing repos? Those get the updates immediately, not waiting for syncs, so you’d catch the errors on time…

9

You can set Discourse to email you notifications when there is a new topic in just this category, which is specifically for announcements like sync announcements. You won’t get noise from the general category unless you watch that one as well.

  1. Either go to the category page and use the notification button in the top left (the little bell icon, usually), or go to your preferences page and select Tracking in the lower toolbar, and add the category to Watched.
  2. In your preferences page, select Email in the lower toolbar, and set “Email me when I am quoted…” to always.
10

I get that! I started getting back on this site more frequently because I was the person monitoring for syncs / breakages at my last 2 jobs :slight_smile: