[Question] How is determined which package version is built? (ros_comm debs seems out of date and dont include latest patches)

[mikaelarguedas]

Hey there 👋

Thanks for all the work to provide ros-one debs!

I tried a ros_base setup with ROS-One debs on ubuntu Noble.

rostest fails due to outdated code

error log here

ERROR: 'RosTest' object has no attribute 'assert_'
  File "/usr/lib/python3.12/unittest/case.py", line 58, in testPartExecutor
    yield
  File "/usr/lib/python3.12/unittest/case.py", line 634, in run
    self._callTestMethod(testMethod)
  File "/usr/lib/python3.12/unittest/case.py", line 589, in _callTestMethod
    if method() is not None:
       ^^^^^^^^
  File "/opt/ros/one/lib/python3/dist-packages/rostest/runner.py", line 113, in fn
    self.assert_(self.test_parent is not None, "ROSTestParent initialization failed")

the deb version is:

Version: 1.16.0-14noble.20240822.1255

The last version tagged on the ros-o/ros_comm repo is 1.17.0

The commit needed to fix that particular issue is ros-o/ros_comm@c822b2f that has been pushed after 1.17.0 was tagged

So my question is: what is the recommended way to:

• Know what packages are up to date in the ros-o based debs ?
• What doc/workflow should I follow to request new releases ?

Thanks!

[rhaschke]

We build Jammy and Noble debs for x64 on a nightly basis now. However, those packages are released to jammy-testing and noble-testing repositories, which are manually synced to the production repos.
You are probably using the noble production repo, which had ros_comm 1.16.0-14.
I just synced the testing repos to the production ones to fix that.

[mikaelarguedas]

Thanks!

(sorry more questions just to get an overview of it)
Are syncs performed periodically? or on a per-request basis?
Based on your comment I take it that the aarch64 ones are built at a different frequency, is that correct ?
If so is there something similar to the ROS1 farm status page to be able to see if the versions are different between 2 arches ?

[rhaschke]

Are syncs performed periodically? or on a per-request basis?

We didn't establish a policy for that yet. For now, I would say: syncs are performed on request (here as an issue).

Based on your comment I take it that the aarch64 ones are built at a different frequency, is that correct ?

Correct. ARM builds are triggered manually, because they require to fire up an external ARM runner.

If so is there something similar to the ROS1 farm status page to be able to see if the versions are different between 2 arches ?

No, we don't yet have status pages. A contribution to feed a yaml? database during building and generate corresponding status pages from it after reprepro import is highly welcome ;-)
How are these status pages generated by the ROS build farm?