A quick heads-up, the problem is known upstream (see URL field). Sorry for the inconvenience. [..] t/astress.t ........... ok t/defaulted.t ......... ok t/cdata.t ............. ok t/encoding.t .......... ok t/finish.t ............ ok t/namespaces.t ........ ok t/file.t .............. ok t/file_open_scalar.t .. ok t/decl.t .............. ok t/partial.t ........... Failed 1/3 subtests t/skip.t .............. ok t/stream.t ............ ok t/styles.t ............ ok t/external_ent.t ...... ok t/parament.t .......... ok [..]
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=50c94be3d92653538e66ea59ad91c6f89a3b9870 commit 50c94be3d92653538e66ea59ad91c6f89a3b9870 Author: Sebastian Pipping <sping@gentoo.org> AuthorDate: 2025-03-27 20:09:44 +0000 Commit: Sebastian Pipping <sping@gentoo.org> CommitDate: 2025-03-27 20:09:44 +0000 dev-libs/expat: 2.7.1 Bug: https://bugs.gentoo.org/951439 Signed-off-by: Sebastian Pipping <sping@gentoo.org> dev-libs/expat/Manifest | 1 + dev-libs/expat/expat-2.7.1.ebuild | 100 ++++++++++++++++++++++++++++++++++++++ 2 files changed, 101 insertions(+)
With the new dev-libs/expat-2.7.1 all tests pass. Should there be a blocker to =dev-libs/expat-2.7.0 in the dev-perl/XML-Parser ebuild? If yes: Before or after the stabilization of dev-libs/expat-2.7.1 (bug #952810)?
