Re: [yocto-patches] [yocto-autobuilder-helper][dunfell][PATCH] config.json: fix cvecheck iputils warning

["Antonin Godard" <antonin.godard@bootlin.com>]

On Thu Sep 24, 2026 at 8:51 AM CEST, Yoann Congal wrote:
> On Wed Sep 23, 2026 at 5:41 PM CEST, Antonin Godard via lists.yoctoproject.org wrote:
>> On Yocto Dunfell, an EOL version of Yocto, we consistently have the
>> following warning showed during the metrics job:
>>
>>   WARNING: iputils-s20190709-r0 do_cve_check: iputils: Failed to compare
>>   s20190709 < 20250602 for CVE-2025-47268
>>
>> This is because upstream stopped adding the leading "s" to their
>> version. Since we can't patch Yocto dunfell anymore, as a workaround set
>> the version of iputils so that the comparison passes. This makes the
>> cvecheck class show the following warning instead, which is expected:
>>
>>   WARNING: iputils-20190709-r0 do_cve_check: Found unpatched CVE
>>   (CVE-2025-47268), for more information check
>>   /build/tmp/work/aarch64-poky-linux/iputils/20190709-r0/temp/cve.log
>>
>> Which isn't shown on the Autobuilder thanks to CVE_CHECK_SHOW_WARNINGS =
>> '0'.
>>
>> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
>> ---
>> Test build (not pushed to metrics repo):
>> https://autobuilder.yoctoproject.org/valkyrie/#/builders/103/builds/4111
>
> Hello,
>
> Thanks! (I had that on my todolist for the longest time but never got to
> it)
>
> Alternatively, since the metrics is the last thing we do actually
> maintain, we could actually fix the recipe (if the fix is non intrusive,
> obviously).
>
> FYI, dunfell had 2 recent fixes for the metrics job.

Ha, I didn't dare sending a patch for dunfell :) Well, the same fix (setting PV to
"20190709") could be done in the recipe directly. If you consider that
non-invasive, I can send it today.

Antonin