Planet ROS

Planet ROS - http://planet.ros.org

Planet ROS - http://planet.ros.org http://planet.ros.org

ROS Discourse General: Better Console Logging

I have used ROS (1+2) for many years and also teached courses with it in university. Most students or people who used ROS for the first time have difficulties to find out what the problem is if their robot is not doing what they expected. When I was asked for help, I just scrolled through the terminal where they have executed their launch and in the vast majority of cases found the problem in a few seconds, because it was something simple like a node crashing on startup. Of course, there was an error message saying what the problem is, but somehow people new to ROS (even those with a lot of coding experience) had trouble seeing it. I also remember many times where it took me a lot of time to actually find a relevant output.
So what is the problem? I think there is just too much spam in the terminal output which makes it really hard to get an overview. In this post I would like to discuss different ways on how to improve this.
I know, that it is possible to use tools like rqt_console to better structure the logging output. But I think there are some good reasons why people sometimes rely on the terminal output:

See general error messages that are not ROS logging (e.g. exceptions from Python)
Get a quick feedback after “ros2 run” or “ros2 launch” without switching windows
Working without GUI, e.g. via SSH

To better visualize the problem look at this screenshot.

The first is the output of starting the logging_demo which just starts a single node that sends some logging messages. Half of the output does not provide information:

The log level is already reflected in the color, writing [Info] is redundant.
I have never used the timestamp in the terminal log for anything but it takes away a lot of space. I is also very hard to read as a human.
The node name can be important in some cases, to know where the message is coming from. However, in my experience, most of the time I already know based on the error message which node it is. Even if I am interested in it, I would like to read the messages first to see which are interesting.

It gets worse when we use launch, as we can see in the next screenshot.

Now launch adds another tag. This one is basically the same as the name of the node and does not provide any information. There are some cases where it does, but again in the majority of cases it is just spam. Another problem, in my oppinion, is that due to the different length of the node names, the start of the actual message on the horizontal axis does not align. This makes it already harder to read. In this example the length difference is not so large, it can be much worse.

So how can we improve this?

You can influence the behavior of the logging using the environment variable RCUTILS_CONSOLE_OUTPUT_FORMAT (see Logging and logger configuration — ROS 2 Documentation: Rolling documentation).
The default is “[{severity}] [{time}] [{name}]: {message}” and leads to outputs like above. We can easily change this to tackle the problems mentioned above. The output is much more readable in my opinion.

If we really need additional information, we can also put it after our message and the node name.

However, if we start something with launch, we will still end up with the extra tag that is introduced by launch.

