Ubuntu
ros-ros-comm package

FTBFS against python 3.12

Bug #2051585 reported by Dan Bungert
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ros-ros-comm (Ubuntu)
Triaged
Undecided
Unassigned

Bug Description

ros-ros-comm contains some usage of deprecated unittest concepts that are now fully gone in python3.12. In addition to `assert_`, which is already fixed in the Debian packaging, there is also usage of assertEquals and failIf.

Dan Bungert (dbungert)
Changed in ros-ros-comm (Ubuntu):
assignee: nobody → Dan Bungert (dbungert)
status: New → In Progress
Revision history for this message
Dan Bungert (dbungert) wrote :

untested patch, was tangled with other python issues and had no plan on how to test it appropriately

Changed in ros-ros-comm (Ubuntu):
assignee: Dan Bungert (dbungert) → nobody
status: In Progress → Triaged
Chris Peterson (cpete)
Changed in ros-ros-comm (Ubuntu):
assignee: nobody → Chris Peterson (cpete)
status: Triaged → In Progress
Jeremy Bícha (jbicha)
tags: added: noble update-excuse
Revision history for this message
Chris Peterson (cpete) wrote :

Unassigning myself. The fix for assert_ in the Debian packaging ended up not being complete and the complete fix to make this package be python3.12 compliant is going to take significant time. Since it's not currently blocking any transitions and may end up not being important to fix for noble anyways, I think the priority on fixing this is low.

At the time of writing, the transition tracker states this package is the last blocker on the tinyxml2 transition:

https://ubuntu-archive-team.ubuntu.com/transitions/html/html/auto-tinyxml2.html

but I've confirmed this isn't the case.

And even though it's FTBFS on python3.12, it doesn't appear to be blocking the python3-defaults transition either.

Changed in ros-ros-comm (Ubuntu):
status: In Progress → New
status: New → Triaged
assignee: Chris Peterson (cpete) → nobody
Revision history for this message
Chris Peterson (cpete) wrote :

Incomplete patch. I tried to keep the code changes small, so I used a custom class to patch the deprecated test methods. It revealed further sections of deprecated code usage, but it may or may not be breaking the custom unittest class loading (see the assert_ patch). At this point I found the delay between build time and test failure to be prohibitive.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.