From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Moritz.Haase@bmw.de, openembedded-core@lists.openembedded.org
Cc: alex.kanavin@gmail.com, mathieu.dubois-briand@bootlin.com,
Ross Burton <ross.burton@arm.com>
Subject: Re: [OE-core] [PATCH v3] json-c: upgrade 0.18 -> 0.19
Date: Mon, 06 Jul 2026 09:56:44 +0100 [thread overview]
Message-ID: <ebb0c3d6facbb9d88be4451aa981363d65c19d67.camel@linuxfoundation.org> (raw)
In-Reply-To: <20260703105349.1664278-1-Moritz.Haase@bmw.de>
On Fri, 2026-07-03 at 12:53 +0200, Moritz Haase via lists.openembedded.org wrote:
> Release notes are available at [0].
>
> Newly added tests (see [1]) require the 'json_parse' app at (test) runtime.
> Thus, apps are now being built and the 'json_parse' app is deployed in the
> 'ptest' package. We do not package the apps separately as upstream doesn't
> consider them to be ready for that (see [2]). This approach is based on the
> discussion in [3].
>
> [0]: https://github.com/json-c/json-c/blob/json-c-0.19/ChangeLog
> [1]: https://github.com/json-c/json-c/blob/d9d8cab82291637671f6c90cf06e578750a08718/tests/test_json_parse_cli.test#L18
> [2]: https://github.com/json-c/json-c/blob/d9d8cab82291637671f6c90cf06e578750a08718/apps/CMakeLists.txt#L122-L124
> [3]: https://lists.openembedded.org/g/openembedded-core/topic/120026557#
>
> Signed-off-by: Moritz Haase <Moritz.Haase@bmw.de>
> CC: alex.kanavin@gmail.com
> CC: mathieu.dubois-briand@bootlin.com
> ---
> changes in v3:
> - Deploy required app differently to hopefully fix failures seen
> on Autobuilder (see [4]).
>
> changes in v2:
> - Build and deploy apps required to fix ptest failure, as discussed in [3].
>
> [4]: https://lists.openembedded.org/g/openembedded-core/topic/120061116#msg240021
>
> ---
> .../json-c/{json-c_0.18.bb => json-c_0.19.bb} | 16 ++++++++++------
> 1 file changed, 10 insertions(+), 6 deletions(-)
> rename meta/recipes-devtools/json-c/{json-c_0.18.bb => json-c_0.19.bb} (72%)
>
> diff --git a/meta/recipes-devtools/json-c/json-c_0.18.bb b/meta/recipes-devtools/json-c/json-c_0.19.bb
> similarity index 72%
> rename from meta/recipes-devtools/json-c/json-c_0.18.bb
> rename to meta/recipes-devtools/json-c/json-c_0.19.bb
> index c112aacf4bceb0c41dbe2e1643d2d7e0944bf250..6f357b45b97c602cb19523089fb63ada2a1384f5 100644
> --- a/meta/recipes-devtools/json-c/json-c_0.18.bb
> +++ b/meta/recipes-devtools/json-c/json-c_0.19.bb
> @@ -9,23 +9,23 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=de54b60fbbc35123ba193fea8ee216f2"
> SRC_URI = "https://s3.amazonaws.com/json-c_releases/releases/${BP}.tar.gz \
> file://run-ptest \
> "
> -SRC_URI[sha256sum] = "876ab046479166b869afc6896d288183bbc0e5843f141200c677b3e8dfb11724"
> +SRC_URI[sha256sum] = "37ad0249902e301bd9052bf712e511fcc6acff4ecaad4b5900aad9ce564e26de"
>
> # NVD uses full tag name including date
> -CVE_VERSION = "0.18-20240915"
> +CVE_VERSION = "0.19-20260627"
>
> UPSTREAM_CHECK_URI = "https://github.com/${BPN}/${BPN}/tags"
> UPSTREAM_CHECK_REGEX = "json-c-(?P<pver>\d+(\.\d+)+)-\d+"
>
> RPROVIDES:${PN} = "libjson"
>
> -# Apps aren't needed/packaged and their CMakeLists.txt is incompatible with CMake 4+.
> -EXTRA_OECMAKE = "-DDISABLE_WERROR=ON \
> - -DBUILD_APPS=OFF \
> -"
> +EXTRA_OECMAKE = "-DDISABLE_WERROR=ON"
>
> inherit cmake ptest
>
> +# xxd is required by the 'json_parse_cli' test.
> +RDEPENDS:${PN}-ptest += "xxd"
> +
This patch turns out to be the one breaking oe-selftest:
e.g.
https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/4276
https://autobuilder.yoctoproject.org/valkyrie/#/builders/35/builds/4216
The reason is that prior to this change, those tests don't build glib-
2.0 but after them, they do due to the new xxd -> vim -> desktop-file-
utils -> glib-2.0 dependency chain.
Not quite sure what we'll do about that yet, we may need to add more
locales to the selftest I guess but the extra dependencies aren't
ideal.
Cheers,
Richard
next prev parent reply other threads:[~2026-07-06 8:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 10:53 [PATCH v3] json-c: upgrade 0.18 -> 0.19 Moritz Haase
2026-07-06 8:56 ` Richard Purdie [this message]
2026-07-06 9:27 ` [OE-core] " Alexander Kanavin
2026-07-06 9:58 ` Ross Burton
2026-07-06 10:22 ` Ross Burton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ebb0c3d6facbb9d88be4451aa981363d65c19d67.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Moritz.Haase@bmw.de \
--cc=alex.kanavin@gmail.com \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox