Fix version comparsion

[felixfontein]

Currently the sanity check for the installed ansible-core version in the build role fails as 2.13.0rc1 > 2.13.0 according to distutils.version.LooseVersion, which is used by ansible-core's version test. (StrictVersion and SemanticVersion do not accept 2.13.0rc1, so they don't help here.)

I've added an internal filter _antsibull_packaging_version to the role that is used for this comparison. It uses packaging.version, which handles the version numbers correctly.

[felixfontein]

https://github.com/ansible-community/antsibull/runs/6455989150?check_suite_focus=true shows how this currently fails (since 2.13.0 has been released).

[felixfontein]

This also makes the tests in ansible-build-data pass again (failure example: https://github.com/ansible-community/ansible-build-data/runs/6458171874?check_suite_focus=true).

[dmsimard]

I've added an internal filter _antsibull_packaging_version to the role that is used for this comparison. It uses packaging.version, which handles the version numbers correctly.

Appreciate the fix, it's short and simple enough.

Currently the sanity check for the installed ansible-core version in the build role fails as 2.13.0rc1 > 2.13.0 according to distutils.version.LooseVersion, which is used by ansible-core's version test. (StrictVersion and SemanticVersion do not accept 2.13.0rc1, so they don't help here.)

Should this be considered an issue in ansible-core, then ?

[felixfontein]

It would definitely nice if ansible-core's filter would support packaging.version as well, but that will not happen before 2.14.0. If I remember I'll create an issue or a PR for that...

[felixfontein]

@dmsimard thanks for reviewing!