Arvados

23373-trixie-ansible @ 1c4c3dbc7bbae6b3c7370ad5f8421f7c83dcb0bb

It turns out the only thing we needed to do to support trixie was add it to our table of package translations. But using it for more development revealed some minor problems with the work done in #23310, so this branch refines that.

• All agreed upon points are implemented / addressed. Describe changes from pre-implementation design.
  • Yes
• Anything not implemented (discovered or discussed during work) has a follow-up story.
  • N/A
• Code is tested and passing, both automated and manual, what manual testing was done is described.
  • I have set up a new Debian 13 development VM based on running it.
• Tested code incorporates recent main branch changes.
  • Yes
• New or changed UI/UX and has gotten feedback from stakeholders.
  • N/A
• Documentation has been updated.
  • N/A
• Behaves appropriately at the intended scale (describe intended scale).
  • No change - Slightly improves things by avoiding a redundant Ruby install
• Considered backwards and forwards compatibility issues between client and server.
  • N/A
• Follows our coding standards and GUI style guidelines.
  • N/A to Ansible

Lgtm!