Now we will have to get a bit more creative and use ANSI control sequences. (I also proposed to have an environment variable which lets you control the launch output but it has not been merged yet Add option to set output_format via environment variable by SammyRamone · Pull Request #713 · ros2/launch · GitHub. So in the future the following might not be necessary.)
ANSI control sequences allow you to manipulate the position of the cursor and how text is displayed. See ANSI escape code - Wikipedia for details on this. The short version is that we can use the character sequence “\x1b[” to initiate an ANSI control sequence. For example, we can use “\x1b[1k” to perform the “erase in line (EL)” command. Then we can do “\r” to move the cursor on the first position. Now we can just erase the launch tag infront of us. Now we get an output, which I find much easier to read.

We can also use this method to change how parts of the messages are displayed. This is especially interesting if we want to show additional information but still highlight the main message. For this we can use the ANSI “Select Graphic Rendition (SGR)” code. In this example, I made the message itself bold, the node name italic, and the additional information darker. Furthermore, the color based on the message type is only used for the message itself and not the additonal information. I added a dash infront of the message, which is helpful when using launch to differentiate messages from the nodes with messages from launch itself.

It is also possible to split one log into multiple lines. This leads to a clean look, but takes up more space.

By the way, you can also use these codes in the message itself. So if you want to send a message that blinks in the terminal, you can using “\x1b[6m”. Just beware that your message will look not so nice in rqt_consol or in a log file.

Here are some interesting codes
Newline: \n
Carriage return: \r
Delete everything until this point: \x1b[1k
Reset font to normal: \x1b[0m
Bold: \x1b[1m
Faint: \x1b[2m
Italic: \x1b[3m
Underline: \x1b[4m
Slow blink: \x1b[5m
Rapid blink: \x1b[6m

See also ANSI escape code - Wikipedia for more information and the color codes.

Some Tips:

Beware when stetting a foreground color, as it will override the colors for the different log levels. However, if you only set the color after displaying the message itself (e.g. to put the name where it came from in a different color), then it will work fine.
Don’t forget to reset any formatting changes with \x1b[0m or you might mess up any output that follows in the terminal
Put the settings for logging in your .bashrc or .zshrc so that they are automatically set for each terminal.

If you have any further tips or ideas on how to get a nicer terminal output, I would be interested in hearing it.

1 post - 1 participant

Read full topic

https://discourse.ros.org/t/better-console-logging/44012

ROS Discourse General: Cloudini: pointcloud compression for the rest of us

Hi,

I am please to announce the first decent release of Cloudini, the pointcloud compression library that you missed in your life.

The focus of this library is FAST compression and decompression, where the primary applications are:

decrease (sometimes dramatically) the dimension of your rosbags containing sensor_msgs/msg/PointCloud2
allow faster streaming over the network.
pay less the cloud provider that charge for the Gb…

What to expect

It is a lossy algorithm, but don’t you worry, you can customize the resolution. 1 mm? You will be good. Felling paranoid? Use 0.1 mm and you still get very good compression ratio.
Compression ratio in the dataset I used have a range from 0.15 to 0.5 of the original size (smaller is better).
Faster and better compression ratios than using LZ4 or ZSTD alone.
Yes, I did try Draco , and in my limited benchmarks, Cloudini as similar compression ratio but is considerably faster.
Preliminary implementation of point_cloud_transport plugins… but it needs more testing
Simple and small. Enjoy reading the code and learning how simple the algorithm is; I did try more complex ones from the literature, but the simplest performed better.

Do you want to test it RIGHT NOW?

Download the rosbag encode here and try encoding your own rosbag (MCAP required).

You may need to run:

chmod +x cloudini_rosbag_converter-*.AppImage

once to execute the file.

Then run:
./cloudini_rosbag_converter-v0.1.0-x86_64.AppImage -c -f your_own_rosbag.mcap -o encoded_bag.mcap

1 post - 1 participant

Read full topic

https://discourse.ros.org/t/cloudini-pointcloud-compression-for-the-rest-of-us/44009

ROS Discourse General: New Packages for Noetic 2025-05-29 - FINAL

We’re happy to announce 3 new packages and 94 updates are now available in ROS Noetic. This sync was tagged as noetic/2025-05-29.

This is the 89th, and (hopefully) final ROS Noetic sync.
We are no longer accepting releases into ROS Noetic. ROS Noetic officially goes end-of-life on May 31st.

ROS Noetic is the last supported ROS 1 release ROS: Upcoming ROS 1 End of Life
If ROS 1 has had a significant impact on you, and you’d like to say something about it, please do leave a review with your story here:

Package Updates for ROS Noetic - FINAL

Added Packages [3]:

ros-noetic-depth-image-publisher: 1.2.19-1
ros-noetic-emotion-analyzer: 2.1.31-4
ros-noetic-voicevox: 2.1.31-4

Updated Packages [94]:

ros-noetic-aques-talk: 2.1.28-1 → 2.1.31-4
ros-noetic-assimp-devel: 2.1.28-1 → 2.1.31-4
ros-noetic-audio-to-spectrogram: 1.2.17-2 → 1.2.19-1
ros-noetic-bayesian-belief-networks: 2.1.28-1 → 2.1.31-4
ros-noetic-bosch-locator-bridge: 1.0.13-1 → 1.0.14-2
ros-noetic-chaplus-ros: 2.1.28-1 → 2.1.31-4
ros-noetic-checkerboard-detector: 1.2.17-2 → 1.2.19-1
ros-noetic-collada-urdf-jsk-patch: 2.1.28-1 → 2.1.31-4
ros-noetic-dialogflow-task-executive: 2.1.28-1 → 2.1.31-4
ros-noetic-downward: 2.1.28-1 → 2.1.31-4
ros-noetic-dynamic-reconfigure: 1.7.5-1 → 1.7.6-1
ros-noetic-easy-markers: 0.3.0-1 → 0.3.1-1
ros-noetic-ff: 2.1.28-1 → 2.1.31-4
ros-noetic-ffha: 2.1.28-1 → 2.1.31-4
ros-noetic-gdrive-ros: 2.1.28-1 → 2.1.31-4
ros-noetic-google-chat-ros: 2.1.28-1 → 2.1.31-4
ros-noetic-google-cloud-texttospeech: 2.1.28-1 → 2.1.31-4
ros-noetic-imagesift: 1.2.17-2 → 1.2.19-1
ros-noetic-influxdb-store: 2.1.28-1 → 2.1.31-4
ros-noetic-joy-listener: 0.3.0-1 → 0.3.1-1
ros-noetic-jsk-3rdparty: 2.1.28-1 → 2.1.31-4
ros-noetic-jsk-pcl-ros: 1.2.17-2 → 1.2.19-1
ros-noetic-jsk-pcl-ros-utils: 1.2.17-2 → 1.2.19-1
ros-noetic-jsk-perception: 1.2.17-2 → 1.2.19-1
ros-noetic-jsk-recognition: 1.2.17-2 → 1.2.19-1
ros-noetic-jsk-recognition-msgs: 1.2.17-2 → 1.2.19-1
ros-noetic-jsk-recognition-utils: 1.2.17-2 → 1.2.19-1
ros-noetic-julius: 2.1.28-1 → 2.1.31-4
ros-noetic-julius-ros: 2.1.28-1 → 2.1.31-4
ros-noetic-kalman-filter: 0.3.0-1 → 0.3.1-1
ros-noetic-laser-filtering: 0.0.5-1 → 0.0.6-1
ros-noetic-libcmt: 2.1.28-1 → 2.1.31-4
ros-noetic-libsiftfast: 2.1.28-1 → 2.1.31-4
ros-noetic-lpg-planner: 2.1.28-1 → 2.1.31-4
ros-noetic-map-laser: 0.0.5-1 → 0.0.6-1
ros-noetic-map-msgs: 1.14.1-1 → 1.14.2-1
ros-noetic-message-filters: 1.17.3-1 → 1.17.4-1
ros-noetic-mini-maxwell: 2.1.28-1 → 2.1.31-4
ros-noetic-move-base-msgs: 1.14.1-1 → 1.14.2-1
ros-noetic-nfc-ros: 2.1.28-1 → 2.1.31-4
ros-noetic-opt-camera: 2.1.28-1 → 2.1.31-4
ros-noetic-osqp: 2.1.28-1 → 2.1.31-4
ros-noetic-pgm-learner: 2.1.28-1 → 2.1.31-4
ros-noetic-resized-image-transport: 1.2.17-2 → 1.2.19-1
ros-noetic-respeaker-ros: 2.1.28-1 → 2.1.31-4
ros-noetic-ros-comm: 1.17.3-1 → 1.17.4-1
ros-noetic-ros-emacs-utils: 0.4.17-1 → 0.4.18-1
ros-noetic-ros-google-cloud-language: 2.1.28-1 → 2.1.31-4
ros-noetic-ros-speech-recognition: 2.1.28-1 → 2.1.31-4
ros-noetic-rosbag: 1.17.3-1 → 1.17.4-1
ros-noetic-rosbag-snapshot: 1.0.5-1 → 1.0.6-1
ros-noetic-rosbag-snapshot-msgs: 1.0.5-1 → 1.0.6-1
ros-noetic-rosbag-storage: 1.17.3-1 → 1.17.4-1
ros-noetic-rosbaglive: 0.3.0-1 → 0.3.1-1
ros-noetic-roscpp: 1.17.3-1 → 1.17.4-1
ros-noetic-rosemacs: 0.4.17-1 → 0.4.18-1
ros-noetic-rosgraph: 1.17.3-1 → 1.17.4-1
ros-noetic-roslaunch: 1.17.3-1 → 1.17.4-1
ros-noetic-roslisp-repl: 0.4.17-1 → 0.4.18-1
ros-noetic-roslz4: 1.17.3-1 → 1.17.4-1
ros-noetic-rosmaster: 1.17.3-1 → 1.17.4-1
ros-noetic-rosmsg: 1.17.3-1 → 1.17.4-1
ros-noetic-rosnode: 1.17.3-1 → 1.17.4-1
ros-noetic-rosout: 1.17.3-1 → 1.17.4-1
ros-noetic-rosparam: 1.17.3-1 → 1.17.4-1
ros-noetic-rospatlite: 2.1.28-1 → 2.1.31-4
ros-noetic-rosping: 2.1.28-1 → 2.1.31-4
ros-noetic-rospy: 1.17.3-1 → 1.17.4-1
ros-noetic-rosservice: 1.17.3-1 → 1.17.4-1
ros-noetic-rostest: 1.17.3-1 → 1.17.4-1
ros-noetic-rostopic: 1.17.3-1 → 1.17.4-1
ros-noetic-rostwitter: 2.1.28-1 → 2.1.31-4
ros-noetic-roswtf: 1.17.3-1 → 1.17.4-1
ros-noetic-sesame-ros: 2.1.28-1 → 2.1.31-4
ros-noetic-slime-ros: 0.4.17-1 → 0.4.18-1
ros-noetic-slime-wrapper: 0.4.17-1 → 0.4.18-1
ros-noetic-sound-classification: 1.2.17-2 → 1.2.19-1
ros-noetic-switchbot-ros: 2.1.28-1 → 2.1.31-4
ros-noetic-system-fingerprint: 0.6.1-1 → 0.6.2-1
ros-noetic-topic-tools: 1.17.3-1 → 1.17.4-1
ros-noetic-trac-ik: 1.6.6-1 → 1.6.7-1
ros-noetic-trac-ik-examples: 1.6.6-1 → 1.6.7-1
ros-noetic-trac-ik-kinematics-plugin: 1.6.6-1 → 1.6.7-1
ros-noetic-trac-ik-lib: 1.6.6-1 → 1.6.7-1
ros-noetic-trac-ik-python: 1.6.6-1 → 1.6.7-1
ros-noetic-ur-calibration: 2.4.0-1 → 2.4.1-1
ros-noetic-ur-dashboard-msgs: 2.4.0-1 → 2.4.1-1
ros-noetic-ur-robot-driver: 2.4.0-1 → 2.4.1-1
ros-noetic-urdf-tutorial: 0.5.0-1 → 0.5.0-2
ros-noetic-webrtcvad-ros: 2.1.28-1 → 2.1.31-4
ros-noetic-wu-ros-tools: 0.3.0-1 → 0.3.1-1
ros-noetic-xmlrpcpp: 1.17.3-1 → 1.17.4-1
ros-noetic-zdepth: 2.1.28-1 → 2.1.31-4
ros-noetic-zdepth-image-transport: 2.1.28-1 → 2.1.31-4

Removed Packages [0]:

Thank you to every maintainer and contributor who made these updates available! This final sync was made possible by the work of the following maintainers:

David V. Lu!!
Felix Exner
Gayane Kazhoyan
Hitoshi Kamada
Iori Yanokura
Kei Okada
Michael Carroll
Moju Zhao
Naoya Yamaguchi
Ryohei Ueda
Sam Pfeiffer
Shingo Kitagawa
Stefan Laible
TRACLabs Robotics
Takuya Nakaoka
Yohei Kakiuchi
Youhei Kakiuchi
Yuki Furuta
Yuto Inagaki
k-okada

Thank you

I also want to say thank you to all 315 maintainers who made 3264 releases during the last 5 years. Thanks to you ROS Noetic is finishing its final sync with 2175 packages.

Thank you for choosing to spend your time and energy maintaining open source robotics software. You didn’t have to do that. Your hard work is what made ROS Noetic possible.

Achille Verheye
Adam Allevato
Adam Serafin
ad-daniel
Addisu Z. Taddese
Adrian Macneil
adrisubi
Affonso, Guilherme
Akshit
Alejandro Hernández Cordero
Aleksander Szymański
Alexander Gutenkunst
Alexander Rössler
Alexander Tiderko
Alexander Winkler
Alex Moriarty
alf767443
anastasispk
Andrea Burani
Andrei Vukolov
AndyZe
anilsripadarao
Anqi Xu
Arne Hitzmann
Atsushi Watanabe
Austin
Autonics-lidar
BarisYazici
Beau Colley-Allerton
Bence Magyar
Benjamin Hug
Benjamin Thiemann
Berscheid
Blaine Miller
Błażej Sowa
Boitumelo Ruf
Boston Cleek
Braden McDorman
Brenden Gibbons
brenden-square
Brennan Cain
Catherine Wong
cdoehn
Chris Iverach-Brereton
Chris Lalancette
Chris Thierauf
Christian Joseph Acar
Christian Rauch
Christopher Berner
Christoph Rösmann
CLOBOT
cubicleguy
cwbollinger
Daisuke Nishimatsu
Daisuke Sato
Daniel Bargmann
Daniel Claes
Daniel Koch
Daniel Stonier
Darko Lukić
Dave Feil-Seifer
David Anthony
Davide Faconti
Davide Torielli
David Fischinger
David Mansolino
David V. Lu!!
dcconner
deadln
Devanshu Sharma
Dima Dorezyuk
Dirk Thomas
Dominik Kleiser
doronhi
Dr. Konstantin Schauwecker
duguguang
EclOutsight
Ed Venator
Elisa Tosello
Eric Relson
Erki Suurjaak
Esteve Fernandez
Eurico F. Pedrosa
Evan Flynn
Fabian Immel
Fabien Spindler
Fares Abawi
Felipe Gomes de Melo
Felix Exner
Felix Exner (fexner)
Felix Messmer
Felix Ruess
Florencia Grosso
Florian Rothmeyer
Florian Walch
Fotios Papadopoulos
fpasch
Franz
frcini
fsuarez6
Gal Gorjup
Gaurav Gupta
G.A. vd. Hoorn
Gayane Kazhoyan
GDqbrobotics
Geoffrey Biggs
George Stavrinos
Gonzalo Mier
guanfengliu
Guglielmo Gemignani
Guilhem Saurel
Hadi Tabatabaee
Hans-Joachim Krauch
Hiroki Matsui
Hunter L. Allen
icolwell-as
Ilija Hadzic
Immanuel Martini
immel-f
Isaac I.Y. Saito
Isaac Saito
Ivan Santiago Paunovic
JackFrost67
Jacob Bandes-Storch
Jacob Perron
Jafar
Jafar Abdi
Jamila Macagba
Janez Cimerman
Jean-Pierre Busch
Jeroen
Jihoon Lee
Jiri Hörner
joel-mb
Johannes Meyer
John Hurliman
John Stechschulte
John Wason
Jonathan Binney
Jorge Beltrán de la Cita
Jose Luis Blanco-Claraco
Jose Luis Rivero
José Manuel González Marín
Joseph Duchesne
Joshua Whitley
Junya Hayashi
Kamal Mohy El Dine
Karsten Knese
Kei Okada
Kenji Brameld
Kenji Brameld (TRACLabs)
Kevin Hallenbeck
Leandro
lebarsfa
Lennart Puck
Lennart Reiher
Levi Armstrong
Louise Poubel
Mabel Zhang
maiertopo
Marc Alban
Marco
Marina Moreira
Mark Moll
Mark Naeem
Marko Bjelonic
Markus Bader
Martin Günther
Martin Pecka
Mathias Lüdtke
matlabbe
Matthias Gruhler
Matthijs van der Burgh
Matt Vollrath
Maxime Busy
Max Schwarz
maxzieba
MHD ALI ALSHIKH KHALIL
Michael Carroll
Michael Ferguson
Michael Görner
Michael Jeronimo
Michael Lehning
Michael Lohrer
Michael Ripperger
Michael Zemb
Michel Hidalgo
Micho Radovnikovich
Mikael Arguedas
Mike Karamousadakis
Mike Purvis
mikramarc
MIURA Yasuyuki
mlione
MoffKalast
Nahuel Espinosa
Nick Lamprianidis
Nickolay V. Shmyrev
Nick Walker
Niels Hvid
Nikhil Khedekar
Nisici
Noel Jiménez García
NovAtel Applications Engineering
nrotella-ainstein
Olivier Kermorgant
Olivier Michel
Pablo Iñigo Blasco
pantor
pariaspe
Patrick
Patrick Geneva
Paul Bovbel
peichto
Peter Mitrano
Peter Weissig
Philipp Schillinger
Philipp Tenbrock
pietrocolombo
Piotr Szlachcic
P. J. Reed
poggenhans
Pradheep Krishna
Praveen Palanisamy
Priyanka Chowdhury
Pyo
QiayuanLiao
Quentin Torgerson
Raebel Christo S J Johney
Rafael Luque
Ralph Lange
Rein Appeldoorn
rfeistenauer
Rob
robbiefish
Robert Haschke
RobertWilbrandt
ROBOTIS-Ashe
Rohan Agrawal
Roland Arsenault
Romain Reignier
Roman Fedorenko
rorosi
Ross Taylor
rostest
Rousseau Vincent
Ryohei Ueda
Ryo Koyama
Sachin Guruswamy
SagarWalishetti
Sai Kishor Kothakota
Sam Pfeiffer
Samuel Bachmann
Scott K Logan
Sean Kelly
Sebastian Pütz
septentrio-users
Séverin Lemaignan
Shane Loretz
Shengye Wang
Sheung Ying Yuen-Wille
Shingo Kitagawa
Shota Aoki
Shreyas Gokhale
Simon Gabl
smoker771
sqbot
Stefan Fabian
Stefan Laible
Stefan May
Stefano Dell’Orto
Stefan Scherzinger
Stephen Hart
Steve Macenski
Steven! Ragnarök
Takashi Ogura
tarasborov
Teshan Shanuka J
Thomas Böhm
Thomas Hauth
Thomas Molnar
Thomas PEYRUCAIN
Thore Goll
Tibor Dome
Tim Clephas
Timo Röhling
Tobias Roth
tolesam
Tom Moore
Tony Baltovski
torydebra
Toship
Toshiya Nakakura
Tully Foote
Tyler Weaver
umbertofontana93
Vatan Aksoy Tezer
Veronika Podliesnova
Victor Lopez
Victor Paléologue
Vladimir Ermakov
Wang DeYou
William Woodall
Will Son
Wolfgang Merkt
xfealal
Yannick Goumaz
Yk
Yoshito Okada
youliang
Yuki Igarashi
Yutaka Kondo
YuuinIH
Zach LaCelle
Zheng Qu

Thank you.

Your friendly ROS Noetic ROS Boss (for two more days),
Shane

3 posts - 3 participants

Read full topic

https://discourse.ros.org/t/new-packages-for-noetic-2025-05-29-final/44003

ROS Discourse General: ROS users meet up at VivaTech/NVIDIA GTC Paris

Paris is the Place to Be in Europe soon!

Two exciting events are just around the corner:

VivaTech: June 11–14
NVIDIA GTC: June 10–12

Who’s attending and up for a drink or meet-up? Let’s connect!

1 post - 1 participant

Read full topic

https://discourse.ros.org/t/ros-users-meet-up-at-vivatech-nvidia-gtc-paris/43994

ROS Discourse General: ROSCon 2025 Sponsors + CFP Reminder

ROSCon 2025 Sponsors and CFP Reminder

Hi everyone, a quick update on ROSCon 2025 in Singapore. We just posted an update to the ROSCon website that includes our first batch of ROSCon sponsors. In the next few weeks we plan to announce our 2025 workshop schedule and open up registration. Most importantly, thereâ€™s less than four days remaining to submit your ROSCon 2025 talk proposals, they are due 2025-06-02T07:00:00Z UTC.

Sponsorship

The generous support of our sponsors makes ROSCon possible! I am happy to announce that we have closed our first batch of sponsorships for ROSCon 2025. We had an overwhelming demonstration of support from our community for ROSCon 2025. If your organization is interested in sponsoring ROSCon there are still some sponsorship options available including Platinum sponsorship and our diversity scholars program! You can find all the details in the ROSCon 2025 prospectus, or by simply e-mailing us at roscon-2025-ec@openrobotics.org.

Now, without further ado, here are your ROSCon 2025 sponsors:

Gold Sponsors

Silver Sponsors

Bronze Sponsors

Startup Alley Sponsors

Kinisi Robotics

Video Archive and Live Stream Sponsor

Refreshment Sponsors

Lunch Sponsors

Intrinsic

Diversity Scholarship Sponsors

1 post - 1 participant

Read full topic

https://discourse.ros.org/t/roscon-2025-sponsors-cfp-reminder/43990

ROS Discourse General: 👉 REMINDERS: ROSCon & ROSCon UK CFP / ROS Meetup Edinburgh & Singapore / Open Hardware Summit

REMINDERS: ROSCon & ROSCon UK CFP / ROS Meetup Edinburgh & Singapore / Open Hardware Summit

Hi Everyone,

We’re in the thick of ROSCon(s) CFP season. I wanted to post a couple of quick reminders about ROSCon and other upcoming events. If you are unsure about submitting a ROSCon talk proposal my advice is as follows, “Don’t self censor, let the review panel make that call for you!” We absolutely want new and first time speakers at each and every ROS events.

Here is a run down of upcoming deadlines:

TODAY – 2025-05-28 Gazebo Community Meeting on MicroMouse Simulation
TODAY – 2025-05-28 Singapore ROS Meetup
TOMORROW – 2025-05-29 Edinburgh Hardware Happy Hour and Edinburgh Robotics Meetup & ROS 1 Wake
TOMORROW – 2025-05-29 ROS Meetup Barcelona
FRIDAY 2025-05-30 => 2025-05-31 2025 Open Hardware Summit in Edinburgh – Discounted tickets with the code “LocalHacker”.
SATURDAY 2025-05-31 ROS Noetic End-of-Life
MONDAY 2025-06-02 ROSCon 2025 Talk Submission Deadline
2025-06-04 NYC ROS Meetup with New York Tech Week!
2025-06-09 ROSCon UK CFP DEADLINE

1 post - 1 participant

Read full topic

https://discourse.ros.org/t/reminders-roscon-roscon-uk-cfp-ros-meetup-edinburgh-singapore-open-hardware-summit/43969

ROS Discourse General: Logging and Observability Discussion Preparation | Cloud Robotics WG Meeting 2025-06-02

The next meeting for the Cloud Robotics Working Group will be at 2025-06-02T16:00:00Z UTCâ†’2025-06-02T17:00:00Z UTC, where we will prepare for a discussion on Logging and Observability. The goal is to publish a community guide on Logging and Observability in Cloud Robotics. We will pool our knowledge, come up with the questions we need to answer, and think of experts we can bring in to get the best possible information for the guide.

Logging and Observability was our highest priority guide according to community poll. For more information, take a look at the announcement blog post.

Last meeting, we came up with a list of community guides that could be published on the Cloud Robotics Hub. If you would like to see the meeting, the recording is available on YouTube.

The meeting link is here, and you can sign up to our calendar or our Google Group for meeting notifications or keep an eye on the Cloud Robotics Hub.

Hopefully we will see you there!

1 post - 1 participant

Read full topic

https://discourse.ros.org/t/logging-and-observability-discussion-preparation-cloud-robotics-wg-meeting-2025-06-02/43968

ROS Discourse General: ROS Deliberation Community Group Meeting - June 2, 2025

The next ROS Deliberation Community Group meeting will be on 2025-06-02T15:00:00Z UTC.

Google Meet link: https://meet.google.com/njs-ieym-dgk

Agenda:

Scenario Execution for Robotics, by Florian Mirus and Frederik Pasch
FlexBE: ROS 2 status and ongoing work towards state machine synthesis, by David Conner

Feel free to propose additional agenda items, join the mailing list, or the Discord server.

- Sebastian

1 post - 1 participant

Read full topic

https://discourse.ros.org/t/ros-deliberation-community-group-meeting-june-2-2025/43947

ROS Discourse General: Boston Robot Hackers first meeting tomorrow - You are invited!

Calling All Robot Enthusiasts!
Join the first meeting of Boston Robot Hackers (BRH) - a new community for ROS and robotics builders on the US East Coast. Whether you are a developer, researcher, or hobbyist, your voice and ideas are welcome!

When: Tomorrow, May 27, 2025 @ 1:30 PM EST
Zoom: LinkedIn
RSVP: LinkedIn

Letâ€™s collaborate, learn, and build the future of robotics - together!

Huge thanks to @pitosalas for taking the initiative and helping bring this to life. We hope BRH becomes a space where like-minded folks can connect, share guidance, and accelerate the positive impact of robotics on society.

7 posts - 4 participants

Read full topic

https://discourse.ros.org/t/boston-robot-hackers-first-meeting-tomorrow-you-are-invited/43941

ROS Discourse General: ROS signing key migration guide

We are again upon the brink of the ROS signing key expiration (June 1st) and from the Infrastructure PMC we are happy to announce a new package for ROS key and repository management.
The set of packages ros-apt-source and ros2-apt-source for Ubuntu and ros2-release for RHEL provide both the signing key and the repository configuration for ROS and ROS 2 .

This a big step towards a simpler key update path allowing the ROS project to rotate keys while keeping ROS users in sync as long as the they keep their system up to date! From a security stand-point, having the ability to rotate keys without breaking ROS users has been a longtime goal for the Infrastructure PMC and this is the first step towards it.

The are two flavors of the package for Ubuntu/Debian distributions:

ros-apt-source and ros2-apt-source: provides key and repository configuration for ROS and ROS 2 main repositories (http://packages.ros.org/ros, http://packages.ros.org/ros2) correspondingly.
ros-testing-apt-source and ros2-testing-apt-source : provides key and repository configuration for ROS and ROS 2 testing repositories (http://packages.ros.org/ros-testing,http://packages.ros.org/ros2-testing) correspondingly.

For RHEL there is a single package ros2-release that configures both main and testing repositories and enables the main repository as the default behavior.

How to migrate (before June 1st)

Given a setup that has the ros key and repository configuration following the former installation steps, you need to perform the following steps

Ubuntu/Debian

Install new package using the previous repository configuration

# if ROS 1 
sudo apt update && sudo apt install ros-apt-source

# if ROS 2 
sudo apt update && sudo apt install ros2-apt-source

Remove old repository configuration files otherwise apt will be broken due to key conflict (these files might be different in your system if you did not follow the installation steps):

# If using ROS 1
sudo rm /etc/apt/sources.list.d/ros-latest.list
sudo apt-key del "C1CF 6E31 E6BA DE88 68B1  72B4 F42E D6FB AB17 C654"

# If using ROS 2
sudo rm /etc/apt/sources.list.d/ros2.list
sudo rm /usr/share/keyrings/ros-archive-keyring.gpg

Test that packages are still discovered and thus installable:

sudo apt update
sudo apt search ^package_name (for example ros-rolling-desktop-full)

RHEL

Install new package

sudo dnf install ros2-release

Due to name conflict you will see that the new configuration is created under /etc/yum.repos.d/ros2.repo.rpmnew
Replace the old configuration with the new one :

sudo rm /etc/yum.repos.d/ros2.repo 
sudo mv /etc/yum.repos.d/ros2.repo.rpmnew /etc/yum.repos.d/ros2.repo

Test that packages are still discovered and thus installable:

sudo dnf update 
sudo dnf search package_name #for example ros-rolling-desktop

How do I migrate (after June 1st)?

There are two ways you can get the new package after June 1st:

Update manually to the new key and run the migration guide above. To get the updated key run:

sudo rm /usr/share/keyrings/ros-archive-keyring.gpg
sudo curl -sSL https://raw.githubusercontent.com/ros/rosdistro/master/ros.key -o /usr/share/keyrings/ros-archive-keyring.gpg

Remove the previous configuration by running the following commands and follow the new installation instructions for your ROS distribution.

# If using ROS 1
sudo rm /etc/apt/sources.list.d/ros-latest.list
sudo apt-key del "C1CF 6E31 E6BA DE88 68B1  72B4 F42E D6FB AB17 C654" # This is the old key fingerprint, you should see by running apt-key list 
# If using ROS 2
sudo rm /etc/apt/sources.list.d/ros2.list 
sudo rm /usr/share/keyrings/ros-archive-keyring.gpg

FAQ

Does it support ROS 1?
The package supports both ROS 1 and ROS 2 for the declared supported platforms on REP-2000. The list of ROS-OS pairs supported can be found here.
What happens if I want to use a mirror of packages.ros.org?
For debian based systems (Ubuntu, Debian)
The package configures the source on etc/apt/sources.list.d/ directory but does not set a preference file. It’s possible to add an additional source file (copying from the one provided by the package and modifying the source) that configures a different repository (the mirror url) with a higher preference (See apt_preferences documentation) so that packages are being sourced from the mirror.
I have already downloaded the package for the tutorial party/kilted testing, do I need to do anything else?
If you downloaded the package for the release party then you have the testing repository configured. You will need to:

Debian
```
sudo apt remove ros2-testing-apt-source
```
Follow the instructions to setup from scratch Ubuntu (deb packages) — ROS 2 Documentation: Kilted documentation

RHEL

In RHEL the package configures both repositories, you will need to disable the ros2-testing repo and enable the main one
```
sudo dnf config-manager --disable ros2-testing
sudo dnf config-manager --enable ros2
```
Can I still source the key the old way?
Even though this is the new recommended way of getting the ROS key it does not prevent ROS users from using the previous way of setting up ROS repositories. The goal of this package is to provide an ergonomic way of configuring ROS repositories and an improved update pathway.

There is still some pending work to update the installation instructions across the docs that will be addressed during this week as well as updates to the key hosted on rosdistro repository and packages.ros.org, but we encourage you to start the migration as soon as possible.

As always feel free to ask questions here or in the #infra-help channel on Discord.

21 posts - 8 participants

Read full topic

https://discourse.ros.org/t/ros-signing-key-migration-guide/43937

ROS Discourse General: Issues After Migrating to ROS 2 Jazzy: RViz Icons and Mesh Loading

Hi everyone,

I recently migrated to ROS 2 Jazzy and I’m encountering two issues that I haven’t been able to resolve:

1. RViz2 Icon Loading Errors

When I launch RViz2, I get several errors related to loading icons. The log shows messages like:

[rviz2-3] [ERROR] [...]: Could not load pixmap package://rviz_common/icons/rotate.svg -- using default cursor instead.
[rviz2-3] [ERROR] [...]: Could not load pixmap package://rviz_common/icons/rotate_cam.svg -- using default cursor instead.
[rviz2-3] [ERROR] [...]: Could not load pixmap package://rviz_common/icons/move2d.svg -- using default cursor instead.
[rviz2-3] [ERROR] [...]: Could not load pixmap package://rviz_common/icons/zoom.svg -- using default cursor instead.
[rviz2-3] [ERROR] [...]: Could not load pixmap package://rviz_common/icons/crosshair.svg -- using default cursor instead.

RViz still works, but all cursors appear as default.

2. URDF Mesh File Not Found

When I launch my robot description, I get an error saying it cannot find the .stl mesh files, even though they are correctly placed in the install directory.

In my URDF I use the following line:

<mesh filename="file://$(find niryo_robot_description)/urdf/ned3/stl/ned3_pro_shoulder_assembly.stl"/>

Is there any change in how ROS 2 Jazzy handles resource paths or mesh loading? Any advice on how to fix these two issues would be greatly appreciated.

Thanks in advance!

Jaime

8 posts - 2 participants

Read full topic

https://discourse.ros.org/t/issues-after-migrating-to-ros-2-jazzy-rviz-icons-and-mesh-loading/43935

ROS Discourse General: ROS News for the Week of May 19th, 2025

ROS News for the Week of May 19th, 2025

Kilted Kaiju is here

! I am writing the news from a very busy Waffle House in downtown

Atlanta (I’ m here for ICRA). As the nice lady behind the counter just told me, “team work makes the dream work!” We want to thank the hundreds of people who made this release possible!

Speaking of Atlanta, we had an absolutely amazing ROS 2 Kilted Kaiju release party at ICRA in Atlanta thanks to the support of our friends at Intrinsic, Foxglove, and PAL Robotics (our newest OSRA member)! Big shout out to the 300 or so people who showed up!

The festivities continue into next week including our Singapore ROS Meetup, our Edinburgh Hardware Happy Hour, Edinburgh robotics meetup ROS 1 wake, a ROS meetup in Barcelona, and Open Hardware Summit in Edinburgh.

ROSCON 2025 TALK PROPOSALS ARE DUE IN 11 DAYS

Events

News

ROS

Got a Minute?

Our colleagues over at MoveIt could use some help!

1 post - 1 participant

Read full topic

https://discourse.ros.org/t/ros-news-for-the-week-of-may-19th-2025/43903

ROS Discourse General: :kilted: ROS 2 Kilted Kaiju Release!

ROS 2 Kilted Kaiju Release!

Happy World Turtle Day! Today the ROS 2 Release Team is happy to announce the eleventh release of ROS 2: Kilted Kaiju (codenamed Kilted).

In addition to the official logo shared previously, we also have a new Kilted Kaiju turtlesim and Discourse icon :kilted:. Our Kilted T-shirt and swag campaign is still live! You can still grab all the cool merch if you want to support the release. All proceeds help support the Open Source Robotics Foundation (OSRF).

Kilted Kaiju is a regular release that will be supported until November 2026. The distribution is primarily supported on the following platforms:

Tier 1 platforms:
- Ubuntu 24.04 (Noble): amd64 and arm64
- Windows (Visual Studio 2019): amd64
Tier 2 platforms:
- RHEL 9: amd64
Tier 3 platforms:
- macOS: amd64
- Debian Bookworm: amd64

For more information about RMW implementations, compiler/interpreter versions, and system dependency versions please see REP-2000.

If you are new to ROS, we recommend trying Kilted Kaiju on a Tier 1 supported platform. Check the installation instructions and tutorials on docs.ros.org, and give Kilted a spin!

Should you run into any difficulties, please ask a question on ROS Stack Exchange. If you would like to try Kilted but are afraid of commitment you can find Kilted Docker containers on Docker Hub shortly. Open Container Initiative Kilted Kaiju images are also available from Shane Loretz Github repository.

New Features and Enhancements

Kilted Kaiju is feature packed and full of improvements! If you want the gritty details feel free to peruse the release notes and changelog for core ROS 2 packages. We’ve summarized a few new features we’ll think you’ll love below.

Tier 1 RMW Zenoh Support

ROS 2 Kilted Kaiju is our first ROS 2 release to support Eclipse Zenoh as a Tier 1 middleware! What do we mean by Tier 1 middleware? A Tier 1 middleware supports all of the listed Tier 1 operating systems for that particular ROS release, and we verify that support with a full battery of tests that run daily. Moreover, each Tier 1 middleware supports a full SROS2 security suite that includes access control, authentication, and encryption tools. We also require that all Tier 1 middlewares support all of the Tier 1 code quality requirements defined in REP-2004 and be included in the core ROS packages as listed in REP-2005. To learn more about the Eclipse Zenoh RMW please visit the following resources.

Eclipse Zenoh is not yet the default RMW in Kilted Kaiju. If you want to take Zenoh out for a test drive you’ll need to swap out your RMW implementation using the following tutorial.

Python Improvements

There are two big improvements to our Python client library (rclpy) available in Kilted Kaiju. The first one is extended Python type checking support, particularly for Python actions and Python generics (compound types such as list[str]). These changes can be found in RCLPy #1349. To ease Python type checking you may want to familiarize yourself with our ament_mypy tool and its relevant documentation.

Thanks to a community member porting the events executor from rclcpp to Python, performance in ROS 2 Kilted Kaiju has also significantly improved. Some rudimentary benchmarks indicate that these speed ups could be as much as 10 times! You’ll need to opt-in to the new executor to see the performance improvement by adding the following to your rclpy.spin command:

rclpy.spin(my_node, rclpy.experimental.EventsExecutor)

Action Introspection

Ever wonder about the status of your action server? Using the new action introspection CLI command you can interrogate your action server from the command line with the action echo command! This new command will show you the current state of your action. The best part? This action status information is also available within your ROS Bags!

New ROSBag Features

Kilted Kaiju has a laundry list of new ROSBag features that will greatly improve the lives of ROS users. A huge improvement for the ROSBag user experience is support for playing multiple bags! You can now replay multiple bag filess with a single command line call.

ros2 bag play -i bag1 -i bag2 -i bag3 [storage_id]

Another bag playback usability improvement is a progress bar that lets you interactively execute, view and control your bag(s) playback. You can check out a video of the progress bar here.

In Kilted Kaiju, ROSBag now has its own first class action server that lets you trigger recording of a bag file by calling an action. We like to think of this feature as a system snapshot mode that lets you log a new behavior for easy debugging.

The ROSBag command also supports four new flags to help you better filter and order the replay of your data. These new flags include:

A message chronology filter, –message-order, that lets you choose between the time messages were sent or received.
A sorting utility, —sort, that lets you sort topics, services and actions by name, topic type, and number of recorded messages.
Ever wondered why your bag file was so big? Our new –size-contribution filter lets you see the amount of data contributed by each topic.
Is log data spoiling your bag file? Trying to track down a bug? Our new –log-level command lets you set the playback log level of your bag.

Better Windows Experience

Windows 11 is here, and we’re working towards a better ROS user experience for Windows 11 users in our planned 2026 “L Turtle” release. A big step in the right direction is a new way to install ROS on Windows. ROS 2 Kilted Kaiju now uses Pixi (prefix.dev) and Conda as the default Windows installation mechanism. This approach has number of advantages:

easier dependency management,
a simplified installation process,
workspace-level installation (vs. global), and
a lower maintainer burden.

Install: bit.ly/KiltedOnWindows

Miscellaneous Features

Kilted Kaiju now supports NV12 in common interfaces! What is NV12? It is a common and efficient way of encoding image data using the YCbCr approach. The format is commonly used by hardware devices like cameras and graphics cards, and many devices have built-in acceleration support for it. This can potentially improve image processing and transport speeds.

A Community Effort

ROS 2 is truly a community effort, and this could not have been better exemplified by our public beta testing of Kilted Kaiju over the past few weeks. Almost 545 test cases were put through the ringer with several improvements identified along the way. It really helped “harden” the Kilted distribution. The release team would like to extend a heartfelt thank you to all testers. For our top twenty testers you should get an e-mail in your inbox with a swag coupon code sometime later next week. A full list of our testers and the number of issues they tested:

Finally, we’d like to announce the name of the next ROS 2 release for May 2026:

Lyrical Luth

15 posts - 13 participants

Read full topic

https://discourse.ros.org/t/ros-2-kilted-kaiju-release/43902

ROS Discourse General: Open-source, low-cost precision tactile sensing

Hey robot makers! My nameâ€™s Charlie and I work as an embedded engineer at Touchlab. I thought Iâ€™d reach out as Iâ€™m keen on getting involved in general robotics chats along with answering any questions people have about tactile sensing/what Touchlab is getting up to.

Please excuse theðŸ”Œbut Iâ€™d love to hear your thoughts:
Want to get in on some top-secret tech? Weâ€™re opening up access to Touchlabâ€™s popular, cutting-edge Triaxial sensors (a low-cost, multi-dimensional tactile solution usually reserved for our exclusive projects) to the wider public. Got a minute to share your thoughts in our quick questionnaire and help shape the future of precision sensing in two-finger grippers? Fill out this form for a chance to win some of our sensors (and maybe even some swag)!

If youâ€™d prefer not to fill out forms (I donâ€™t blame you one bit), pls let me know your general thoughts in this thread instead <3

My DMs are also always open for a chat!

1 post - 1 participant

Read full topic

https://discourse.ros.org/t/open-source-low-cost-precision-tactile-sensing/43901

ROS Discourse General: New Packages for Jazzy Jalisco 2025-05-23

Hello there everyone!

We’re happy to announce 55 new packages and 414 updates are now available in ROS 2 Jazzy Jalisco .

This sync was tagged as jazzy/2025-05-23 .

Package Updates for jazzy

Added Packages [55]:

ros-jazzy-autoware-utils: 1.4.1-1
ros-jazzy-autoware-utils-debug: 1.4.1-1
ros-jazzy-autoware-utils-diagnostics: 1.4.1-1
ros-jazzy-autoware-utils-diagnostics-dbgsym: 1.4.1-1
ros-jazzy-autoware-utils-geometry: 1.4.1-1
ros-jazzy-autoware-utils-geometry-dbgsym: 1.4.1-1
ros-jazzy-autoware-utils-logging: 1.4.1-1
ros-jazzy-autoware-utils-logging-dbgsym: 1.4.1-1
ros-jazzy-autoware-utils-math: 1.4.1-1
ros-jazzy-autoware-utils-math-dbgsym: 1.4.1-1
ros-jazzy-autoware-utils-pcl: 1.4.1-1
ros-jazzy-autoware-utils-rclcpp: 1.4.1-1
ros-jazzy-autoware-utils-system: 1.4.1-1
ros-jazzy-autoware-utils-system-dbgsym: 1.4.1-1
ros-jazzy-autoware-utils-tf: 1.4.1-1
ros-jazzy-autoware-utils-uuid: 1.4.1-1
ros-jazzy-autoware-utils-visualization: 1.4.1-1
ros-jazzy-autoware-utils-visualization-dbgsym: 1.4.1-1
ros-jazzy-broll: 0.1.0-1
ros-jazzy-broll-dbgsym: 0.1.0-1
ros-jazzy-ffw-bringup: 1.0.5-1
ros-jazzy-ffw-description: 1.0.5-1
ros-jazzy-ffw-joint-trajectory-command-broadcaster: 1.0.5-1
ros-jazzy-ffw-joint-trajectory-command-broadcaster-dbgsym: 1.0.5-1
ros-jazzy-ffw-moveit-config: 1.0.5-1
ros-jazzy-ffw-teleop: 1.0.5-1
ros-jazzy-gurumdds-cmake-module: 5.0.0-2
ros-jazzy-leo-filters: 2.1.3-1
ros-jazzy-leo-filters-dbgsym: 2.1.3-1
ros-jazzy-mocap-optitrack: 1.0.1-1
ros-jazzy-mocap-optitrack-dbgsym: 1.0.1-1
ros-jazzy-mola-input-video: 1.7.0-1
ros-jazzy-mola-input-video-dbgsym: 1.7.0-1
ros-jazzy-phidgets-stepper: 2.3.4-1
ros-jazzy-phidgets-stepper-dbgsym: 2.3.4-1
ros-jazzy-rai-interfaces: 0.2.2-1
ros-jazzy-rai-interfaces-dbgsym: 0.2.2-1
ros-jazzy-rmw-gurumdds-cpp: 5.0.0-2
ros-jazzy-rmw-gurumdds-cpp-dbgsym: 5.0.0-2
ros-jazzy-rmw-stats-shim: 0.1.1-1
ros-jazzy-rmw-stats-shim-dbgsym: 0.1.1-1
ros-jazzy-rosgraph-monitor: 0.1.1-1
ros-jazzy-rosgraph-monitor-dbgsym: 0.1.1-1
ros-jazzy-rosgraph-monitor-msgs: 0.1.1-1
ros-jazzy-rosgraph-monitor-msgs-dbgsym: 0.1.1-1
ros-jazzy-simulation-interfaces: 1.0.0-1
ros-jazzy-simulation-interfaces-dbgsym: 1.0.0-1
ros-jazzy-tsid: 1.8.0-1
ros-jazzy-tsid-dbgsym: 1.8.0-1
ros-jazzy-turtlebot3-applications-msgs: 1.0.1-1
ros-jazzy-turtlebot3-applications-msgs-dbgsym: 1.0.1-1
ros-jazzy-turtlebot3-autorace: 1.2.2-1
ros-jazzy-turtlebot3-autorace-camera: 1.2.2-1
ros-jazzy-turtlebot3-autorace-detect: 1.2.2-1
ros-jazzy-turtlebot3-autorace-mission: 1.2.2-1

Updated Packages [414]:

ros-jazzy-ackermann-steering-controller: 4.23.0-1 → 4.25.0-1
ros-jazzy-ackermann-steering-controller-dbgsym: 4.23.0-1 → 4.25.0-1
ros-jazzy-admittance-controller: 4.23.0-1 → 4.25.0-1
ros-jazzy-admittance-controller-dbgsym: 4.23.0-1 → 4.25.0-1
ros-jazzy-autoware-common-msgs: 1.6.0-1 → 1.7.0-1
ros-jazzy-autoware-common-msgs-dbgsym: 1.6.0-1 → 1.7.0-1
ros-jazzy-autoware-control-msgs: 1.6.0-1 → 1.7.0-1
ros-jazzy-autoware-control-msgs-dbgsym: 1.6.0-1 → 1.7.0-1
ros-jazzy-autoware-lanelet2-extension: 0.7.0-1 → 0.7.2-1
ros-jazzy-autoware-lanelet2-extension-dbgsym: 0.7.0-1 → 0.7.2-1
ros-jazzy-autoware-lanelet2-extension-python: 0.7.0-1 → 0.7.2-1
ros-jazzy-autoware-lanelet2-extension-python-dbgsym: 0.7.0-1 → 0.7.2-1
ros-jazzy-autoware-localization-msgs: 1.6.0-1 → 1.7.0-1
ros-jazzy-autoware-localization-msgs-dbgsym: 1.6.0-1 → 1.7.0-1
ros-jazzy-autoware-map-msgs: 1.6.0-1 → 1.7.0-1
ros-jazzy-autoware-map-msgs-dbgsym: 1.6.0-1 → 1.7.0-1
ros-jazzy-autoware-msgs: 1.6.0-1 → 1.7.0-1
ros-jazzy-autoware-perception-msgs: 1.6.0-1 → 1.7.0-1
ros-jazzy-autoware-perception-msgs-dbgsym: 1.6.0-1 → 1.7.0-1
ros-jazzy-autoware-planning-msgs: 1.6.0-1 → 1.7.0-1
ros-jazzy-autoware-planning-msgs-dbgsym: 1.6.0-1 → 1.7.0-1
ros-jazzy-autoware-sensing-msgs: 1.6.0-1 → 1.7.0-1
ros-jazzy-autoware-sensing-msgs-dbgsym: 1.6.0-1 → 1.7.0-1
ros-jazzy-autoware-system-msgs: 1.6.0-1 → 1.7.0-1
ros-jazzy-autoware-system-msgs-dbgsym: 1.6.0-1 → 1.7.0-1
ros-jazzy-autoware-v2x-msgs: 1.6.0-1 → 1.7.0-1
ros-jazzy-autoware-v2x-msgs-dbgsym: 1.6.0-1 → 1.7.0-1
ros-jazzy-autoware-vehicle-msgs: 1.6.0-1 → 1.7.0-1
ros-jazzy-autoware-vehicle-msgs-dbgsym: 1.6.0-1 → 1.7.0-1
ros-jazzy-behaviortree-cpp: 4.6.2-1 → 4.7.1-1
ros-jazzy-behaviortree-cpp-dbgsym: 4.6.2-1 → 4.7.1-1
ros-jazzy-bicycle-steering-controller: 4.23.0-1 → 4.25.0-1
ros-jazzy-bicycle-steering-controller-dbgsym: 4.23.0-1 → 4.25.0-1
ros-jazzy-clearpath-bt-joy: 2.3.1-1 → 2.3.2-1
ros-jazzy-clearpath-common: 2.3.1-1 → 2.3.2-1
ros-jazzy-clearpath-config: 2.3.0-1 → 2.4.0-1
ros-jazzy-clearpath-control: 2.3.1-1 → 2.3.2-1
ros-jazzy-clearpath-customization: 2.3.1-1 → 2.3.2-1
ros-jazzy-clearpath-description: 2.3.1-1 → 2.3.2-1
ros-jazzy-clearpath-generator-common: 2.3.1-1 → 2.3.2-1
ros-jazzy-clearpath-generator-common-dbgsym: 2.3.1-1 → 2.3.2-1
ros-jazzy-clearpath-generator-gz: 2.3.0-1 → 2.3.1-1
ros-jazzy-clearpath-gz: 2.3.0-1 → 2.3.1-1
ros-jazzy-clearpath-manipulators: 2.3.1-1 → 2.3.2-1
ros-jazzy-clearpath-manipulators-description: 2.3.1-1 → 2.3.2-1
ros-jazzy-clearpath-motor-msgs: 2.3.0-1 → 2.4.0-1
ros-jazzy-clearpath-motor-msgs-dbgsym: 2.3.0-1 → 2.4.0-1
ros-jazzy-clearpath-mounts-description: 2.3.1-1 → 2.3.2-1
ros-jazzy-clearpath-msgs: 2.3.0-1 → 2.4.0-1
ros-jazzy-clearpath-nav2-demos: 2.0.0-1 → 2.4.0-1
ros-jazzy-clearpath-platform-description: 2.3.1-1 → 2.3.2-1
ros-jazzy-clearpath-platform-msgs: 2.3.0-1 → 2.4.0-1
ros-jazzy-clearpath-platform-msgs-dbgsym: 2.3.0-1 → 2.4.0-1
ros-jazzy-clearpath-sensors-description: 2.3.1-1 → 2.3.2-1
ros-jazzy-clearpath-simulator: 2.3.0-1 → 2.3.1-1
ros-jazzy-control-toolbox: 4.2.0-1 → 4.3.0-1
ros-jazzy-control-toolbox-dbgsym: 4.2.0-1 → 4.3.0-1
ros-jazzy-controller-interface: 4.28.1-1 → 4.29.0-1
ros-jazzy-controller-interface-dbgsym: 4.28.1-1 → 4.29.0-1
ros-jazzy-controller-manager: 4.28.1-1 → 4.29.0-1
ros-jazzy-controller-manager-dbgsym: 4.28.1-1 → 4.29.0-1
ros-jazzy-controller-manager-msgs: 4.28.1-1 → 4.29.0-1
ros-jazzy-controller-manager-msgs-dbgsym: 4.28.1-1 → 4.29.0-1
ros-jazzy-diagnostic-aggregator: 4.2.3-1 → 4.2.4-1
ros-jazzy-diagnostic-aggregator-dbgsym: 4.2.3-1 → 4.2.4-1
ros-jazzy-diagnostic-common-diagnostics: 4.2.3-1 → 4.2.4-1
ros-jazzy-diagnostic-remote-logging: 4.2.3-1 → 4.2.4-1
ros-jazzy-diagnostic-remote-logging-dbgsym: 4.2.3-1 → 4.2.4-1
ros-jazzy-diagnostic-updater: 4.2.3-1 → 4.2.4-1
ros-jazzy-diagnostic-updater-dbgsym: 4.2.3-1 → 4.2.4-1
ros-jazzy-diagnostics: 4.2.3-1 → 4.2.4-1
ros-jazzy-diff-drive-controller: 4.23.0-1 → 4.25.0-1
ros-jazzy-diff-drive-controller-dbgsym: 4.23.0-1 → 4.25.0-1
ros-jazzy-effort-controllers: 4.23.0-1 → 4.25.0-1
ros-jazzy-effort-controllers-dbgsym: 4.23.0-1 → 4.25.0-1
ros-jazzy-eigenpy: 3.10.3-1 → 3.11.0-1
ros-jazzy-eigenpy-dbgsym: 3.10.3-1 → 3.11.0-1
ros-jazzy-etsi-its-cam-coding: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-cam-coding-dbgsym: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-cam-conversion: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-cam-msgs: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-cam-msgs-dbgsym: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-cam-ts-coding: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-cam-ts-coding-dbgsym: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-cam-ts-conversion: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-cam-ts-msgs: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-cam-ts-msgs-dbgsym: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-coding: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-conversion: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-conversion-dbgsym: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-cpm-ts-coding: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-cpm-ts-coding-dbgsym: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-cpm-ts-conversion: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-cpm-ts-msgs: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-cpm-ts-msgs-dbgsym: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-denm-coding: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-denm-coding-dbgsym: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-denm-conversion: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-denm-msgs: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-denm-msgs-dbgsym: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-denm-ts-coding: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-denm-ts-coding-dbgsym: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-denm-ts-conversion: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-denm-ts-msgs: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-denm-ts-msgs-dbgsym: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-mapem-ts-coding: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-mapem-ts-coding-dbgsym: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-mapem-ts-conversion: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-mapem-ts-msgs: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-mapem-ts-msgs-dbgsym: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-mcm-uulm-coding: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-mcm-uulm-coding-dbgsym: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-mcm-uulm-conversion: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-mcm-uulm-msgs: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-mcm-uulm-msgs-dbgsym: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-messages: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-msgs: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-msgs-utils: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-primitives-conversion: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-rviz-plugins: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-rviz-plugins-dbgsym: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-spatem-ts-coding: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-spatem-ts-coding-dbgsym: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-spatem-ts-conversion: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-spatem-ts-msgs: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-spatem-ts-msgs-dbgsym: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-vam-ts-coding: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-vam-ts-coding-dbgsym: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-vam-ts-conversion: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-vam-ts-msgs: 3.2.0-1 → 3.2.1-1
ros-jazzy-etsi-its-vam-ts-msgs-dbgsym: 3.2.0-1 → 3.2.1-1
ros-jazzy-examples-tf2-py: 0.36.10-1 → 0.36.11-1
ros-jazzy-filters: 2.1.2-2 → 2.2.1-1
ros-jazzy-filters-dbgsym: 2.1.2-2 → 2.2.1-1
ros-jazzy-fkie-message-filters: 3.0.2-1 → 3.2.0-1
ros-jazzy-fkie-message-filters-dbgsym: 3.0.2-1 → 3.2.0-1
ros-jazzy-force-torque-sensor-broadcaster: 4.23.0-1 → 4.25.0-1
ros-jazzy-force-torque-sensor-broadcaster-dbgsym: 4.23.0-1 → 4.25.0-1
ros-jazzy-forward-command-controller: 4.23.0-1 → 4.25.0-1
ros-jazzy-forward-command-controller-dbgsym: 4.23.0-1 → 4.25.0-1
ros-jazzy-foxglove-bridge: 0.8.3-1 → 0.8.5-1
ros-jazzy-foxglove-bridge-dbgsym: 0.8.3-1 → 0.8.5-1
ros-jazzy-geometry2: 0.36.10-1 → 0.36.11-1
ros-jazzy-gpio-controllers: 4.23.0-1 → 4.25.0-1
ros-jazzy-gpio-controllers-dbgsym: 4.23.0-1 → 4.25.0-1
ros-jazzy-gps-sensor-broadcaster: 4.23.0-1 → 4.25.0-1
ros-jazzy-gps-sensor-broadcaster-dbgsym: 4.23.0-1 → 4.25.0-1
ros-jazzy-gripper-controllers: 4.23.0-1 → 4.25.0-1
ros-jazzy-gripper-controllers-dbgsym: 4.23.0-1 → 4.25.0-1
ros-jazzy-hardware-interface: 4.28.1-1 → 4.29.0-1
ros-jazzy-hardware-interface-dbgsym: 4.28.1-1 → 4.29.0-1
ros-jazzy-hardware-interface-testing: 4.28.1-1 → 4.29.0-1
ros-jazzy-hardware-interface-testing-dbgsym: 4.28.1-1 → 4.29.0-1
ros-jazzy-imu-sensor-broadcaster: 4.23.0-1 → 4.25.0-1
ros-jazzy-imu-sensor-broadcaster-dbgsym: 4.23.0-1 → 4.25.0-1
ros-jazzy-joint-limits: 4.28.1-1 → 4.29.0-1
ros-jazzy-joint-limits-dbgsym: 4.28.1-1 → 4.29.0-1
ros-jazzy-joint-state-broadcaster: 4.23.0-1 → 4.25.0-1
ros-jazzy-joint-state-broadcaster-dbgsym: 4.23.0-1 → 4.25.0-1
ros-jazzy-joint-trajectory-controller: 4.23.0-1 → 4.25.0-1
ros-jazzy-joint-trajectory-controller-dbgsym: 4.23.0-1 → 4.25.0-1
ros-jazzy-joy-teleop: 1.8.0-1 → 2.0.0-1
ros-jazzy-key-teleop: 1.8.0-1 → 2.0.0-1
ros-jazzy-kitti-metrics-eval: 1.6.3-1 → 1.7.0-1
ros-jazzy-kitti-metrics-eval-dbgsym: 1.6.3-1 → 1.7.0-1
ros-jazzy-leo-bringup: 2.0.0-1 → 2.1.3-1
ros-jazzy-leo-fw: 2.0.0-1 → 2.1.3-1
ros-jazzy-leo-fw-dbgsym: 2.0.0-1 → 2.1.3-1
ros-jazzy-leo-robot: 2.0.0-1 → 2.1.3-1
ros-jazzy-libmavconn: 2.9.0-1 → 2.10.0-1
ros-jazzy-libmavconn-dbgsym: 2.9.0-1 → 2.10.0-1
ros-jazzy-libphidget22: 2.3.3-2 → 2.3.4-1
ros-jazzy-libphidget22-dbgsym: 2.3.3-2 → 2.3.4-1
ros-jazzy-mavlink: 2024.10.10-1 → 2025.5.5-1
ros-jazzy-mavros: 2.9.0-1 → 2.10.0-1
ros-jazzy-mavros-dbgsym: 2.9.0-1 → 2.10.0-1
ros-jazzy-mavros-extras: 2.9.0-1 → 2.10.0-1
ros-jazzy-mavros-extras-dbgsym: 2.9.0-1 → 2.10.0-1
ros-jazzy-mavros-msgs: 2.9.0-1 → 2.10.0-1
ros-jazzy-mavros-msgs-dbgsym: 2.9.0-1 → 2.10.0-1
ros-jazzy-mecanum-drive-controller: 4.23.0-1 → 4.25.0-1
ros-jazzy-mecanum-drive-controller-dbgsym: 4.23.0-1 → 4.25.0-1
ros-jazzy-microstrain-inertial-description: 4.6.0-1 → 4.6.1-1
ros-jazzy-microstrain-inertial-driver: 4.6.0-1 → 4.6.1-1
ros-jazzy-microstrain-inertial-driver-dbgsym: 4.6.0-1 → 4.6.1-1
ros-jazzy-microstrain-inertial-examples: 4.6.0-1 → 4.6.1-1
ros-jazzy-microstrain-inertial-msgs: 4.6.0-1 → 4.6.1-1
ros-jazzy-microstrain-inertial-msgs-dbgsym: 4.6.0-1 → 4.6.1-1
ros-jazzy-microstrain-inertial-rqt: 4.6.0-1 → 4.6.1-1
ros-jazzy-mola: 1.6.3-1 → 1.7.0-1
ros-jazzy-mola-bridge-ros2: 1.6.3-1 → 1.7.0-1
ros-jazzy-mola-bridge-ros2-dbgsym: 1.6.3-1 → 1.7.0-1
ros-jazzy-mola-demos: 1.6.3-1 → 1.7.0-1
ros-jazzy-mola-input-euroc-dataset: 1.6.3-1 → 1.7.0-1
ros-jazzy-mola-input-euroc-dataset-dbgsym: 1.6.3-1 → 1.7.0-1
ros-jazzy-mola-input-kitti-dataset: 1.6.3-1 → 1.7.0-1
ros-jazzy-mola-input-kitti-dataset-dbgsym: 1.6.3-1 → 1.7.0-1
ros-jazzy-mola-input-kitti360-dataset: 1.6.3-1 → 1.7.0-1
ros-jazzy-mola-input-kitti360-dataset-dbgsym: 1.6.3-1 → 1.7.0-1
ros-jazzy-mola-input-mulran-dataset: 1.6.3-1 → 1.7.0-1
ros-jazzy-mola-input-mulran-dataset-dbgsym: 1.6.3-1 → 1.7.0-1
ros-jazzy-mola-input-paris-luco-dataset: 1.6.3-1 → 1.7.0-1
ros-jazzy-mola-input-paris-luco-dataset-dbgsym: 1.6.3-1 → 1.7.0-1
ros-jazzy-mola-input-rawlog: 1.6.3-1 → 1.7.0-1
ros-jazzy-mola-input-rawlog-dbgsym: 1.6.3-1 → 1.7.0-1
ros-jazzy-mola-input-rosbag2: 1.6.3-1 → 1.7.0-1
ros-jazzy-mola-input-rosbag2-dbgsym: 1.6.3-1 → 1.7.0-1
ros-jazzy-mola-kernel: 1.6.3-1 → 1.7.0-1
ros-jazzy-mola-kernel-dbgsym: 1.6.3-1 → 1.7.0-1
ros-jazzy-mola-launcher: 1.6.3-1 → 1.7.0-1
ros-jazzy-mola-launcher-dbgsym: 1.6.3-1 → 1.7.0-1
ros-jazzy-mola-lidar-odometry: 0.7.1-1 → 0.7.2-1
ros-jazzy-mola-lidar-odometry-dbgsym: 0.7.1-1 → 0.7.2-1
ros-jazzy-mola-metric-maps: 1.6.3-1 → 1.7.0-1
ros-jazzy-mola-metric-maps-dbgsym: 1.6.3-1 → 1.7.0-1
ros-jazzy-mola-msgs: 1.6.3-1 → 1.7.0-1
ros-jazzy-mola-msgs-dbgsym: 1.6.3-1 → 1.7.0-1
ros-jazzy-mola-pose-list: 1.6.3-1 → 1.7.0-1
ros-jazzy-mola-pose-list-dbgsym: 1.6.3-1 → 1.7.0-1
ros-jazzy-mola-relocalization: 1.6.3-1 → 1.7.0-1
ros-jazzy-mola-relocalization-dbgsym: 1.6.3-1 → 1.7.0-1
ros-jazzy-mola-traj-tools: 1.6.3-1 → 1.7.0-1
ros-jazzy-mola-traj-tools-dbgsym: 1.6.3-1 → 1.7.0-1
ros-jazzy-mola-viz: 1.6.3-1 → 1.7.0-1
ros-jazzy-mola-viz-dbgsym: 1.6.3-1 → 1.7.0-1
ros-jazzy-mola-yaml: 1.6.3-1 → 1.7.0-1
ros-jazzy-mola-yaml-dbgsym: 1.6.3-1 → 1.7.0-1
ros-jazzy-mouse-teleop: 1.8.0-1 → 2.0.0-1
ros-jazzy-mrpt-apps: 2.14.7-1 → 2.14.9-1
ros-jazzy-mrpt-apps-dbgsym: 2.14.7-1 → 2.14.9-1
ros-jazzy-mrpt-libapps: 2.14.7-1 → 2.14.9-1
ros-jazzy-mrpt-libapps-dbgsym: 2.14.7-1 → 2.14.9-1
ros-jazzy-mrpt-libbase: 2.14.7-1 → 2.14.9-1
ros-jazzy-mrpt-libbase-dbgsym: 2.14.7-1 → 2.14.9-1
ros-jazzy-mrpt-libgui: 2.14.7-1 → 2.14.9-1
ros-jazzy-mrpt-libgui-dbgsym: 2.14.7-1 → 2.14.9-1
ros-jazzy-mrpt-libhwdrivers: 2.14.7-1 → 2.14.9-1
ros-jazzy-mrpt-libhwdrivers-dbgsym: 2.14.7-1 → 2.14.9-1
ros-jazzy-mrpt-libmaps: 2.14.7-1 → 2.14.9-1
ros-jazzy-mrpt-libmaps-dbgsym: 2.14.7-1 → 2.14.9-1
ros-jazzy-mrpt-libmath: 2.14.7-1 → 2.14.9-1
ros-jazzy-mrpt-libmath-dbgsym: 2.14.7-1 → 2.14.9-1
ros-jazzy-mrpt-libnav: 2.14.7-1 → 2.14.9-1
ros-jazzy-mrpt-libnav-dbgsym: 2.14.7-1 → 2.14.9-1
ros-jazzy-mrpt-libobs: 2.14.7-1 → 2.14.9-1
ros-jazzy-mrpt-libobs-dbgsym: 2.14.7-1 → 2.14.9-1
ros-jazzy-mrpt-libopengl: 2.14.7-1 → 2.14.9-1
ros-jazzy-mrpt-libopengl-dbgsym: 2.14.7-1 → 2.14.9-1
ros-jazzy-mrpt-libposes: 2.14.7-1 → 2.14.9-1
ros-jazzy-mrpt-libposes-dbgsym: 2.14.7-1 → 2.14.9-1
ros-jazzy-mrpt-libros-bridge: 2.14.7-1 → 2.14.9-1
ros-jazzy-mrpt-libros-bridge-dbgsym: 2.14.7-1 → 2.14.9-1
ros-jazzy-mrpt-libslam: 2.14.7-1 → 2.14.9-1
ros-jazzy-mrpt-libslam-dbgsym: 2.14.7-1 → 2.14.9-1
ros-jazzy-mrpt-libtclap: 2.14.7-1 → 2.14.9-1
ros-jazzy-om-joint-trajectory-command-broadcaster: 3.2.1-1 → 3.2.2-1
ros-jazzy-om-joint-trajectory-command-broadcaster-dbgsym: 3.2.1-1 → 3.2.2-1
ros-jazzy-ompl: 1.6.0-1 → 1.7.0-2
ros-jazzy-ompl-dbgsym: 1.6.0-1 → 1.7.0-2
ros-jazzy-open-manipulator-bringup: 3.2.1-1 → 3.2.2-1
ros-jazzy-open-manipulator-description: 3.2.1-1 → 3.2.2-1
ros-jazzy-open-manipulator-gui: 3.2.1-1 → 3.2.2-1
ros-jazzy-open-manipulator-gui-dbgsym: 3.2.1-1 → 3.2.2-1
ros-jazzy-open-manipulator-moveit-config: 3.2.1-1 → 3.2.2-1
ros-jazzy-open-manipulator-playground: 3.2.1-1 → 3.2.2-1
ros-jazzy-open-manipulator-playground-dbgsym: 3.2.1-1 → 3.2.2-1
ros-jazzy-open-manipulator-teleop: 3.2.1-1 → 3.2.2-1
ros-jazzy-parallel-gripper-controller: 4.23.0-1 → 4.25.0-1
ros-jazzy-parallel-gripper-controller-dbgsym: 4.23.0-1 → 4.25.0-1
ros-jazzy-phidgets-accelerometer: 2.3.3-2 → 2.3.4-1
ros-jazzy-phidgets-accelerometer-dbgsym: 2.3.3-2 → 2.3.4-1
ros-jazzy-phidgets-analog-inputs: 2.3.3-2 → 2.3.4-1
ros-jazzy-phidgets-analog-inputs-dbgsym: 2.3.3-2 → 2.3.4-1
ros-jazzy-phidgets-analog-outputs: 2.3.3-2 → 2.3.4-1
ros-jazzy-phidgets-analog-outputs-dbgsym: 2.3.3-2 → 2.3.4-1
ros-jazzy-phidgets-api: 2.3.3-2 → 2.3.4-1
ros-jazzy-phidgets-api-dbgsym: 2.3.3-2 → 2.3.4-1
ros-jazzy-phidgets-digital-inputs: 2.3.3-2 → 2.3.4-1
ros-jazzy-phidgets-digital-inputs-dbgsym: 2.3.3-2 → 2.3.4-1
ros-jazzy-phidgets-digital-outputs: 2.3.3-2 → 2.3.4-1
ros-jazzy-phidgets-digital-outputs-dbgsym: 2.3.3-2 → 2.3.4-1
ros-jazzy-phidgets-drivers: 2.3.3-2 → 2.3.4-1
ros-jazzy-phidgets-gyroscope: 2.3.3-2 → 2.3.4-1
ros-jazzy-phidgets-gyroscope-dbgsym: 2.3.3-2 → 2.3.4-1
ros-jazzy-phidgets-high-speed-encoder: 2.3.3-2 → 2.3.4-1
ros-jazzy-phidgets-high-speed-encoder-dbgsym: 2.3.3-2 → 2.3.4-1
ros-jazzy-phidgets-ik: 2.3.3-2 → 2.3.4-1
ros-jazzy-phidgets-magnetometer: 2.3.3-2 → 2.3.4-1
ros-jazzy-phidgets-magnetometer-dbgsym: 2.3.3-2 → 2.3.4-1
ros-jazzy-phidgets-motors: 2.3.3-2 → 2.3.4-1
ros-jazzy-phidgets-motors-dbgsym: 2.3.3-2 → 2.3.4-1
ros-jazzy-phidgets-msgs: 2.3.3-2 → 2.3.4-1
ros-jazzy-phidgets-msgs-dbgsym: 2.3.3-2 → 2.3.4-1
ros-jazzy-phidgets-spatial: 2.3.3-2 → 2.3.4-1
ros-jazzy-phidgets-spatial-dbgsym: 2.3.3-2 → 2.3.4-1
ros-jazzy-phidgets-temperature: 2.3.3-2 → 2.3.4-1
ros-jazzy-phidgets-temperature-dbgsym: 2.3.3-2 → 2.3.4-1
ros-jazzy-pid-controller: 4.23.0-1 → 4.25.0-1
ros-jazzy-pid-controller-dbgsym: 4.23.0-1 → 4.25.0-1
ros-jazzy-pinocchio: 3.4.0-2 → 3.5.0-1
ros-jazzy-pinocchio-dbgsym: 3.4.0-2 → 3.5.0-1
ros-jazzy-pose-broadcaster: 4.23.0-1 → 4.25.0-1
ros-jazzy-pose-broadcaster-dbgsym: 4.23.0-1 → 4.25.0-1
ros-jazzy-position-controllers: 4.23.0-1 → 4.25.0-1
ros-jazzy-position-controllers-dbgsym: 4.23.0-1 → 4.25.0-1
ros-jazzy-python-mrpt: 2.14.7-1 → 2.14.9-1
ros-jazzy-range-sensor-broadcaster: 4.23.0-1 → 4.25.0-1
ros-jazzy-range-sensor-broadcaster-dbgsym: 4.23.0-1 → 4.25.0-1
ros-jazzy-realtime-tools: 3.5.0-1 → 3.5.1-1
ros-jazzy-realtime-tools-dbgsym: 3.5.0-1 → 3.5.1-1
ros-jazzy-rig-reconfigure: 1.5.0-1 → 1.6.0-1
ros-jazzy-rig-reconfigure-dbgsym: 1.5.0-1 → 1.6.0-1
ros-jazzy-ros-gz: 1.0.11-1 → 1.0.12-1
ros-jazzy-ros-gz-bridge: 1.0.11-1 → 1.0.12-1
ros-jazzy-ros-gz-bridge-dbgsym: 1.0.11-1 → 1.0.12-1
ros-jazzy-ros-gz-image: 1.0.11-1 → 1.0.12-1
ros-jazzy-ros-gz-image-dbgsym: 1.0.11-1 → 1.0.12-1
ros-jazzy-ros-gz-interfaces: 1.0.11-1 → 1.0.12-1
ros-jazzy-ros-gz-interfaces-dbgsym: 1.0.11-1 → 1.0.12-1
ros-jazzy-ros-gz-sim: 1.0.11-1 → 1.0.12-1
ros-jazzy-ros-gz-sim-dbgsym: 1.0.11-1 → 1.0.12-1
ros-jazzy-ros-gz-sim-demos: 1.0.11-1 → 1.0.12-1
ros-jazzy-ros2-control: 4.28.1-1 → 4.29.0-1
ros-jazzy-ros2-control-test-assets: 4.28.1-1 → 4.29.0-1
ros-jazzy-ros2-controllers: 4.23.0-1 → 4.25.0-1
ros-jazzy-ros2-controllers-test-nodes: 4.23.0-1 → 4.25.0-1
ros-jazzy-ros2controlcli: 4.28.1-1 → 4.29.0-1
ros-jazzy-rosapi: 2.2.0-1 → 2.3.0-1
ros-jazzy-rosapi-msgs: 2.2.0-1 → 2.3.0-1
ros-jazzy-rosapi-msgs-dbgsym: 2.2.0-1 → 2.3.0-1
ros-jazzy-rosbridge-library: 2.2.0-1 → 2.3.0-1
ros-jazzy-rosbridge-msgs: 2.2.0-1 → 2.3.0-1
ros-jazzy-rosbridge-msgs-dbgsym: 2.2.0-1 → 2.3.0-1
ros-jazzy-rosbridge-server: 2.2.0-1 → 2.3.0-1
ros-jazzy-rosbridge-suite: 2.2.0-1 → 2.3.0-1
ros-jazzy-rosbridge-test-msgs: 2.2.0-1 → 2.3.0-1
ros-jazzy-rosbridge-test-msgs-dbgsym: 2.2.0-1 → 2.3.0-1
ros-jazzy-rqt-controller-manager: 4.28.1-1 → 4.29.0-1
ros-jazzy-rqt-joint-trajectory-controller: 4.23.0-1 → 4.25.0-1
ros-jazzy-rqt-plot: 1.4.2-1 → 1.4.3-1
ros-jazzy-rviz-assimp-vendor: 14.1.10-1 → 14.1.11-1
ros-jazzy-rviz-common: 14.1.10-1 → 14.1.11-1
ros-jazzy-rviz-common-dbgsym: 14.1.10-1 → 14.1.11-1
ros-jazzy-rviz-default-plugins: 14.1.10-1 → 14.1.11-1
ros-jazzy-rviz-default-plugins-dbgsym: 14.1.10-1 → 14.1.11-1
ros-jazzy-rviz-ogre-vendor: 14.1.10-1 → 14.1.11-1
ros-jazzy-rviz-ogre-vendor-dbgsym: 14.1.10-1 → 14.1.11-1
ros-jazzy-rviz-rendering: 14.1.10-1 → 14.1.11-1
ros-jazzy-rviz-rendering-dbgsym: 14.1.10-1 → 14.1.11-1
ros-jazzy-rviz-rendering-tests: 14.1.10-1 → 14.1.11-1
ros-jazzy-rviz-satellite: 4.1.0-2 → 4.2.0-1
ros-jazzy-rviz-satellite-dbgsym: 4.1.0-2 → 4.2.0-1
ros-jazzy-rviz-visual-testing-framework: 14.1.10-1 → 14.1.11-1
ros-jazzy-rviz2: 14.1.10-1 → 14.1.11-1
ros-jazzy-rviz2-dbgsym: 14.1.10-1 → 14.1.11-1
ros-jazzy-self-test: 4.2.3-1 → 4.2.4-1
ros-jazzy-self-test-dbgsym: 4.2.3-1 → 4.2.4-1
ros-jazzy-septentrio-gnss-driver: 1.4.2-1 → 1.4.3-1
ros-jazzy-septentrio-gnss-driver-dbgsym: 1.4.2-1 → 1.4.3-1
ros-jazzy-slider-publisher: 2.3.1-3 → 2.4.1-1
ros-jazzy-steering-controllers-library: 4.23.0-1 → 4.25.0-1
ros-jazzy-steering-controllers-library-dbgsym: 4.23.0-1 → 4.25.0-1
ros-jazzy-teleop-tools: 1.8.0-1 → 2.0.0-1
ros-jazzy-teleop-tools-msgs: 1.8.0-1 → 2.0.0-1
ros-jazzy-teleop-tools-msgs-dbgsym: 1.8.0-1 → 2.0.0-1
ros-jazzy-test-ros-gz-bridge: 1.0.11-1 → 1.0.12-1
ros-jazzy-tf2: 0.36.10-1 → 0.36.11-1
ros-jazzy-tf2-bullet: 0.36.10-1 → 0.36.11-1
ros-jazzy-tf2-dbgsym: 0.36.10-1 → 0.36.11-1
ros-jazzy-tf2-eigen: 0.36.10-1 → 0.36.11-1
ros-jazzy-tf2-eigen-kdl: 0.36.10-1 → 0.36.11-1
ros-jazzy-tf2-eigen-kdl-dbgsym: 0.36.10-1 → 0.36.11-1
ros-jazzy-tf2-geometry-msgs: 0.36.10-1 → 0.36.11-1
ros-jazzy-tf2-kdl: 0.36.10-1 → 0.36.11-1
ros-jazzy-tf2-msgs: 0.36.10-1 → 0.36.11-1
ros-jazzy-tf2-msgs-dbgsym: 0.36.10-1 → 0.36.11-1
ros-jazzy-tf2-py: 0.36.10-1 → 0.36.11-1
ros-jazzy-tf2-py-dbgsym: 0.36.10-1 → 0.36.11-1
ros-jazzy-tf2-ros: 0.36.10-1 → 0.36.11-1
ros-jazzy-tf2-ros-dbgsym: 0.36.10-1 → 0.36.11-1
ros-jazzy-tf2-ros-py: 0.36.10-1 → 0.36.11-1
ros-jazzy-tf2-sensor-msgs: 0.36.10-1 → 0.36.11-1
ros-jazzy-tf2-tools: 0.36.10-1 → 0.36.11-1
ros-jazzy-transmission-interface: 4.28.1-1 → 4.29.0-1
ros-jazzy-transmission-interface-dbgsym: 4.28.1-1 → 4.29.0-1
ros-jazzy-tricycle-controller: 4.23.0-1 → 4.25.0-1
ros-jazzy-tricycle-controller-dbgsym: 4.23.0-1 → 4.25.0-1
ros-jazzy-tricycle-steering-controller: 4.23.0-1 → 4.25.0-1
ros-jazzy-tricycle-steering-controller-dbgsym: 4.23.0-1 → 4.25.0-1
ros-jazzy-turtlebot3-msgs: 2.3.0-1 → 2.4.0-1
ros-jazzy-turtlebot3-msgs-dbgsym: 2.3.0-1 → 2.4.0-1
ros-jazzy-tuw-geometry: 0.1.2-1 → 0.1.3-1
ros-jazzy-tuw-geometry-dbgsym: 0.1.2-1 → 0.1.3-1
ros-jazzy-ur: 3.2.0-1 → 3.3.0-1
ros-jazzy-ur-calibration: 3.2.0-1 → 3.3.0-1
ros-jazzy-ur-calibration-dbgsym: 3.2.0-1 → 3.3.0-1
ros-jazzy-ur-client-library: 1.9.0-1 → 2.0.0-1
ros-jazzy-ur-client-library-dbgsym: 1.9.0-1 → 2.0.0-1
ros-jazzy-ur-controllers: 3.2.0-1 → 3.3.0-1
ros-jazzy-ur-controllers-dbgsym: 3.2.0-1 → 3.3.0-1
ros-jazzy-ur-dashboard-msgs: 3.2.0-1 → 3.3.0-1
ros-jazzy-ur-dashboard-msgs-dbgsym: 3.2.0-1 → 3.3.0-1
ros-jazzy-ur-description: 3.1.0-1 → 3.2.0-1
ros-jazzy-ur-moveit-config: 3.2.0-1 → 3.3.0-1
ros-jazzy-ur-robot-driver: 3.2.0-1 → 3.3.0-1
ros-jazzy-ur-robot-driver-dbgsym: 3.2.0-1 → 3.3.0-1
ros-jazzy-urdfdom: 4.0.1-1 → 4.0.2-1
ros-jazzy-urdfdom-dbgsym: 4.0.1-1 → 4.0.2-1
ros-jazzy-velocity-controllers: 4.23.0-1 → 4.25.0-1
ros-jazzy-velocity-controllers-dbgsym: 4.23.0-1 → 4.25.0-1
ros-jazzy-wireless-msgs: 1.1.4-1 → 1.1.5-1
ros-jazzy-wireless-msgs-dbgsym: 1.1.4-1 → 1.1.5-1
ros-jazzy-wireless-watcher: 1.1.4-1 → 1.1.5-1
ros-jazzy-wireless-watcher-dbgsym: 1.1.4-1 → 1.1.5-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 Dabrowski
Aditya Pande
Alejandro Hernandez Cordero
Andre Schröder
Apex.AI, Inc.
Austin Hendrix
Bence Magyar
Bonsai Robotics Engineering
Brandon Ong
Błażej Sowa
Chris Iverach-Brereton
Chris Lalancette
Daan Wijffels
Davide Faconti
Donghyeon Lee
Emerson Knapp
Enrique Fernandez
Felix Exner
Fictionlab
Guilhem Saurel
Hans-Joachim Krauch
Jean-Pierre Busch
Jian Kang
Jose Luis Blanco-Claraco
Justin Carpentier
Luis Camero
M. Fatih Cırıt
Mamoru Sobue
Mark Moll
Markus Bader
Martin Günther
Olivier Kermorgant
Pyo
Rob Fisher
Roni Kreinin
Takagi, Isamu
Team Spatzenhirn
Tibor Dome
Timo Röhling
Tony Baltovski
Tully Foote
Vladimir Ermakov
Yutaka Kondo
kminoda
mitsudome-r

Enjoy!

1 post - 1 participant

Read full topic

https://discourse.ros.org/t/new-packages-for-jazzy-jalisco-2025-05-23/43898

ROS Discourse General: Optional automatic `source install/setup.bash` in cwd when using ROS 2 CLI commands

One of the most tedious parts of ROS 2 is repeatedly calling source install/setup.bash in every new workspace terminal. I’m suggestion an optional environment variable that, when enabled, automatically runs source install/setup.bash (or other shell equivalent) when CLI commands including ros2 run, launch, topic, msg, param, action, service, ... are called. This would restrict the user’s ability to call these commands anywhere except the root of the intended workspace. However, I find that to be a worthwhile tradeoff that many CLI tools outside of ROS 2 already do, but would be interested to know if others feel the same way. Again, completely optional non-default behavior.

The specific logical flow would be:

User calls ros2 ... from their workspace root
Code in ros2cli checks if an “auto-source” environment variable is set
If it’s set, then run source install/setup.<shell_extension>
Finally, the intended command is run

Side note: this idea could be extended to auto colcon build before ros2 run/launch as well.

14 posts - 9 participants

Read full topic

https://discourse.ros.org/t/optional-automatic-source-install-setup-bash-in-cwd-when-using-ros-2-cli-commands/43867

ROS Discourse General: Vote for the most useful Cloud Robotics guides!

Last year, the Cloud Robotics Working Group ran the State of Cloud Robotics survey. We found that what people need most is more guidance on best practices and documentation for Cloud Robotics. With that in mind, we are trying to write and publish different guides on our site, the Cloud Robotics Hub.

Which of these topics would be most useful to you as a guide?

Click to view the poll.

If you have already responded to the poll on LinkedIn, please donâ€™t respond again! Thank you.

2 posts - 1 participant

Read full topic

https://discourse.ros.org/t/vote-for-the-most-useful-cloud-robotics-guides/43842

ROS Discourse General: Upcoming Distribution Freeze for Kilted Kaiju

As we prepare for the release of Kilted Kaiju later this week, we plan to pause ros/rosdistro pull requests for kilted/distribution.yaml and changes proposed to the kilted branches of ROS core packages as of 2025-05-20T07:00:00Z UTC.

During this time, any changes which are needed to resolve any release-blocking or critical bugs will be reviewed by the team. Anything not granted an exception may instead be documented as a known issue prior to release.

We will re-open rosdistro for package release PRs after the freeze period ends on World Turtle Day. As always, you can find more information about the Kilted Kaiju release timeline here: ROS 2 Kilted Kaiju.

Thanks!

4 posts - 2 participants

Read full topic

https://discourse.ros.org/t/upcoming-distribution-freeze-for-kilted-kaiju/43839

ROS Discourse General: About 85% of all robotic arms now have ROS 2 drivers

Since announcing this ROS driver hardware database in January, weâ€™ve gotten a lot of submissions from folks of additional robot hardware that are using ROS. We have also added more robot arms that do not yet support ROS 2. In total we are now tracking 34 robot arm brands, and we are excited to share to the ROS community that about 85% of them have ROS 2 support.

In addition, about 76% of those drivers are supported by the arm vendor! Caveat: these statistics do not reflect driver quality - some implementations are not as good as others.

We will continue to expand our database of ROS 2 real-time drivers and encourage you to submit hardware that is missing. Not only are we tracking robot arms - it also includes AMRs, cameras, end effectors, and much more.

We also encourage you to reach out to vendors directly if there are missing or sub-par drivers - they are very responsive to customer demand. Especially from larger companies.

5 posts - 4 participants

Read full topic

https://discourse.ros.org/t/about-85-of-all-robotic-arms-now-have-ros-2-drivers/43835

ROS Discourse General: ICRA 2025 Open Thread

ICRA 2025 Open Thread

Hi Everyone,

Let’s meetup at ICRA 2025 in Atlanta!

I’ll be giving a 15 minute ROS 2 Kilted Kaiju intro at the Innovation Stage on 2025-05-20T19:15:00Z UTC and handing out Kilted stickers. We also have a ROS meetup / Kilted Kaiju launch party scheduled for 2025-05-21T21:00:00Z UTC→2025-05-22T00:00:00Z UTC.

If you are presenting a ROS-related poster or talk feel free to post the details below (we might even help promote it)! If you would like to find a time to chat send me a DM and we’ll work something out. Feel free to use this thread or Discord to coordinate.

1 post - 1 participant

Read full topic

https://discourse.ros.org/t/icra-2025-open-thread/43834

ROS Discourse General: Summer Hackathon with ROSCon 2025 Awards

Dear Open Robotics Community,

I would like to suggest organizing a Summer Hackathon from June to August 2025 to boost contributions to the ROS ecosystem during the summer period.

Many students and contributors have more free time during summer, making it the perfect opportunity to engage them in open-source development.

Key Highlights:

Timeline: June â†’ August 2025
Focus: Contributions via GitHub issues and pull requests across ROS, Gazebo, Ros-controls, and related projects.
Community Engagement: Open to everyone students, researchers, hobbyists, and professionals.
Recognition: Winners selected by a review panel and announced at ROSCon 2025.

This would be a great way to strengthen community involvement, discover new talent, and accelerate development across the ecosystem.

2 posts - 2 participants

Read full topic

https://discourse.ros.org/t/summer-hackathon-with-roscon-2025-awards/43810

ROS Discourse General: ROS News for the Week of May 12th, 2025

ROS News for the Week of May 12th, 2025

Are you heading to ICRA 2025 in Atlanta! Thanks to support from our friends at Intrinsic, PAL Robotics, and Foxglove we’ve organized a Kilted Kaiju launch party and ROS meetup at ICRA 2025 in Atlanta

Europe - The Final Countdown (Official Video)

The final Noetic Sync will be on 2025-05-29. It is the final countdown for ROS 1!

This week I was at Automate / ROS Industrial Annual meeting in Detroit. We had a fantastic ROS meetup thanks to help from PickNik and ROS Industrial.

The big news out of ROS Industrial is that Fanuc now has an official ROS 2 driver! You need to ask your Fanuc rep for the details and source code. Want to know more about ROS support for various arm vendors? Check out this compatibility guide from PickNik.

A team at UMass Lowell, Rutgers, WPI, Yale, and University of South Florida have just launched robot-manipulation.org. This new website is a one stop shop for all things open source manipulation.

Two weeks from today join us for an Edinburgh ROS Meetup and ROS 1 wake.

Events

News

ROS

Got a Minute?

We could sure use your help with the following issues:

1 post - 1 participant

Read full topic

https://discourse.ros.org/t/ros-news-for-the-week-of-may-12th-2025/43803

ROS Discourse General: New packages for Humble Hawksbill 2025-05-16

Package Updates for humble

Added Packages [33]:

ros-humble-autoware-utils-debug: 1.4.0-1
ros-humble-autoware-utils-diagnostics: 1.4.0-1
ros-humble-autoware-utils-diagnostics-dbgsym: 1.4.0-1
ros-humble-autoware-utils-geometry: 1.4.0-1
ros-humble-autoware-utils-geometry-dbgsym: 1.4.0-1
ros-humble-autoware-utils-logging: 1.4.0-1
ros-humble-autoware-utils-logging-dbgsym: 1.4.0-1
ros-humble-autoware-utils-math: 1.4.0-1
ros-humble-autoware-utils-math-dbgsym: 1.4.0-1
ros-humble-autoware-utils-pcl: 1.4.0-1
ros-humble-autoware-utils-rclcpp: 1.4.0-1
ros-humble-autoware-utils-system: 1.4.0-1
ros-humble-autoware-utils-system-dbgsym: 1.4.0-1
ros-humble-autoware-utils-tf: 1.4.0-1
ros-humble-autoware-utils-uuid: 1.4.0-1
ros-humble-autoware-utils-visualization: 1.4.0-1
ros-humble-autoware-utils-visualization-dbgsym: 1.4.0-1
ros-humble-broll: 0.1.0-1
ros-humble-broll-dbgsym: 0.1.0-1
ros-humble-mocap-optitrack: 1.0.1-1
ros-humble-mocap-optitrack-dbgsym: 1.0.1-1
ros-humble-mola-input-video: 1.7.0-1
ros-humble-mola-input-video-dbgsym: 1.7.0-1
ros-humble-rai-interfaces: 0.2.2-1
ros-humble-rai-interfaces-dbgsym: 0.2.2-1
ros-humble-sicks300-2: 1.3.3-1
ros-humble-sicks300-2-dbgsym: 1.3.3-1
ros-humble-tsid: 1.8.0-1
ros-humble-tsid-dbgsym: 1.8.0-1
ros-humble-turtlebot3-autorace: 1.2.2-1
ros-humble-turtlebot3-autorace-camera: 1.2.2-1
ros-humble-turtlebot3-autorace-detect: 1.2.2-1
ros-humble-turtlebot3-autorace-mission: 1.2.2-1

Updated Packages [304]:

ros-humble-ackermann-steering-controller: 2.44.0-1 → 2.45.0-1
ros-humble-ackermann-steering-controller-dbgsym: 2.44.0-1 → 2.45.0-1
ros-humble-admittance-controller: 2.44.0-1 → 2.45.0-1
ros-humble-admittance-controller-dbgsym: 2.44.0-1 → 2.45.0-1
ros-humble-autoware-common-msgs: 1.6.0-1 → 1.7.0-1
ros-humble-autoware-common-msgs-dbgsym: 1.6.0-1 → 1.7.0-1
ros-humble-autoware-control-msgs: 1.6.0-1 → 1.7.0-1
ros-humble-autoware-control-msgs-dbgsym: 1.6.0-1 → 1.7.0-1
ros-humble-autoware-lanelet2-extension: 0.7.0-1 → 0.7.2-1
ros-humble-autoware-lanelet2-extension-dbgsym: 0.7.0-1 → 0.7.2-1
ros-humble-autoware-lanelet2-extension-python: 0.7.0-1 → 0.7.2-1
ros-humble-autoware-lanelet2-extension-python-dbgsym: 0.7.0-1 → 0.7.2-1
ros-humble-autoware-localization-msgs: 1.6.0-1 → 1.7.0-1
ros-humble-autoware-localization-msgs-dbgsym: 1.6.0-1 → 1.7.0-1
ros-humble-autoware-map-msgs: 1.6.0-1 → 1.7.0-1
ros-humble-autoware-map-msgs-dbgsym: 1.6.0-1 → 1.7.0-1
ros-humble-autoware-msgs: 1.6.0-1 → 1.7.0-1
ros-humble-autoware-perception-msgs: 1.6.0-1 → 1.7.0-1
ros-humble-autoware-perception-msgs-dbgsym: 1.6.0-1 → 1.7.0-1
ros-humble-autoware-planning-msgs: 1.6.0-1 → 1.7.0-1
ros-humble-autoware-planning-msgs-dbgsym: 1.6.0-1 → 1.7.0-1
ros-humble-autoware-sensing-msgs: 1.6.0-1 → 1.7.0-1
ros-humble-autoware-sensing-msgs-dbgsym: 1.6.0-1 → 1.7.0-1
ros-humble-autoware-system-msgs: 1.6.0-1 → 1.7.0-1
ros-humble-autoware-system-msgs-dbgsym: 1.6.0-1 → 1.7.0-1
ros-humble-autoware-utils: 1.0.0-1 → 1.4.0-1
ros-humble-autoware-v2x-msgs: 1.6.0-1 → 1.7.0-1
ros-humble-autoware-v2x-msgs-dbgsym: 1.6.0-1 → 1.7.0-1
ros-humble-autoware-vehicle-msgs: 1.6.0-1 → 1.7.0-1
ros-humble-autoware-vehicle-msgs-dbgsym: 1.6.0-1 → 1.7.0-1
ros-humble-behaviortree-cpp: 4.6.2-1 → 4.7.1-1
ros-humble-behaviortree-cpp-dbgsym: 4.6.2-1 → 4.7.1-1
ros-humble-bicycle-steering-controller: 2.44.0-1 → 2.45.0-1
ros-humble-bicycle-steering-controller-dbgsym: 2.44.0-1 → 2.45.0-1
ros-humble-bosch-locator-bridge: 2.1.13-1 → 2.1.14-1
ros-humble-bosch-locator-bridge-dbgsym: 2.1.13-1 → 2.1.14-1
ros-humble-bosch-locator-bridge-utils: 2.1.13-1 → 2.1.14-1
ros-humble-bosch-locator-bridge-utils-dbgsym: 2.1.13-1 → 2.1.14-1
ros-humble-camera-calibration: 3.0.7-1 → 3.0.8-1
ros-humble-clearpath-generator-gz: 1.3.0-1 → 1.3.1-1
ros-humble-clearpath-gz: 1.3.0-1 → 1.3.1-1
ros-humble-clearpath-simulator: 1.3.0-1 → 1.3.1-1
ros-humble-depth-image-proc: 3.0.7-1 → 3.0.8-1
ros-humble-depth-image-proc-dbgsym: 3.0.7-1 → 3.0.8-1
ros-humble-diagnostic-aggregator: 4.0.3-1 → 4.0.4-1
ros-humble-diagnostic-aggregator-dbgsym: 4.0.3-1 → 4.0.4-1
ros-humble-diagnostic-common-diagnostics: 4.0.3-1 → 4.0.4-1
ros-humble-diagnostic-remote-logging: 4.0.3-1 → 4.0.4-1
ros-humble-diagnostic-remote-logging-dbgsym: 4.0.3-1 → 4.0.4-1
ros-humble-diagnostic-updater: 4.0.3-1 → 4.0.4-1
ros-humble-diagnostic-updater-dbgsym: 4.0.3-1 → 4.0.4-1
ros-humble-diagnostics: 4.0.3-1 → 4.0.4-1
ros-humble-diff-drive-controller: 2.44.0-1 → 2.45.0-1
ros-humble-diff-drive-controller-dbgsym: 2.44.0-1 → 2.45.0-1
ros-humble-effort-controllers: 2.44.0-1 → 2.45.0-1
ros-humble-effort-controllers-dbgsym: 2.44.0-1 → 2.45.0-1
ros-humble-eigenpy: 3.10.3-1 → 3.11.0-1
ros-humble-eigenpy-dbgsym: 3.10.3-1 → 3.11.0-1
ros-humble-event-camera-py: 1.1.6-1 → 2.0.0-1
ros-humble-fastrtps: 2.6.9-1 → 2.6.10-1
ros-humble-fastrtps-dbgsym: 2.6.9-1 → 2.6.10-1
ros-humble-filters: 2.1.0-3 → 2.2.1-1
ros-humble-filters-dbgsym: 2.1.0-3 → 2.2.1-1
ros-humble-fkie-message-filters: 3.0.2-1 → 3.2.0-1
ros-humble-fkie-message-filters-dbgsym: 3.0.2-1 → 3.2.0-1
ros-humble-force-torque-sensor-broadcaster: 2.44.0-1 → 2.45.0-1
ros-humble-force-torque-sensor-broadcaster-dbgsym: 2.44.0-1 → 2.45.0-1
ros-humble-forward-command-controller: 2.44.0-1 → 2.45.0-1
ros-humble-forward-command-controller-dbgsym: 2.44.0-1 → 2.45.0-1
ros-humble-gpio-controllers: 2.44.0-1 → 2.45.0-1
ros-humble-gpio-controllers-dbgsym: 2.44.0-1 → 2.45.0-1
ros-humble-gripper-controllers: 2.44.0-1 → 2.45.0-1
ros-humble-gripper-controllers-dbgsym: 2.44.0-1 → 2.45.0-1
ros-humble-image-pipeline: 3.0.7-1 → 3.0.8-1
ros-humble-image-proc: 3.0.7-1 → 3.0.8-1
ros-humble-image-proc-dbgsym: 3.0.7-1 → 3.0.8-1
ros-humble-image-publisher: 3.0.7-1 → 3.0.8-1
ros-humble-image-publisher-dbgsym: 3.0.7-1 → 3.0.8-1
ros-humble-image-rotate: 3.0.7-1 → 3.0.8-1
ros-humble-image-rotate-dbgsym: 3.0.7-1 → 3.0.8-1
ros-humble-image-view: 3.0.7-1 → 3.0.8-1
ros-humble-image-view-dbgsym: 3.0.7-1 → 3.0.8-1
ros-humble-imu-sensor-broadcaster: 2.44.0-1 → 2.45.0-1
ros-humble-imu-sensor-broadcaster-dbgsym: 2.44.0-1 → 2.45.0-1
ros-humble-joint-state-broadcaster: 2.44.0-1 → 2.45.0-1
ros-humble-joint-state-broadcaster-dbgsym: 2.44.0-1 → 2.45.0-1
ros-humble-joint-trajectory-controller: 2.44.0-1 → 2.45.0-1
ros-humble-joint-trajectory-controller-dbgsym: 2.44.0-1 → 2.45.0-1
ros-humble-kitti-metrics-eval: 1.6.3-1 → 1.7.0-1
ros-humble-kitti-metrics-eval-dbgsym: 1.6.3-1 → 1.7.0-1
ros-humble-launch-pal: 0.11.0-1 → 0.12.1-1
ros-humble-libmavconn: 2.9.0-1 → 2.10.0-1
ros-humble-libmavconn-dbgsym: 2.9.0-1 → 2.10.0-1
ros-humble-mavlink: 2024.10.10-1 → 2025.5.5-1
ros-humble-mavros: 2.9.0-1 → 2.10.0-1
ros-humble-mavros-dbgsym: 2.9.0-1 → 2.10.0-1
ros-humble-mavros-extras: 2.9.0-1 → 2.10.0-1
ros-humble-mavros-extras-dbgsym: 2.9.0-1 → 2.10.0-1
ros-humble-mavros-msgs: 2.9.0-1 → 2.10.0-1
ros-humble-mavros-msgs-dbgsym: 2.9.0-1 → 2.10.0-1
ros-humble-mecanum-drive-controller: 2.44.0-1 → 2.45.0-1
ros-humble-mecanum-drive-controller-dbgsym: 2.44.0-1 → 2.45.0-1
ros-humble-microstrain-inertial-description: 4.6.0-1 → 4.6.1-1
ros-humble-microstrain-inertial-driver: 4.6.0-1 → 4.6.1-1
ros-humble-microstrain-inertial-driver-dbgsym: 4.6.0-1 → 4.6.1-1
ros-humble-microstrain-inertial-examples: 4.6.0-1 → 4.6.1-1
ros-humble-microstrain-inertial-msgs: 4.6.0-1 → 4.6.1-1
ros-humble-microstrain-inertial-msgs-dbgsym: 4.6.0-1 → 4.6.1-1
ros-humble-microstrain-inertial-rqt: 4.6.0-1 → 4.6.1-1
ros-humble-mola: 1.6.3-1 → 1.7.0-1
ros-humble-mola-bridge-ros2: 1.6.3-1 → 1.7.0-1
ros-humble-mola-bridge-ros2-dbgsym: 1.6.3-1 → 1.7.0-1
ros-humble-mola-demos: 1.6.3-1 → 1.7.0-1
ros-humble-mola-input-euroc-dataset: 1.6.3-1 → 1.7.0-1
ros-humble-mola-input-euroc-dataset-dbgsym: 1.6.3-1 → 1.7.0-1
ros-humble-mola-input-kitti-dataset: 1.6.3-1 → 1.7.0-1
ros-humble-mola-input-kitti-dataset-dbgsym: 1.6.3-1 → 1.7.0-1
ros-humble-mola-input-kitti360-dataset: 1.6.3-1 → 1.7.0-1
ros-humble-mola-input-kitti360-dataset-dbgsym: 1.6.3-1 → 1.7.0-1
ros-humble-mola-input-mulran-dataset: 1.6.3-1 → 1.7.0-1
ros-humble-mola-input-mulran-dataset-dbgsym: 1.6.3-1 → 1.7.0-1
ros-humble-mola-input-paris-luco-dataset: 1.6.3-1 → 1.7.0-1
ros-humble-mola-input-paris-luco-dataset-dbgsym: 1.6.3-1 → 1.7.0-1
ros-humble-mola-input-rawlog: 1.6.3-1 → 1.7.0-1
ros-humble-mola-input-rawlog-dbgsym: 1.6.3-1 → 1.7.0-1
ros-humble-mola-input-rosbag2: 1.6.3-1 → 1.7.0-1
ros-humble-mola-input-rosbag2-dbgsym: 1.6.3-1 → 1.7.0-1
ros-humble-mola-kernel: 1.6.3-1 → 1.7.0-1
ros-humble-mola-kernel-dbgsym: 1.6.3-1 → 1.7.0-1
ros-humble-mola-launcher: 1.6.3-1 → 1.7.0-1
ros-humble-mola-launcher-dbgsym: 1.6.3-1 → 1.7.0-1
ros-humble-mola-lidar-odometry: 0.7.1-1 → 0.7.2-1
ros-humble-mola-lidar-odometry-dbgsym: 0.7.1-1 → 0.7.2-1
ros-humble-mola-metric-maps: 1.6.3-1 → 1.7.0-1
ros-humble-mola-metric-maps-dbgsym: 1.6.3-1 → 1.7.0-1
ros-humble-mola-msgs: 1.6.3-1 → 1.7.0-1
ros-humble-mola-msgs-dbgsym: 1.6.3-1 → 1.7.0-1
ros-humble-mola-pose-list: 1.6.3-1 → 1.7.0-1
ros-humble-mola-pose-list-dbgsym: 1.6.3-1 → 1.7.0-1
ros-humble-mola-relocalization: 1.6.3-1 → 1.7.0-1
ros-humble-mola-relocalization-dbgsym: 1.6.3-1 → 1.7.0-1
ros-humble-mola-traj-tools: 1.6.3-1 → 1.7.0-1
ros-humble-mola-traj-tools-dbgsym: 1.6.3-1 → 1.7.0-1
ros-humble-mola-viz: 1.6.3-1 → 1.7.0-1
ros-humble-mola-viz-dbgsym: 1.6.3-1 → 1.7.0-1
ros-humble-mola-yaml: 1.6.3-1 → 1.7.0-1
ros-humble-mola-yaml-dbgsym: 1.6.3-1 → 1.7.0-1
ros-humble-mrpt-apps: 2.14.7-1 → 2.14.8-1
ros-humble-mrpt-apps-dbgsym: 2.14.7-1 → 2.14.8-1
ros-humble-mrpt-libapps: 2.14.7-1 → 2.14.8-1
ros-humble-mrpt-libapps-dbgsym: 2.14.7-1 → 2.14.8-1
ros-humble-mrpt-libbase: 2.14.7-1 → 2.14.8-1
ros-humble-mrpt-libbase-dbgsym: 2.14.7-1 → 2.14.8-1
ros-humble-mrpt-libgui: 2.14.7-1 → 2.14.8-1
ros-humble-mrpt-libgui-dbgsym: 2.14.7-1 → 2.14.8-1
ros-humble-mrpt-libhwdrivers: 2.14.7-1 → 2.14.8-1
ros-humble-mrpt-libhwdrivers-dbgsym: 2.14.7-1 → 2.14.8-1
ros-humble-mrpt-libmaps: 2.14.7-1 → 2.14.8-1
ros-humble-mrpt-libmaps-dbgsym: 2.14.7-1 → 2.14.8-1
ros-humble-mrpt-libmath: 2.14.7-1 → 2.14.8-1
ros-humble-mrpt-libmath-dbgsym: 2.14.7-1 → 2.14.8-1
ros-humble-mrpt-libnav: 2.14.7-1 → 2.14.8-1
ros-humble-mrpt-libnav-dbgsym: 2.14.7-1 → 2.14.8-1
ros-humble-mrpt-libobs: 2.14.7-1 → 2.14.8-1
ros-humble-mrpt-libobs-dbgsym: 2.14.7-1 → 2.14.8-1
ros-humble-mrpt-libopengl: 2.14.7-1 → 2.14.8-1
ros-humble-mrpt-libopengl-dbgsym: 2.14.7-1 → 2.14.8-1
ros-humble-mrpt-libposes: 2.14.7-1 → 2.14.8-1
ros-humble-mrpt-libposes-dbgsym: 2.14.7-1 → 2.14.8-1
ros-humble-mrpt-libros-bridge: 2.14.7-1 → 2.14.8-1
ros-humble-mrpt-libros-bridge-dbgsym: 2.14.7-1 → 2.14.8-1
ros-humble-mrpt-libslam: 2.14.7-1 → 2.14.8-1
ros-humble-mrpt-libslam-dbgsym: 2.14.7-1 → 2.14.8-1
ros-humble-mrpt-libtclap: 2.14.7-1 → 2.14.8-1
ros-humble-novatel-gps-driver: 4.2.0-1 → 4.2.1-1
ros-humble-novatel-gps-driver-dbgsym: 4.2.0-1 → 4.2.1-1
ros-humble-novatel-gps-msgs: 4.2.0-1 → 4.2.1-1
ros-humble-novatel-gps-msgs-dbgsym: 4.2.0-1 → 4.2.1-1
ros-humble-omni-base-2dnav: 2.12.1-1 → 2.15.0-1
ros-humble-omni-base-bringup: 2.9.0-1 → 2.10.1-1
ros-humble-omni-base-controller-configuration: 2.9.0-1 → 2.10.1-1
ros-humble-omni-base-description: 2.9.0-1 → 2.10.1-1
ros-humble-omni-base-gazebo: 2.4.0-1 → 2.8.0-1
ros-humble-omni-base-laser-sensors: 2.12.1-1 → 2.15.0-1
ros-humble-omni-base-navigation: 2.12.1-1 → 2.15.0-1
ros-humble-omni-base-rgbd-sensors: 2.12.1-1 → 2.15.0-1
ros-humble-omni-base-robot: 2.9.0-1 → 2.10.1-1
ros-humble-omni-base-simulation: 2.4.0-1 → 2.8.0-1
ros-humble-openvdb-vendor: 2.3.3-1 → 2.3.4-1
ros-humble-openvdb-vendor-dbgsym: 2.3.3-1 → 2.3.4-1
ros-humble-pal-gazebo-plugins: 4.0.5-1 → 4.0.6-1
ros-humble-pal-gazebo-plugins-dbgsym: 4.0.5-1 → 4.0.6-1
ros-humble-pid-controller: 2.44.0-1 → 2.45.0-1
ros-humble-pid-controller-dbgsym: 2.44.0-1 → 2.45.0-1
ros-humble-pinocchio: 3.4.0-2 → 3.5.0-1
ros-humble-pinocchio-dbgsym: 3.4.0-2 → 3.5.0-1
ros-humble-play-motion2: 1.5.1-1 → 1.5.2-1
ros-humble-play-motion2-dbgsym: 1.5.1-1 → 1.5.2-1
ros-humble-play-motion2-msgs: 1.5.1-1 → 1.5.2-1
ros-humble-play-motion2-msgs-dbgsym: 1.5.1-1 → 1.5.2-1
ros-humble-plotjuggler: 3.9.1-1 → 3.10.1-1
ros-humble-plotjuggler-dbgsym: 3.9.1-1 → 3.10.1-1
ros-humble-pmb2-2dnav: 4.11.0-1 → 4.15.0-1
ros-humble-pmb2-bringup: 5.7.0-1 → 5.8.2-1
ros-humble-pmb2-controller-configuration: 5.7.0-1 → 5.8.2-1
ros-humble-pmb2-description: 5.7.0-1 → 5.8.2-1
ros-humble-pmb2-gazebo: 4.3.0-1 → 4.7.0-1
ros-humble-pmb2-laser-sensors: 4.11.0-1 → 4.15.0-1
ros-humble-pmb2-navigation: 4.11.0-1 → 4.15.0-1
ros-humble-pmb2-rgbd-sensors: 4.11.0-1 → 4.15.0-1
ros-humble-pmb2-robot: 5.7.0-1 → 5.8.2-1
ros-humble-pmb2-simulation: 4.3.0-1 → 4.7.0-1
ros-humble-pose-broadcaster: 2.44.0-1 → 2.45.0-1
ros-humble-pose-broadcaster-dbgsym: 2.44.0-1 → 2.45.0-1
ros-humble-position-controllers: 2.44.0-1 → 2.45.0-1
ros-humble-position-controllers-dbgsym: 2.44.0-1 → 2.45.0-1
ros-humble-python-mrpt: 2.14.7-1 → 2.14.8-1
ros-humble-range-sensor-broadcaster: 2.44.0-1 → 2.45.0-1
ros-humble-range-sensor-broadcaster-dbgsym: 2.44.0-1 → 2.45.0-1
ros-humble-rig-reconfigure: 1.5.0-1 → 1.6.0-1
ros-humble-rig-reconfigure-dbgsym: 1.5.0-1 → 1.6.0-1
ros-humble-ros-gz: 0.244.16-2 → 0.244.17-1
ros-humble-ros-gz-bridge: 0.244.16-2 → 0.244.17-1
ros-humble-ros-gz-bridge-dbgsym: 0.244.16-2 → 0.244.17-1
ros-humble-ros-gz-image: 0.244.16-2 → 0.244.17-1
ros-humble-ros-gz-image-dbgsym: 0.244.16-2 → 0.244.17-1
ros-humble-ros-gz-interfaces: 0.244.16-2 → 0.244.17-1
ros-humble-ros-gz-interfaces-dbgsym: 0.244.16-2 → 0.244.17-1
ros-humble-ros-gz-sim: 0.244.16-2 → 0.244.17-1
ros-humble-ros-gz-sim-dbgsym: 0.244.16-2 → 0.244.17-1
ros-humble-ros-gz-sim-demos: 0.244.16-2 → 0.244.17-1
ros-humble-ros-ign: 0.244.16-2 → 0.244.17-1
ros-humble-ros-ign-bridge: 0.244.16-2 → 0.244.17-1
ros-humble-ros-ign-bridge-dbgsym: 0.244.16-2 → 0.244.17-1
ros-humble-ros-ign-gazebo: 0.244.16-2 → 0.244.17-1
ros-humble-ros-ign-gazebo-dbgsym: 0.244.16-2 → 0.244.17-1
ros-humble-ros-ign-gazebo-demos: 0.244.16-2 → 0.244.17-1
ros-humble-ros-ign-image: 0.244.16-2 → 0.244.17-1
ros-humble-ros-ign-image-dbgsym: 0.244.16-2 → 0.244.17-1
ros-humble-ros-ign-interfaces: 0.244.16-2 → 0.244.17-1
ros-humble-ros-ign-interfaces-dbgsym: 0.244.16-2 → 0.244.17-1
ros-humble-ros2-controllers: 2.44.0-1 → 2.45.0-1
ros-humble-ros2-controllers-test-nodes: 2.44.0-1 → 2.45.0-1
ros-humble-rqt-joint-trajectory-controller: 2.44.0-1 → 2.45.0-1
ros-humble-rqt-plot: 1.1.4-1 → 1.1.5-1
ros-humble-rviz-assimp-vendor: 11.2.16-1 → 11.2.17-1
ros-humble-rviz-common: 11.2.16-1 → 11.2.17-1
ros-humble-rviz-common-dbgsym: 11.2.16-1 → 11.2.17-1
ros-humble-rviz-default-plugins: 11.2.16-1 → 11.2.17-1
ros-humble-rviz-default-plugins-dbgsym: 11.2.16-1 → 11.2.17-1
ros-humble-rviz-ogre-vendor: 11.2.16-1 → 11.2.17-1
ros-humble-rviz-ogre-vendor-dbgsym: 11.2.16-1 → 11.2.17-1
ros-humble-rviz-rendering: 11.2.16-1 → 11.2.17-1
ros-humble-rviz-rendering-dbgsym: 11.2.16-1 → 11.2.17-1
ros-humble-rviz-rendering-tests: 11.2.16-1 → 11.2.17-1
ros-humble-rviz-visual-testing-framework: 11.2.16-1 → 11.2.17-1
ros-humble-rviz2: 11.2.16-1 → 11.2.17-1
ros-humble-rviz2-dbgsym: 11.2.16-1 → 11.2.17-1
ros-humble-self-test: 4.0.3-1 → 4.0.4-1
ros-humble-self-test-dbgsym: 4.0.3-1 → 4.0.4-1
ros-humble-septentrio-gnss-driver: 1.4.2-2 → 1.4.3-1
ros-humble-septentrio-gnss-driver-dbgsym: 1.4.2-2 → 1.4.3-1
ros-humble-slam-toolbox: 2.6.9-1 → 2.6.10-1
ros-humble-slam-toolbox-dbgsym: 2.6.9-1 → 2.6.10-1
ros-humble-slider-publisher: 2.4.0-1 → 2.4.1-1
ros-humble-spatio-temporal-voxel-layer: 2.3.3-1 → 2.3.4-1
ros-humble-spatio-temporal-voxel-layer-dbgsym: 2.3.3-1 → 2.3.4-1
ros-humble-steering-controllers-library: 2.44.0-1 → 2.45.0-1
ros-humble-steering-controllers-library-dbgsym: 2.44.0-1 → 2.45.0-1
ros-humble-stereo-image-proc: 3.0.7-1 → 3.0.8-1
ros-humble-stereo-image-proc-dbgsym: 3.0.7-1 → 3.0.8-1
ros-humble-talos-bringup: 2.0.1-1 → 2.0.2-1
ros-humble-talos-controller-configuration: 2.0.1-1 → 2.0.2-1
ros-humble-talos-description: 2.0.1-1 → 2.0.2-1
ros-humble-talos-description-calibration: 2.0.1-1 → 2.0.2-1
ros-humble-talos-description-inertial: 2.0.1-1 → 2.0.2-1
ros-humble-talos-robot: 2.0.1-1 → 2.0.2-1
ros-humble-tiago-2dnav: 4.9.0-1 → 4.11.0-1
ros-humble-tiago-bringup: 4.14.0-1 → 4.17.1-1
ros-humble-tiago-controller-configuration: 4.14.0-1 → 4.17.1-1
ros-humble-tiago-description: 4.14.0-1 → 4.17.1-1
ros-humble-tiago-gazebo: 4.3.0-1 → 4.7.0-1
ros-humble-tiago-gazebo-dbgsym: 4.3.0-1 → 4.7.0-1
ros-humble-tiago-laser-sensors: 4.9.0-1 → 4.11.0-1
ros-humble-tiago-navigation: 4.9.0-1 → 4.11.0-1
ros-humble-tiago-rgbd-sensors: 4.9.0-1 → 4.11.0-1
ros-humble-tiago-robot: 4.14.0-1 → 4.17.1-1
ros-humble-tiago-simulation: 4.3.0-1 → 4.7.0-1
ros-humble-tracetools-image-pipeline: 3.0.7-1 → 3.0.8-1
ros-humble-tracetools-image-pipeline-dbgsym: 3.0.7-1 → 3.0.8-1
ros-humble-tricycle-controller: 2.44.0-1 → 2.45.0-1
ros-humble-tricycle-controller-dbgsym: 2.44.0-1 → 2.45.0-1
ros-humble-tricycle-steering-controller: 2.44.0-1 → 2.45.0-1
ros-humble-tricycle-steering-controller-dbgsym: 2.44.0-1 → 2.45.0-1
ros-humble-turtlebot3-msgs: 2.3.0-1 → 2.4.0-1
ros-humble-turtlebot3-msgs-dbgsym: 2.3.0-1 → 2.4.0-1
ros-humble-ur-client-library: 1.9.0-1 → 2.0.0-1
ros-humble-ur-client-library-dbgsym: 1.9.0-1 → 2.0.0-1
ros-humble-velocity-controllers: 2.44.0-1 → 2.45.0-1
ros-humble-velocity-controllers-dbgsym: 2.44.0-1 → 2.45.0-1
ros-humble-wireless-msgs: 1.1.3-1 → 1.1.5-2
ros-humble-wireless-msgs-dbgsym: 1.1.3-1 → 1.1.5-2
ros-humble-wireless-watcher: 1.1.3-1 → 1.1.5-2
ros-humble-wireless-watcher-dbgsym: 1.1.3-1 → 1.1.5-2

Removed Packages [3]:

ros-humble-autoware-utils-dbgsym
ros-humble-plotjuggler-ros
ros-humble-plotjuggler-ros-dbgsym

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 Dabrowski
Adria Roig
Alberto Tudela
Alejandro Hernandez
Andrea Capodacqua
Antonio Brandi
Apex.AI, Inc.
Austin Hendrix
Bence Magyar
Bernd Pfrommer
Brandon Ong
Daan Wijffels
Davide Faconti
Emerson Knapp
Felix Exner
Guilhem Saurel
Jacob Perron
Jian Kang
Jordan Palacios
Jordi Pages
Jose Luis Blanco-Claraco
Jose-Luis Blanco-Claraco
Justin Carpentier
Louise Poubel
Luis Camero
M. Fatih Cırıt
Mabel Zhang
Mamoru Sobue
Miguel Company
Noel Jimenez
Olivier Kermorgant
P. J. Reed
Pyo
Rob Fisher
Roni Kreinin
Stefan Laible
Steve Macenski
Takagi, Isamu
Team Spatzenhirn
Tibor Dome
Tim Clephas
Timo Röhling
Tony Baltovski
Tully Foote
Vincent Rabaud
Vladimir Ermakov
Víctor Mayoral-Vilches
Yue Erro
Yutaka Kondo
kminoda
mitsudome-r

1 post - 1 participant

Read full topic

https://discourse.ros.org/t/new-packages-for-humble-hawksbill-2025-05-16/43801

ROS Discourse General: Next Client Library WG Meeting: Friday 16th May 2025 8AM PT

Hi,

The next meeting of the Client Library Working Group will be this Friday, 16th May 2025 at 8 AM Pacific Time.

Meeting link: https://meet.google.com/oij-atzj-znw
Meeting minutes and agenda: ROS 2 Client Libraries Working Group - Google Docs
Google group if you want to be notified of future meetings: https://groups.google.com/g/ros-2-client-library-wg

Everyone is welcome to join and bring their own topics for discussion, just add them to the agenda!

1 post - 1 participant

Read full topic

https://discourse.ros.org/t/next-client-library-wg-meeting-friday-16th-may-2025-8am-pt/43797

ROS Discourse General: New Packages for Noetic 2025-05-15

We’re happy to announce 3 new packages and 94 updates are now available in ROS Noetic. This sync was tagged as noetic/2025-05-15.

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

Package Updates for ROS Noetic

Added Packages [3]:

ros-noetic-gpmf-metadata-extractor: 3.0.2-1
ros-noetic-phidgets-current-inputs: 1.0.10-1
ros-noetic-ur15-moveit-config: 1.5.0-1

Updated Packages [94]:

ros-noetic-actionlib: 1.14.2-1 → 1.14.3-1
ros-noetic-actionlib-tools: 1.14.2-1 → 1.14.3-1
ros-noetic-camera-info-manager-lib: 2.0.3-1 → 3.0.2-1
ros-noetic-camera-info-manager-metadata-extractor: 2.0.3-1 → 3.0.2-1
ros-noetic-costmap-cspace: 0.17.7-1 → 0.18.0-1
ros-noetic-exiftool-metadata-extractor: 2.0.3-1 → 3.0.2-1
ros-noetic-exiv2-metadata-extractor: 2.0.3-1 → 3.0.2-1
ros-noetic-joystick-interrupt: 0.17.7-1 → 0.18.0-1
ros-noetic-lensfun-metadata-extractor: 2.0.3-1 → 3.0.2-1
ros-noetic-libexif-metadata-extractor: 2.0.3-1 → 3.0.2-1
ros-noetic-libphidget22: 1.0.9-1 → 1.0.10-1
ros-noetic-map-organizer: 0.17.7-1 → 0.18.0-1
ros-noetic-message-filters: 1.17.2-1 → 1.17.3-1
ros-noetic-mir-actions: 1.1.7-1 → 1.1.8-1
ros-noetic-mir-description: 1.1.7-1 → 1.1.8-1
ros-noetic-mir-driver: 1.1.7-1 → 1.1.8-1
ros-noetic-mir-dwb-critics: 1.1.7-1 → 1.1.8-1
ros-noetic-mir-gazebo: 1.1.7-1 → 1.1.8-1
ros-noetic-mir-msgs: 1.1.7-1 → 1.1.8-1
ros-noetic-mir-navigation: 1.1.7-1 → 1.1.8-1
ros-noetic-mir-robot: 1.1.7-1 → 1.1.8-1
ros-noetic-movie-publisher: 2.0.3-1 → 3.0.2-1
ros-noetic-movie-publisher-plugins: 2.0.3-1 → 3.0.2-1
ros-noetic-movie-publisher-plugins-copyleft: 2.0.3-1 → 3.0.2-1
ros-noetic-movie-publisher-plugins-nonfree: 2.0.3-1 → 3.0.2-1
ros-noetic-movie-publisher-plugins-permissive: 2.0.3-1 → 3.0.2-1
ros-noetic-neonavigation: 0.17.7-1 → 0.18.0-1
ros-noetic-neonavigation-common: 0.17.7-1 → 0.18.0-1
ros-noetic-neonavigation-launch: 0.17.7-1 → 0.18.0-1
ros-noetic-nodelet: 1.11.1-1 → 1.11.2-1
ros-noetic-nodelet-core: 1.11.1-1 → 1.11.2-1
ros-noetic-nodelet-topic-tools: 1.11.1-1 → 1.11.2-1
ros-noetic-obj-to-pointcloud: 0.17.7-1 → 0.18.0-1
ros-noetic-phidgets-accelerometer: 1.0.9-1 → 1.0.10-1
ros-noetic-phidgets-analog-inputs: 1.0.9-1 → 1.0.10-1
ros-noetic-phidgets-analog-outputs: 1.0.9-1 → 1.0.10-1
ros-noetic-phidgets-api: 1.0.9-1 → 1.0.10-1
ros-noetic-phidgets-digital-inputs: 1.0.9-1 → 1.0.10-1
ros-noetic-phidgets-digital-outputs: 1.0.9-1 → 1.0.10-1
ros-noetic-phidgets-drivers: 1.0.9-1 → 1.0.10-1
ros-noetic-phidgets-gyroscope: 1.0.9-1 → 1.0.10-1
ros-noetic-phidgets-high-speed-encoder: 1.0.9-1 → 1.0.10-1
ros-noetic-phidgets-humidity: 1.0.9-1 → 1.0.10-1
ros-noetic-phidgets-ik: 1.0.9-1 → 1.0.10-1
ros-noetic-phidgets-magnetometer: 1.0.9-1 → 1.0.10-1
ros-noetic-phidgets-motors: 1.0.9-1 → 1.0.10-1
ros-noetic-phidgets-msgs: 1.0.9-1 → 1.0.10-1
ros-noetic-phidgets-spatial: 1.0.9-1 → 1.0.10-1
ros-noetic-phidgets-temperature: 1.0.9-1 → 1.0.10-1
ros-noetic-planner-cspace: 0.17.7-1 → 0.18.0-1
ros-noetic-ros-comm: 1.17.2-1 → 1.17.3-1
ros-noetic-rosbag: 1.17.2-1 → 1.17.3-1
ros-noetic-rosbag-storage: 1.17.2-1 → 1.17.3-1
ros-noetic-roscpp: 1.17.2-1 → 1.17.3-1
ros-noetic-rosgraph: 1.17.2-1 → 1.17.3-1
ros-noetic-roslaunch: 1.17.2-1 → 1.17.3-1
ros-noetic-roslz4: 1.17.2-1 → 1.17.3-1
ros-noetic-rosmaster: 1.17.2-1 → 1.17.3-1
ros-noetic-rosmsg: 1.17.2-1 → 1.17.3-1
ros-noetic-rosnode: 1.17.2-1 → 1.17.3-1
ros-noetic-rosout: 1.17.2-1 → 1.17.3-1
ros-noetic-rosparam: 1.17.2-1 → 1.17.3-1
ros-noetic-rospy: 1.17.2-1 → 1.17.3-1
ros-noetic-rosservice: 1.17.2-1 → 1.17.3-1
ros-noetic-rostest: 1.17.2-1 → 1.17.3-1
ros-noetic-rostopic: 1.17.2-1 → 1.17.3-1
ros-noetic-roswtf: 1.17.2-1 → 1.17.3-1
ros-noetic-rqt-console: 0.4.13-1 → 0.4.14-1
ros-noetic-rqt-launch: 0.4.9-1 → 0.4.10-1
ros-noetic-rqt-moveit: 0.5.11-1 → 0.5.13-1
ros-noetic-safety-limiter: 0.17.7-1 → 0.18.0-1
ros-noetic-sdc21x0: 1.1.7-1 → 1.1.8-1
ros-noetic-septentrio-gnss-driver: 1.4.2-1 → 1.4.3-1
ros-noetic-topic-tools: 1.17.2-1 → 1.17.3-1
ros-noetic-track-odometry: 0.17.7-1 → 0.18.0-1
ros-noetic-trajectory-tracker: 0.17.7-1 → 0.18.0-1
ros-noetic-universal-robots: 1.4.0-1 → 1.5.0-1
ros-noetic-ur-calibration: 2.3.0-1 → 2.4.0-1
ros-noetic-ur-dashboard-msgs: 2.3.0-1 → 2.4.0-1
ros-noetic-ur-description: 1.4.0-1 → 1.5.0-1
ros-noetic-ur-gazebo: 1.4.0-1 → 1.5.0-1
ros-noetic-ur-robot-driver: 2.3.0-1 → 2.4.0-1
ros-noetic-ur10-moveit-config: 1.4.0-1 → 1.5.0-1
ros-noetic-ur10e-moveit-config: 1.4.0-1 → 1.5.0-1
ros-noetic-ur12e-moveit-config: 1.4.0-1 → 1.5.0-1
ros-noetic-ur16e-moveit-config: 1.4.0-1 → 1.5.0-1
ros-noetic-ur20-moveit-config: 1.4.0-1 → 1.5.0-1
ros-noetic-ur3-moveit-config: 1.4.0-1 → 1.5.0-1
ros-noetic-ur30-moveit-config: 1.4.0-1 → 1.5.0-1
ros-noetic-ur3e-moveit-config: 1.4.0-1 → 1.5.0-1
ros-noetic-ur5-moveit-config: 1.4.0-1 → 1.5.0-1
ros-noetic-ur5e-moveit-config: 1.4.0-1 → 1.5.0-1
ros-noetic-ur7e-moveit-config: 1.4.0-1 → 1.5.0-1
ros-noetic-xmlrpcpp: 1.17.2-1 → 1.17.3-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:

Atsushi Watanabe
Dirk Thomas
Felix Exner
G.A. vd. Hoorn
G.A. vd. Hoorn (TU Delft Robotics Institute)
Geoffrey Biggs
Isaac I.Y. Saito
Martin Günther
Martin Pecka
Michael Carroll
Tibor Dome
Vincenzo Di Pentima

1 post - 1 participant

Read full topic

https://discourse.ros.org/t/new-packages-for-noetic-2025-05-15/43785

ROS 2 Documentation

Wiki

Page

User

Planet ROS

Planet ROS - http://planet.ros.org

ROS Discourse General: Better Console Logging

ROS Discourse General: Cloudini: pointcloud compression for the rest of us

What to expect

Do you want to test it RIGHT NOW?

ROS Discourse General: New Packages for Noetic 2025-05-29 - FINAL

Package Updates for ROS Noetic - FINAL

Added Packages [3]:

Updated Packages [94]:

Removed Packages [0]:

Thank you

ROS Discourse General: ROS users meet up at VivaTech/NVIDIA GTC Paris

ROS Discourse General: ROSCon 2025 Sponsors + CFP Reminder

ROSCon 2025 Sponsors and CFP Reminder

Sponsorship

Now, without further ado, here are your ROSCon 2025 sponsors:

Gold Sponsors

Silver Sponsors

Bronze Sponsors

Startup Alley Sponsors

Video Archive and Live Stream Sponsor

Refreshment Sponsors

Lunch Sponsors

Diversity Scholarship Sponsors

ROS Discourse General: 👉 REMINDERS: ROSCon & ROSCon UK CFP / ROS Meetup Edinburgh & Singapore / Open Hardware Summit

REMINDERS: ROSCon & ROSCon UK CFP / ROS Meetup Edinburgh & Singapore / Open Hardware Summit

ROS Discourse General: Logging and Observability Discussion Preparation | Cloud Robotics WG Meeting 2025-06-02

ROS Discourse General: ROS Deliberation Community Group Meeting - June 2, 2025

ROS Discourse General: Boston Robot Hackers first meeting tomorrow - You are invited!

ROS Discourse General: ROS signing key migration guide

How to migrate (before June 1st)

Ubuntu/Debian

RHEL

How do I migrate (after June 1st)?

FAQ

Debian

RHEL

ROS Discourse General: Issues After Migrating to ROS 2 Jazzy: RViz Icons and Mesh Loading

1. RViz2 Icon Loading Errors

2. URDF Mesh File Not Found

ROS Discourse General: ROS News for the Week of May 19th, 2025

ROS News for the Week of May 19th, 2025

ROSCON 2025 TALK PROPOSALS ARE DUE IN 11 DAYS

Events

News

ROS

Got a Minute?

ROS Discourse General: :kilted: ROS 2 Kilted Kaiju Release!

ROS 2 Kilted Kaiju Release!

New Features and Enhancements

Tier 1 RMW Zenoh Support

Python Improvements

Action Introspection

New ROSBag Features

Better Windows Experience

Miscellaneous Features

A Community Effort

Top Test and Tutorial Party Testers

Finally, we’d like to announce the name of the next ROS 2 release for May 2026:

Lyrical Luth

ROS Discourse General: Open-source, low-cost precision tactile sensing

ROS Discourse General: New Packages for Jazzy Jalisco 2025-05-23

Package Updates for jazzy

Added Packages [55]:

Updated Packages [414]:

Removed Packages [0]:

ROS Discourse General: Optional automatic `source install/setup.bash` in cwd when using ROS 2 CLI commands

ROS Discourse General: Vote for the most useful Cloud Robotics guides!

Which of these topics would be most useful to you as a guide?

ROS Discourse General: Upcoming Distribution Freeze for Kilted Kaiju

ROS Discourse General: About 85% of all robotic arms now have ROS 2 drivers

ROS Discourse General: ICRA 2025 Open Thread

ICRA 2025 Open Thread

ROS Discourse General: Summer Hackathon with ROSCon 2025 Awards

ROS Discourse General: ROS News for the Week of May 12th, 2025