wrong use of config-manager arguments in rhel 10 for lyrical

[mfruhner]

Generated by Generative AI

No response

Operating System:

Linux ... 6.6.87.2-microsoft-standard-WSL2 #1 SMP PREEMPT_DYNAMIC Thu Jun 5 18:30:46 UTC 2025 x86_64 GNU/Linux

ROS version or commit hash:

lyrical

RMW implementation (if applicable):

No response

RMW Configuration (if applicable):

When setting up lyrical for testing in a RHEL 10 (AlmaLinux) WSL instance, I noticed that the steps to enable the ros-testing repos are wrong / outdated:

https://docs.ros.org/en/lyrical/Installation/Testing.html

sudo dnf config-manager setopt ros2-testing.enabled=1
sudo dnf config-manager setopt ros2.enabled=0

The infos in the rolling release are updated /correct:

sudo dnf config-manager --set-enabled ros2-testing
sudo dnf config-manager --set-disabled ros2

Client library (if applicable):

No response

'ros2 doctor --report' output

No response

Steps to reproduce issue

sudo dnf config-manager setopt ros2.enabled=0

Expected behavior

no error

Actual behavior

missing argument error

Additional information

No response

[kscottz]

I dropped it on our board for investigation.

[yukaitung]

@mfruhner Did you get any errors when testing the examples after installing ROS 2? 🤔

[mfruhner]

actually, I can not get the examples to work using fastdds ...
I dont know if this is related to WSL2, but the listener does not receive any messages.
I even did a full reinstall of the distro.

HOWEVER, it works when using zenoh. I installed the lyrical prebuilt binaries and added the testing repos again to install zenoh.

I also tried with a local fastdds config. I can see the node and the topic, but no messages are received:

[yukaitung]

I have to install ros-lyrical-rmw-fastrtps-cpp, otherwise the example fails. I am using an AMD64 machine (not a VM). I am afraid the dependency is incorrect because I need to install additional packages to compile the C++/Python packages as well.

[mfruhner]

I let the listener sit for a while and suddenly the messages came through:

Restarting the listener again fails to listen: