From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: wangmy@fujitsu.com, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 06/22] json-glib: upgrade 1.8.0 -> 1.10.0
Date: Tue, 03 Sep 2024 22:51:11 +0100 [thread overview]
Message-ID: <42ac587c4e691d9c2526e9088de9bc27bb92b0b9.camel@linuxfoundation.org> (raw)
In-Reply-To: <1725352379-20334-6-git-send-email-wangmy@fujitsu.com>
On Tue, 2024-09-03 at 16:32 +0800, wangmy via lists.openembedded.org
wrote:
> From: Wang Mingyu <wangmy@fujitsu.com>
>
> License-Update: Add copyright and licensing metadata to all files
>
> Changelog:
> ==========
> - Improve conformance of the JSON parser
> - Add conformance test suite from
> https://github.com/nst/JSONTestSuite
> - Add JsonParser:strict to enable strict parsing
> - Add '--strict' to json-glib-validate to enable strict parsing
> - Deprecate the signals on JsonParser
> - Port tools man pages from DocBook to reStructureText
> - Add "documentation" configuration option, and deprecate "gtk_doc"
> - Add JsonGenerator.take_root()
> - Documentation improvements for JsonReader
> - Raise parser error for malformed Unicode
> - Build fixes and performance improvements
> - Allow disabling installed tests
> - Support parsing multiple root statements in non-strict mode
> - Allow loading files >4GB with json-glib-validate
>
> Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
https://autobuilder.yoctoproject.org/typhoon/#/builders/108/builds/6344/steps/11/logs/stdio
The recipe probably needs to adapt to the change listed above:
'Add "documentation" configuration option, and deprecate "gtk_doc"'
but I didn't look in detail, I'm just noting it was a docs build that
failed.
Cheers,
Richard
next prev parent reply other threads:[~2024-09-03 21:51 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 8:32 [OE-core] [PATCH 01/22] acpica: upgrade 20240322 -> 20240827 wangmy
2024-09-03 8:32 ` [OE-core] [PATCH 02/22] cairo: upgrade 1.18.0 -> 1.18.2 wangmy
2024-09-03 8:32 ` [OE-core] [PATCH 03/22] dhcpcd: upgrade 10.0.8 -> 10.0.10 wangmy
2024-09-03 8:32 ` [OE-core] [PATCH 04/22] diffoscope: upgrade 276 -> 277 wangmy
2024-09-03 8:32 ` [OE-core] [PATCH 05/22] ell: upgrade 0.67 -> 0.68 wangmy
2024-09-03 8:32 ` [OE-core] [PATCH 06/22] json-glib: upgrade 1.8.0 -> 1.10.0 wangmy
2024-09-03 21:51 ` Richard Purdie [this message]
2024-09-04 1:25 ` Mingyu Wang (Fujitsu)
2024-09-04 7:49 ` Richard Purdie
2024-09-11 0:57 ` Mingyu Wang (Fujitsu)
2024-09-11 10:21 ` Alexander Kanavin
2024-09-04 2:21 ` Yi Zhao
2024-09-03 8:32 ` [OE-core] [PATCH 07/22] libdrm: upgrade 2.4.122 -> 2.4.123 wangmy
2024-09-03 8:32 ` [OE-core] [PATCH 08/22] libsoup: upgrade 3.4.4 -> 3.6.0 wangmy
2024-09-03 8:32 ` [OE-core] [PATCH 09/22] liburcu: upgrade 0.14.0 -> 0.14.1 wangmy
2024-09-03 8:32 ` [OE-core] [PATCH 10/22] lttng-tools: upgrade 2.13.13 -> 2.13.14 wangmy
2024-09-03 8:32 ` [OE-core] [PATCH 11/22] mc: upgrade 4.8.31 -> 4.8.32 wangmy
2024-09-03 8:32 ` [OE-core] [PATCH 12/22] nghttp2: upgrade 1.62.1 -> 1.63.0 wangmy
2024-09-03 8:32 ` [OE-core] [PATCH 13/22] ofono: upgrade 2.9 -> 2.10 wangmy
2024-09-03 8:32 ` [OE-core] [PATCH 14/22] python3-certifi: upgrade 2024.7.4 -> 2024.8.30 wangmy
2024-09-03 8:32 ` [OE-core] [PATCH 15/22] python3-idna: upgrade 3.7 -> 3.8 wangmy
2024-09-03 8:32 ` [OE-core] [PATCH 16/22] python3-maturin: upgrade 1.7.0 -> 1.7.1 wangmy
2024-09-03 8:32 ` [OE-core] [PATCH 17/22] python3-pbr: upgrade 6.0.0 -> 6.1.0 wangmy
2024-09-03 8:32 ` [OE-core] [PATCH 18/22] python3-websockets: upgrade 12.0 -> 13.0.1 wangmy
2024-09-03 8:32 ` [OE-core] [PATCH 19/22] python3-zipp: upgrade 3.20.0 -> 3.20.1 wangmy
2024-09-03 8:32 ` [OE-core] [PATCH 20/22] taglib: upgrade 2.0.1 -> 2.0.2 wangmy
2024-09-03 8:32 ` [OE-core] [PATCH 21/22] wayland-protocols: upgrade 1.36 -> 1.37 wangmy
2024-09-03 8:32 ` [OE-core] [PATCH 22/22] wayland: upgrade 1.23.0 -> 1.23.1 wangmy
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=42ac587c4e691d9c2526e9088de9bc27bb92b0b9.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=wangmy@fujitsu.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