From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Hongxu Jia" <hongxu.jia@windriver.com>,
<Peter.Marko@siemens.com>, <alex.kanavin@gmail.com>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/5] libxml2: upgrade 2.13.8 -> 2.14.3
Date: Thu, 22 May 2025 08:30:38 +0200 [thread overview]
Message-ID: <DA2H7Z2IQH15.8AQHUB50F8SB@bootlin.com> (raw)
In-Reply-To: <20250521080925.815334-1-hongxu.jia@windriver.com>
On Wed May 21, 2025 at 10:09 AM CEST, Hongxu Jia wrote:
> - Rebase install-tests.patch
> - Remove --enable-ipv6, due to upstream [build: Remove check for IPv6 ][2]
>
> License-Update: Mention contributors in Copyright [1]
>
> [1] https://gitlab.gnome.org/GNOME/libxml2/-/commit/4bd66d4549b2e8925a752e0daac3a189d2fec8f7
> [2] https://gitlab.gnome.org/GNOME/libxml2/-/commit/dc6f55cf6e03ae63a40e3af9ad6879821558d6a7
>
> Release notes: https://gitlab.gnome.org/GNOME/libxml2/-/releases/v2.14.3
> Regressions
>
> reader: Fix reading compressed data
> parser: Make undeclared entities in XML content fatal
> save: Fix XML escape table
> save: Fix xmlSave with NULL encoding
> Revert "valid: Remove duplicate error messages when streaming"
>
> Bug fixes
>
> save: Fix serialization of attribute defaults containing <
> io: Fix linkage of __xml*BufferCreateFilename functions
>
> Build systems
>
> cmake: Fix installation directories in libxml2-config.cmake
> meson: Install libxml2.py
>
> Improvements
>
> parser: Make xmlCtxtGetValidCtxt depend on VALID_ENABLED
> html: Avoid HTML_PARSE_HTML5 clashing with XML_PARSE_NOENT
>
> Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
> ---
Hi,
Thanks for the lttng fix.
Build is now correct with this version of libxml2, but we do have some
ptest failures:
Failed ptests:
{'libxml2': ['testThreads']}
https://autobuilder.yoctoproject.org/valkyrie/#/builders/61/builds/1541
https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/1540
Corresponding ptest logs can be found here:
https://valkyrie.yocto.io/pub/non-release/20250521-95/testresults/qemuarm64-ptest/core-image-ptest-libxml2/
https://valkyrie.yocto.io/pub/non-release/20250521-95/testresults/qemux86-64-ptest/core-image-ptest-libxml2/
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-05-22 6:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 8:09 [PATCH 1/5] libxml2: upgrade 2.13.8 -> 2.14.3 Hongxu Jia
2025-05-21 8:09 ` [PATCH v2 2/5] patch: upgrade 2.7.6 -> 2.8 Hongxu Jia
2025-05-21 8:09 ` [PATCH v2 3/5] man-pages: upgrade 6.13 -> 6.14 Hongxu Jia
2025-05-21 8:09 ` [PATCH v2 4/5] libgcrypt: upgrade 1.11.0 -> 1.11.1 Hongxu Jia
2025-05-21 8:09 ` [PATCH 5/5] lttng-tools: fix compile failed with libxml2 2.14.0+ Hongxu Jia
2025-05-22 6:30 ` Mathieu Dubois-Briand [this message]
2025-05-22 6:35 ` [PATCH 1/5] libxml2: upgrade 2.13.8 -> 2.14.3 Marko, Peter
2025-05-22 8:58 ` Mathieu Dubois-Briand
2025-05-22 12:14 ` Marko, Peter
2025-05-22 12:25 ` Mathieu Dubois-Briand
2025-05-26 1:55 ` [OE-core] " Khem Raj
2025-05-26 17:48 ` Marko, Peter
2025-05-26 18:57 ` Khem Raj
2025-05-26 19:36 ` Marko, Peter
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=DA2H7Z2IQH15.8AQHUB50F8SB@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=Peter.Marko@siemens.com \
--cc=alex.kanavin@gmail.com \
--cc=hongxu.jia@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
/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