shared: macros: oval: Fix evr datatype for dpkg-based distros

[dodys]

Fixes #13879

[dodys]

@Mab879 @jan-cerny @marcusburghardt the ctests failures in Debian and Ubuntu seems to be related to the fact of build supporting 5.11 and not 5.11.1. Should we consider re-opening this: #11903 but instead of 5.11.2, we target at least 5.11.1?

[jan-cerny]

Hi @dodys I haven't verified this but I assume that it should be safe to use the 5.11.2 version now because RHEL 7 is after end-of-life. You would have to try to change the OVAL version and see if the CI test fail or pass.

[dodys]

Hi @dodys I haven't verified this but I assume that it should be safe to use the 5.11.2 version now because RHEL 7 is after end-of-life. You would have to try to change the OVAL version and see if the CI test fail or pass.

I believe that 5.11.2 will be a problem on Ubuntu's/Debian's side as 5.11.1 is the supported version in 22.04 and 24.04 according to oscap --version. Ubuntu 22.04 has openscap 1.2.17 and Ubuntu 24.04 has openscap 1.3.9.
Do you happen to remember when 5.11.2 was added to openscap? Because I've tested also openscap 1.4.1 and it also returns 5.11.1

Ok, I took a look at openscap code, and perhaps relying on oscap --version might be not accurate, as still today in the main branch it is set to 5.11.1:
https://github.com/OpenSCAP/openscap/blob/main/src/OVAL/oval_agent_api_impl.h#L38

Edit: it seems I can validate an OVAL 5.11.2 in 22.04 and 24.04 without issues, it might be that we can bump to 5.11.2.

[jan-cerny]

OK, then let's try 5.11.2 !

[dodys]

rebased this PR on top of #13966 and ctests are now passing.

[openshift-ci]

@dodys: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-aws-openshift-node-compliance	0664d00	link	true	/test e2e-aws-openshift-node-compliance

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.