From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Cc: Adolf Belka <adolf.belka@ipfire.org>
Subject: [PATCH] libxml2: Update to version 2.14.2
Date: Tue, 13 May 2025 18:03:40 +0200 [thread overview]
Message-ID: <20250513160343.2096670-8-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20250513160343.2096670-1-adolf.belka@ipfire.org>
- Update from version 2.14.0 to 2.14.2
- Update of rootfile
- Two CVE fixes in 2.14.2
- Changelog
2.14.2
### Security
- [CVE-2025-32415] schemas: Fix heap buffer overflow in
xmlSchemaIDCFillNodeTables
- [CVE-2025-32414] python: Read at most len/4 characters. (Maks Verver)
### Build
- error: Fix initGenericErrorDefaultFunc compatibility macro
- meson: don't link with pthreads on Windows (Benjamin Gilbert)
- cmake, meson: Align Darwin version info with Autotools
- globals: Fix --with-thread-alloc build
- meson: ensure relaxng option supports minimum option (Lovell Fuller)
2.14.1
### Regressions
- parser: Fix XML_PARSE_NOBLANKS dropping non-whitespace text
### Build systems
- win32-legacy: Fix build (ThomasK)
- meson: Fix build from tarball
- cmake, meson: Change library filename to libxml2.so.16.0.0
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
---
config/rootfiles/common/libxml2 | 2 +-
lfs/libxml2 | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/config/rootfiles/common/libxml2 b/config/rootfiles/common/libxml2
index 589b5b752..a3e256c25 100644
--- a/config/rootfiles/common/libxml2
+++ b/config/rootfiles/common/libxml2
@@ -54,7 +54,7 @@
#usr/lib/libxml2.la
#usr/lib/libxml2.so
usr/lib/libxml2.so.16
-usr/lib/libxml2.so.16.0.0
+usr/lib/libxml2.so.16.0.2
#usr/lib/pkgconfig/libxml-2.0.pc
#usr/share/doc/libxml2
#usr/share/doc/libxml2/xmlcatalog.html
diff --git a/lfs/libxml2 b/lfs/libxml2
index c1014f56f..03749d031 100644
--- a/lfs/libxml2
+++ b/lfs/libxml2
@@ -24,7 +24,7 @@
include Config
-VER = 2.14.0
+VER = 2.14.2
THISAPP = libxml2-$(VER)
DL_FILE = $(THISAPP).tar.xz
@@ -42,7 +42,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_BLAKE2 = 4e210661b10b846cf80c2ba393209fd2bde1e7f8e4a024eff2e6a90369969e7a7696e2cb77197fe63f63fae959bcaed052d5c5107603f0c64a16d6ceeab6b43c
+$(DL_FILE)_BLAKE2 = 2331234ed60358168298d04c83162bfe7d08e6fc77091fe1ecf8384e68902ab745f039dc807d12dda3124313724806bd7fb651de975dbc60fdaf963bac043ff8
install : $(TARGET)
--
2.49.0
next prev parent reply other threads:[~2025-05-13 16:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 16:03 [PATCH] core196: Ship intel-microcode Adolf Belka
2025-05-13 16:03 ` [PATCH] core196: Ship libpng Adolf Belka
2025-05-13 16:03 ` [PATCH] core196: Ship libxml2 Adolf Belka
2025-05-13 16:03 ` [PATCH] core196: Ship lvm2 Adolf Belka
2025-05-13 16:03 ` [PATCH] core196: Ship pixman Adolf Belka
2025-05-13 16:03 ` [PATCH] intel-microcode: Update to version 20250512 Adolf Belka
2025-05-13 16:03 ` [PATCH] libpng: Update to version 1.6.48 Adolf Belka
2025-05-13 16:03 ` Adolf Belka [this message]
2025-05-13 16:03 ` [PATCH] lvm2: Update to version 2.03.32 Adolf Belka
2025-05-13 16:03 ` [PATCH] pixman: Update to version 0.46.0 Adolf Belka
2025-05-13 16:03 ` [PATCH] sdl2: Update to version 2.32.6 Adolf Belka
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=20250513160343.2096670-8-adolf.belka@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.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