On Mon, 17 Jun 2024 16:38:58 +0200 (CEST) Thorsten Glaser <t.gla...@qvest-digital.com> wrote:
On Mon, 17 Jun 2024, Aron Xu wrote:

>Control: tags -1 - pending

Oops, right.

>It looks that this libxml2 update is causing more troubles than
>expected, I would like to ask for your opinion whether it's better to
>revert to an older version for the moment?

Might be useful while you ask upstream what they’re doing there
with regards to both API and ABI, and/or someone diffs the API
and ABI surface of the old and new version and figures out whether
there are any other such surprises. Security fixes might need
backporting though.

Maybe they haven’t realised themselves and decide they need to
bump to libxml3 upstream at some point.

There's also a new upstream release (2.13), which probably also breaks the API/ABI from 2.12 again. So it might be worth jumping right to 2.13 if you need to take a trip through NEW.

tree.h:
-XMLPUBFUN void
+XMLPUBFUN int
                xmlSetTreeDoc           (xmlNodePtr tree,
                                         xmlDocPtr doc);
-XMLPUBFUN void
+XMLPUBFUN int
                xmlSetListDoc           (xmlNodePtr list,
                                         xmlDocPtr doc);


parser.h:
@@ -327,6 +313,9 @@
     xmlParserNsData       *nsdb;    /* namespace database */
     unsigned        attrHashMax;    /* allocated size */
     xmlAttrHashBucket *attrHash;    /* atttribute hash table */
+
+    xmlStructuredErrorFunc errorHandler;
+    void *errorCtxt;
 };


The libxml package is currently keeping chromium from migrating to trixie, so I'm looking forward to this getting sorted out (whether upstream or with an SONAME bump or what).

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to