hi everyone, tl;dr can anyone form the cyborg team approve https://review.opendev.org/c/openstack/cyborg/+/949772 As you all are likely aware when we updated the testing runtime for 2025.2 and unfroze the setuptool version by the removal of python 3.9 support setuptools 80 became available in ci. this resulted in any project that still religed on PBRs `wsgi_scripts` extension failing to deploy under devstack if they had note converted to providing a pyproject.toml Stephen finucan and i started trying to prepare openstack for this change 18 months ago but with the release of setup-tools 80 it became much more important given it blocked gates. while there are a lot of patches still in flight for other project https://review.opendev.org/q/topic:%22pip-23.1-support%22 im reaching out specifically related to https://review.opendev.org/c/openstack/cyborg/+/949772 because the cyborg job on the nova repo has been failing for several weeks now. this change should fix the failing jobs on the cyborg repo too but the nova team does still check the status of the non voting job in our check pipeline too. i pushed https://review.opendev.org/c/openstack/cyborg/+/949772 for review 20 days ago and i have a follow up to remove the jammy jobs https://review.opendev.org/c/openstack/cyborg/+/949777/1 to align cyborgs testing to the testing runtime for this release. in general the cyborg repo seam to have a number of bot and procedural patches open for the last few release https://review.opendev.org/q/project:openstack/cyborg+status:open so its not clear if any of the current core team member are active with that said there have been a few patches merged in the last 6 months https://review.opendev.org/q/project:openstack/cyborg+status:merged so the cyborg team does not seam to be entirely inactive currently. if anyone form the cyborg team sees this could you please review those patches to unblock the cyborg gate. if we don't see movent on this after m2 ill probably propose removing the cyborg job form the nova check line since its currently just wasting ci time given it always fails. regard sean. ps note for the cyborg team https://review.opendev.org/c/openstack/cyborg/+/949772 also complete the cyborg part of https://github.com/openstack/governance/blob/master/goals/proposed/migrate-f... as that is the general approach we had selected to addressing the packaging issue sand adopting pyporejct.toml was required to make that possible since it was not merged before the setuptool changes.