From: Ralph Siemsen <ralph.siemsen@linaro.org>
To: openembedded-core@lists.openembedded.org
Cc: tony.tascioglu@windriver.com, Ralph Siemsen <ralph.siemsen@linaro.org>
Subject: [RFC PATCH 0/2] libxml2 update
Date: Fri, 11 Mar 2022 11:58:53 -0500 [thread overview]
Message-ID: <20220311165855.3477645-1-ralph.siemsen@linaro.org> (raw)
The first patch has no actual impact on generated code, so it hopefully
can go into the upcoming release. It allows "devtool upgrade" to
recognize that there is a newer version available.
The second patch is the version bump, including a CVE fix. I do not have
extensive test suite, so all I can say is that it compiles and seems to
work in some light testing. Perhaps others could help test it.
--
2.25.1
Ralph Siemsen (2):
libxml2: move to gitlab.gnome.org
libxml2: update to 2.9.13
.../0002-Work-around-lxml-API-abuse.patch | 213 ----------------
.../libxml2/libxml-m4-use-pkgconfig.patch | 229 ------------------
.../{libxml2_2.9.12.bb => libxml2_2.9.13.bb} | 11 +-
3 files changed, 5 insertions(+), 448 deletions(-)
delete mode 100644 meta/recipes-core/libxml/libxml2/0002-Work-around-lxml-API-abuse.patch
delete mode 100644 meta/recipes-core/libxml/libxml2/libxml-m4-use-pkgconfig.patch
rename meta/recipes-core/libxml/{libxml2_2.9.12.bb => libxml2_2.9.13.bb} (91%)
--
2.25.1
next reply other threads:[~2022-03-11 16:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 16:58 Ralph Siemsen [this message]
2022-03-11 16:58 ` [RFC PATCH 1/2] libxml2: move to gitlab.gnome.org Ralph Siemsen
2022-03-11 16:58 ` [RFC PATCH 2/2] libxml2: update to 2.9.13 Ralph Siemsen
2022-03-12 9:19 ` [OE-core] " Richard Purdie
[not found] ` <16DB979A6291AEB5.27059@lists.openembedded.org>
2022-03-12 14:04 ` Richard Purdie
2022-03-12 23:51 ` Ralph Siemsen
2022-03-13 12:25 ` Richard Purdie
2022-03-11 17:02 ` [OE-core] [RFC PATCH 0/2] libxml2 update Alexander Kanavin
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=20220311165855.3477645-1-ralph.siemsen@linaro.org \
--to=ralph.siemsen@linaro.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=tony.tascioglu@windriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.