On Sat, 22 Oct 2022 00:01:32 -0400 Scott Kitterman <deb...@kitterman.com> 
wrote:
> Package: xml2rfc
> Version: 3.13.1-1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source
> 
> Using FTBFS as it's the closest thing we have to an autopkgtest
> regression severity.  xml2rfc autopkgtest fails in Unstable with
> Weasyprint 57.0:
> 
> ======================================================================
> ERROR: setUpClass (__main__.PdfWriterTests)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File "/tmp/autopkgtest-lxc.48kx6p_4/downtmp/build.obL/src/xxx/test.py", 
line 495, in setUpClass
>     cls.elements_pdfxml = xmldoc(None, bytes=elements_pdfdoc)
>   File "/usr/lib/python3/dist-packages/xml2rfc/walkpdf.py", line 96, in 
xmldoc
>     return lxml.etree.fromstring(text)
>   File "src/lxml/etree.pyx", line 3254, in lxml.etree.fromstring
>   File "src/lxml/parser.pxi", line 1913, in lxml.etree._parseMemoryDocument
>   File "src/lxml/parser.pxi", line 1793, in lxml.etree._parseDoc
>   File "src/lxml/parser.pxi", line 1082, in 
lxml.etree._BaseParser._parseUnicodeDoc
>   File "src/lxml/parser.pxi", line 615, in 
lxml.etree._ParserContext._handleParseResultDoc
>   File "src/lxml/parser.pxi", line 725, in lxml.etree._handleParseResult
>   File "src/lxml/parser.pxi", line 654, in lxml.etree._raiseParseError
>   File "<string>", line 14199
> lxml.etree.XMLSyntaxError: PCDATA invalid Char value 23, line 14199, column 
11
> 
> ----------------------------------------------------------------------
> Ran 42 tests in 21.851s
> 
> FAILED (errors=1)
> 
> https://ci.debian.net/data/autopkgtest/testing/amd64/x/xml2rfc/27394437/
log.gz
> 
> Upstream is apparently aware since (I discovered after uploading
> Weasyprint) they have recently pinned the Weasyprint dependency to
> <57.0.
> 
> I did file an issue upstream:
> 
> https://github.com/ietf-tools/xml2rfc/issues/921
> 

I narrowed down the Weasyprint commit that leads to the failure and asked for 
feedback from that upstream:

https://github.com/Kozea/WeasyPrint/issues/1752

If that doesn't prove fruitful, I am open to patching Debian's weasyprint to 
fix the issue.

Scott K

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to