bodnuti

Deterministic checks of Yocto Project & OpenEmbedded patches.

[PATCH 00/82] Blacksail pull request

List
openembedded-devel
Thread
lore
Author
ankur.tyagi85@gmail.com
Last message
2026-10-15 05:45
Result
8 findings, 4 errors ยท 7 style findings
Checked against
meta-openembedded master
Base
afc85af443e4
Note
checked against master at afc85af443e4, before the first of its patches that had landed
Upstream
probably 42/82 applied
AutoBuilder
2 builds: 1 passed, 0 with warnings, 1 failed

[PATCH 01/82] readme: update maintainer

[PATCH 02/82] Revert "libpwquality: remove recipe (moved to oe-core)"

error patchtest test_patch.test_upstream_status_presence_format
Upstream-Status is present only after the patch scissors. It must be placed in the patch header before the scissors line.
error oelint oelint.var.mandatoryvar.SUMMARY meta-oe/recipes-extended/libpwquality/libpwquality_1.4.5.bb:1
Variable 'SUMMARY' should be set
1DESCRIPTION = "Library for password quality checking and generating random passwords"2HOMEPAGE = "https://github.com/libpwquality/libpwquality"3SECTION = "devel/lib"4
Show 7 style findings
warning oelint oelint.newline.consecutive meta-oe/recipes-extended/libpwquality/libpwquality_1.4.5.bb:16
Consecutive blank lines should be avoided
13"14SRCREV = "5490e96a3dd6ed7371435ca5b3ccef98bdb48b5a"151617inherit autotools-brokensep gettext18inherit_defer ${@bb.utils.contains('PACKAGECONFIG', 'python3', 'setuptools3-base', '', d)}19
warning oelint oelint.var.order.PACKAGECONFIG meta-oe/recipes-extended/libpwquality/libpwquality_1.4.5.bb:32
'PACKAGECONFIG' should be placed before 'EXTRA_OECONF'
29                 --with-securedir=${base_libdir}/security \30"3132PACKAGECONFIG ??= "${@bb.utils.contains('DISTRO_FEATURES', 'pam', 'pam', '', d)} python3"33PACKAGECONFIG[pam] = "--enable-pam,--disable-pam,libpam"34PACKAGECONFIG[python3] = "--enable-python-bindings --with-python-rev=${PYTHON_BASEVERSION} --with-python-binary=${STAGING_BINDIR_NATIVE}/python3-native/python3 --with-pythonsitedir=${PYTHON_SITEPACKAG35
info oelint oelint.var.bbclassextend meta-oe/recipes-extended/libpwquality/libpwquality_1.4.5.bb:1
BBCLASSEXTEND should be set if possible
1DESCRIPTION = "Library for password quality checking and generating random passwords"2HOMEPAGE = "https://github.com/libpwquality/libpwquality"3SECTION = "devel/lib"4
info oelint oelint.var.suggestedvar.BUGTRACKER meta-oe/recipes-extended/libpwquality/libpwquality_1.4.5.bb:1
Variable 'BUGTRACKER' should be set
1DESCRIPTION = "Library for password quality checking and generating random passwords"2HOMEPAGE = "https://github.com/libpwquality/libpwquality"3SECTION = "devel/lib"4
info oelint oelint.var.suggestedvar.CVE_PRODUCT meta-oe/recipes-extended/libpwquality/libpwquality_1.4.5.bb:1
Variable 'CVE_PRODUCT' should be set
1DESCRIPTION = "Library for password quality checking and generating random passwords"2HOMEPAGE = "https://github.com/libpwquality/libpwquality"3SECTION = "devel/lib"4
info oelint oelint.vars.multilineident meta-oe/recipes-extended/libpwquality/libpwquality_1.4.5.bb:11
On a multiline assignment, line indent is desirable. 4 set, 11 desirable
 8DEPENDS = "cracklib" 910SRC_URI = "git://github.com/libpwquality/libpwquality;branch=master;protocol=https \11    file://0001-Use-setuptools-instead-of-distutils.patch \12    file://0002-Makefile.am-respect-PYTHONSITEDIR.patch \13"14SRCREV = "5490e96a3dd6ed7371435ca5b3ccef98bdb48b5a"
info oelint oelint.vars.multilineident meta-oe/recipes-extended/libpwquality/libpwquality_1.4.5.bb:12
On a multiline assignment, line indent is desirable. 4 set, 11 desirable
 910SRC_URI = "git://github.com/libpwquality/libpwquality;branch=master;protocol=https \11    file://0001-Use-setuptools-instead-of-distutils.patch \12    file://0002-Makefile.am-respect-PYTHONSITEDIR.patch \13"14SRCREV = "5490e96a3dd6ed7371435ca5b3ccef98bdb48b5a"15

[PATCH 03/82] pcsc-lite: create pcscd user and group also via useradd

[PATCH 04/82] Revert "gnome-shell-extensions: upgrade 50.3 -> 51.0"

[PATCH 05/82] Revert "gnome-shell: upgrade 50.4 -> 51.0"

error patchtest test_patch.test_signed_off_by_presence
A patch file has been added without a Signed-off-by tag: '0002-calendar-server-Fix-build-failure-with-libical-4.patch'
warning oelint oelint.file.patchsignedoff meta-gnome/recipes-gnome/gnome-shell/gnome-shell_50.4.bb:34
Patch '0002-calendar-server-Fix-build-failure-with-libical-4.patch' should contain a Signed-off-by entry
31REQUIRED_DISTRO_FEATURES += "gobject-introspection-data"3233SRC_URI += "file://0001-shell-app-usage.c-only-include-x11-headers-if-HAVE_X.patch"34SRC_URI += "file://0002-calendar-server-Fix-build-failure-with-libical-4.patch"35SRC_URI[archive.sha256sum] = "c531939539db316a41aef23670370abd1330d3254f84bcb0f9f4dae5d6e362cf"3637PACKAGECONFIG ??= " \

[PATCH 06/82] Revert "mutter: upgrade 50.4 -> 51.0"

[PATCH 07/82] libwebsockets: patch CVE-2026-19773

[PATCH 08/82] libwebsockets: patch CVE-2026-78161

[PATCH 09/82] nginx: set status for CVE-2026-90439

[PATCH 10/82] capnproto: ignore CVE-2026-59704

probably applied to master as 52ef4850f46d

[PATCH 11/82] civetweb: ignore CVE-2026-5789

probably applied to master as 187e2890da3b

[PATCH 12/82] dovecot: ignore already fixed CVEs

probably applied to master as ead8f70fa63e

[PATCH 13/82] eject: ignore CVE-2026-28065

probably applied to master as 6ed50c8a2b55

[PATCH 14/82] gpsd: patch CVE-2026-58459

probably applied to master as 13d46c5cb2c5

[PATCH 15/82] bcc: correct CVE_PRODUCT mapping

probably applied to master as 567dad77137b

[PATCH 16/82] dool: patch CVE-2026-56651

probably applied to master as 0a807241ffd9

[PATCH 17/82] dool: patch CVE-2026-56652

probably applied to master as 0b890c47451f

[PATCH 18/82] haveged: ignore CVE-2026-41054

probably applied to master as 997a8ab5af8a

[PATCH 19/82] gpm: ignore CVE-2025-4558

probably applied to master as 34576300e00a

[PATCH 20/82] gerbera: ignore CVE-2025-23386

probably applied to master as bef03c1c45d7

[PATCH 21/82] libde265: patch CVE-2026-49295

probably applied to master as 2bba25a0e672

[PATCH 22/82] libde265: patch CVE-2026-49337

probably applied to master as 6f9970147f42

[PATCH 23/82] libde265: patch CVE-2026-49346

probably applied to master as a1a902b3b985

[PATCH 24/82] libde265: patch CVE-2026-54240 and CVE-2026-54241

probably applied to master as 8cd6a6b15a52

[PATCH 25/82] hdf5: patch CVE-2026-17572

probably applied to master as 5468d43cbd50

[PATCH 26/82] hdf5: patch CVE-2026-17573

probably applied to master as 5ac7a070e3d5

[PATCH 27/82] hdf5: patch CVE-2026-17574

probably applied to master as 0cdf123177c9

[PATCH 28/82] hdf5: patch CVE-2026-19025

probably applied to master as 796a3d4adba5

[PATCH 29/82] iniparser: mark CVE-2025-0633 pached

probably applied to master as 58ca5eac9157

[PATCH 30/82] jq: ignore already fixed CVEs

warning oelint oelint.vars.mispell.unknown meta-oe/recipes-devtools/jq/jq_1.8.2.bb:53
'CVE_STATUS_FIXED_ALREADY' is unknown. Consider adding it via --constantmods
50BBCLASSEXTEND = "native"5152CVE_STATUS_GROUPS += "CVE_STATUS_FIXED_ALREADY"53CVE_STATUS_FIXED_ALREADY[status] = "fixed-version: The issue is fixed in v1.8.2"54CVE_STATUS_FIXED_ALREADY = "CVE-2026-33948 CVE-2026-39979 CVE-2026-40164 CVE-2026-44777"
warning oelint oelint.vars.mispell.unknown meta-oe/recipes-devtools/jq/jq_1.8.2.bb:54
'CVE_STATUS_FIXED_ALREADY' is unknown. Consider adding it via --constantmods
5152CVE_STATUS_GROUPS += "CVE_STATUS_FIXED_ALREADY"53CVE_STATUS_FIXED_ALREADY[status] = "fixed-version: The issue is fixed in v1.8.2"54CVE_STATUS_FIXED_ALREADY = "CVE-2026-33948 CVE-2026-39979 CVE-2026-40164 CVE-2026-44777"

[PATCH 31/82] libiec61850: mark CVE-2024-45969 patched

probably applied to master as 0f8cf2b6f7ac

[PATCH 32/82] libnfs: patch CVE-2026-53689

[PATCH 33/82] libnfs: patch CVE-2026-57918

[PATCH 34/82] libssh: ignore CVE-2025-14821

[PATCH 35/82] libssh: mark CVEs patched

[PATCH 36/82] libssh: ignore CVE-2026-59851

[PATCH 37/82] miniupnpd: patch CVE-2026-107159

probably applied to master as 2c888ebe7549

[PATCH 38/82] libyang: patch CVE-2026-41401

probably applied to master as d015851ed949

[PATCH 39/82] tinyproxy: patch CVE-2026-31842

probably applied to master as 568c569c2fe3

[PATCH 40/82] tinyproxy: patch CVE-2026-54387

probably applied to master as c3796d630f6b

[PATCH 41/82] tinyproxy: patch CVE-2026-55202

probably applied to master as 9b938c16164e

[PATCH 42/82] wolfssl: mark CVEs patched

probably applied to master as 28737626214c

[PATCH 43/82] python3-gunicorn: mark CVE-2024-1135 patched

probably applied to master as ed7807e83b48

[PATCH 44/82] pgpool2: upgrade 4.7.2 -> 4.7.3

[PATCH 45/82] smarty: upgrade 5.8.4 -> 5.8.5

[PATCH 46/82] python3-astroid: upgrade 4.3.2 -> 4.3.3

[PATCH 47/82] python3-django: upgrade 6.0.8 -> 6.0.9

[PATCH 48/82] python3-django: upgrade 5.2.17 -> 5.2.18

[PATCH 49/82] python3-tzdata: upgrade 2026.4 -> 2026.5

[PATCH 50/82] python3-werkzeug: upgrade 3.1.8 -> 3.1.9

[PATCH 51/82] python3-zeroconf: upgrade 0.151.3 -> 0.151.5

[PATCH 52/82] swagger-ui: upgrade 5.33.0 -> 5.33.1

[PATCH 53/82] openvpn: ignore CVE-2026-84256

[PATCH 54/82] openvpn: patch CVE-2026-88964

[PATCH 55/82] openvpn: patch CVE-2026-84790

[PATCH 56/82] python3-eventlet: mark CVE-2023-29483 fixed

probably applied to master as 96cedce0465f

[PATCH 57/82] cjson: patch CVE-2026-87933

probably applied to master as c8dd8428d05b

[PATCH 58/82] smarty: mark CVE-2026-82531 patched

probably applied to master as df5f8478c4a7

[PATCH 59/82] ntopng: patch CVE-2026-84990

probably applied to master as 4e8a7265bde5

[PATCH 60/82] ntopng: patch CVE-2026-86090 and CVE-2026-86091

probably applied to master as ba9537ae1f83

[PATCH 61/82] sngrep: patch CVE-2026-90558

probably applied to master as 30acdca70627

[PATCH 62/82] strongswan: patch CVE-2026-78123

[PATCH 63/82] strongswan: patch CVE-2026-78124

[PATCH 64/82] strongswan: patch CVE-2026-78126

[PATCH 65/82] strongswan: patch CVE-2026-78127

[PATCH 66/82] strongswan: patch CVE-2026-78129

[PATCH 67/82] strongswan: patch CVE-2026-78133

[PATCH 68/82] strongswan: patch CVE-2026-78131

[PATCH 69/82] strongswan: patch CVE-2026-78130

[PATCH 70/82] strongswan: patch CVE-2026-78132

[PATCH 71/82] strongswan: patch CVE-2026-78135

[PATCH 72/82] strongswan: patch CVE-2026-78134

[PATCH 73/82] tesseract: patch CVE-2026-88052

probably applied to master as 8ee82e432c12

[PATCH 74/82] tesseract: patch CVE-2026-88048

probably applied to master as 0aa1782e9588

[PATCH 75/82] tesseract: patch CVE-2026-88049

probably applied to master as 909d433ca08a

[PATCH 76/82] tesseract: patch CVE-2026-88050

probably applied to master as cc2b58f13566

[PATCH 77/82] tesseract: patch CVE-2026-88047

probably applied to master as 2ba3ed5dc8da

[PATCH 78/82] tesseract: patch CVE-2026-88051

probably applied to master as 4c928862f5dc

[PATCH 79/82] tesseract: patch CVE-2026-88054

probably applied to master as b9c3d34642a3

[PATCH 80/82] gpsd: patch CVE-2026-60122

probably applied to master as 031bdc4ab3e6

[PATCH 81/82] apache2: fix build with OpenSSL 4

error patchtest test_patch.test_signed_off_by_presence
A patch file has been added without a Signed-off-by tag: '0011-mod_md-Add-OpenSSL-4.0-compatibility.patch'
warning oelint oelint.file.patchsignedoff meta-webserver/recipes-httpd/apache2/apache2_2.4.68.bb:8
Patch '0011-mod_md-Add-OpenSSL-4.0-compatibility.patch' should contain a Signed-off-by entry
 5SECTION = "net" 6LICENSE = "Apache-2.0" 7 8SRC_URI = "${APACHE_MIRROR}/httpd/httpd-${PV}.tar.bz2 \ 9           file://0001-configure-use-pkg-config-for-PCRE-detection.patch \10           file://0002-apache2-bump-up-the-core-size-limit-if-CoreDumpDirec.patch \11           file://0003-apache2-do-not-export-apr-apr-util-symbols-when-usin.patch \

[PATCH 82/82] lvgl-demo-fb: fix SRCREV

patchtest: 879 pass, 3 fail, 348 skip

Text report

AutoBuilder

Builds of staging branches that carried this series. Each builds every patch on the branch; a failure is shown as this series' only when it is in a recipe the series changes, or two builds failed so newly carrying it.