Hi Miro, Very interesting. This is the latest upstream version of expat and nothing was suggesting that there could be such issues. I will start to look for the cause of this immediately.
Thanks for bringing this to my attention.
On Tue, Feb 22, 2022 at 12:25 PM Miro Hrončok mhroncok@redhat.com wrote:
On 22. 02. 22 12:20, Miro Hrončok wrote:
Hello Dave and Tomas,
I see in Koschei that since libxml2 has been upgraded from 2.9.12-7.fc36 to 2.9.13-1.fc37 [1] and expat has been upgraded from 2.4.4-1.fc36 to 2.4.6-1.fc37 [2], Python fails to build (as well as many other packages).
The Python test failures are:
====================================================================== ERROR: testEncodings (test.test_minidom.MinidomTest)
Traceback (most recent call last): File "/builddir/build/BUILD/Python-3.8.12/Lib/test/test_minidom.py", line 1150, in testEncodings self.assertRaises(UnicodeDecodeError, parseString, File "/builddir/build/BUILD/Python-3.8.12/Lib/unittest/case.py", line 816, in assertRaises return context.handle('assertRaises', args, kwargs) File "/builddir/build/BUILD/Python-3.8.12/Lib/unittest/case.py", line 202, in handle callable_obj(*args, **kwargs) File "/builddir/build/BUILD/Python-3.8.12/Lib/xml/dom/minidom.py", line 1969, in parseString return expatbuilder.parseString(string) File "/builddir/build/BUILD/Python-3.8.12/Lib/xml/dom/expatbuilder.py", line 925, in parseString return builder.parseString(string) File "/builddir/build/BUILD/Python-3.8.12/Lib/xml/dom/expatbuilder.py", line 223, in parseString parser.Parse(string, True) xml.parsers.expat.ExpatError: not well-formed (invalid token): line 1, column 5
====================================================================== ERROR: testExceptionOnSpacesInXMLNSValue (test.test_minidom.MinidomTest)
Traceback (most recent call last): File "/builddir/build/BUILD/Python-3.8.12/Lib/test/test_minidom.py", line 1597, in testExceptionOnSpacesInXMLNSValue parseString('<element xmlns:abc="http:abc.com/de f g/hi/j k">abc:foo /</element>') File "/builddir/build/BUILD/Python-3.8.12/Lib/xml/dom/minidom.py", line 1969, in parseString return expatbuilder.parseString(string) File "/builddir/build/BUILD/Python-3.8.12/Lib/xml/dom/expatbuilder.py", line 925, in parseString return builder.parseString(string) File "/builddir/build/BUILD/Python-3.8.12/Lib/xml/dom/expatbuilder.py", line 223, in parseString parser.Parse(string, True) xml.parsers.expat.ExpatError: syntax error: line 1, column 0
====================================================================== ERROR: test_issue3151 (test.test_xml_etree.BugsTest)
Traceback (most recent call last): File "/builddir/build/BUILD/Python-3.8.12/Lib/test/test_xml_etree.py", line 1972, in test_issue3151 e = ET.XML('<prefix:localname xmlns:prefix="${stuff}"/>') File "/builddir/build/BUILD/Python-3.8.12/Lib/xml/etree/ElementTree.py", line 1320, in XML parser.feed(text) xml.etree.ElementTree.ParseError: syntax error: line 1, column 0
Is it possible that libxml2 or expat (or both) have a regression that causes a previously valid XML document to fail to parse?
[1] https://koschei.fedoraproject.org/affected-by/libxml2-devel?epoch1=0&ver...
[2] https://koschei.fedoraproject.org/affected-by/expat-devel?epoch1=0&versi...
This also happens on Fedora 36:
https://koschei.fedoraproject.org/affected-by/libxml2?epoch1=0&version1=... https://koschei.fedoraproject.org/affected-by/expat-devel?epoch1=0&versi...
-- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok