5.4.0-2 not compatible with Ansible 2.15.2

[Drew N]

The upstream released 6.12.0 of the Ansible-lint package on February 1, 2023, containing the following fix:
"Add support for Ansible 2.15 (#2960)"
As Jammy is now shipping Ansible 2.15.2 that means that Ansible-lint 6.12.0 or higher is required, but it currently has 5.4.0-2. Given that Jammy is an LTS release I ask that Ansible-lint be upgraded to match the current Ansible and Ansible-core packages in use.
Thank you for your time.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Troels Arvin (troels-w)]

According to https://github.com/ansible/ansible-lint/discussions/3520 it may also have to do with the Python version. No matter what, I agree that an updated ansible-lint package is needed. (I'm affected by the bug, as well.)

[Sorin Sbarnea (ssbarnea)]

As one of the maintainers of the upstream ansible-lint project, I can say that the included version with Ubuntu is so outdated that is not of much practical use.

It should also be noted that ansible-lint versions are much safer to update than ansible-core ones. One might think that 6.x in linter is major, but is not major in any way than the "15" in 2.15 ansible-core version.

Now the big issue is that apparently Jammy LTS installs ansible-core 2.10 which ended EOL before even Jammy went out! see https://docs.ansible.com/ansible/latest/reference_appendices/release_and_maintenance.html -- which reports EOL date 23 May 2022

Basically having ansible-lint outdated is more of a sign of a much bigger problem with Jammy itself.

The good news is that apparently the system python is 3.10, which will allow installing latest stable versions of both, ansible-core and ansible-lint... via pip, as I did not see deb being made available.