The call of the abi-compliance-checker might fail due to
errors. Possible reasons are the failed compilation of the
header files. To ease the analysis of the job logs the
additional printout might help.
Correct 'apt update' command.

Signed-off-by: Tino Lippold <Tino.Lippold@de.bosch.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

VER and PATH variables need to be dynamically replaced

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Having these headers and libraries lists in a not reproducible order
can generate random errors with abi-compliance-checker

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

When an xml descriptor file is provided, its path is not returned.
Consequently, run_abi_checker() fails due to an empty value.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

This value will be used to determine if the job should fail or succeed

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>