On Thu, 16 Dec 2021 23:28:26 -0500 Scott Kitterman <deb...@kitterman.com> wrote: > Package: xml2rfc > Version: 3.12.0-1 > Severity: serious > Tags: ftbfs upstream patch > Justification: fails to build from source > > Note: Using ftbfs because that's the closest thing we have to an > autopkgtest failure. > > The new version of weasyprint no longer uses the same PDF generation > libraries and as a result, xml2rfc's detection mechanism for if it is > capable of making a PDF is not working (see attached patch). > > Once the detection mechanism is patched, PDF generation works fine, > which leads me to believe the test failure is bogus: > > ====================================================================== > FAIL: test_text_content (__main__.PdfWriterTests) > ---------------------------------------------------------------------- > Traceback (most recent call last): > File "/home/xml2rfc-3.12.0/test.py", line 510, in test_text_content > self.assertIn(t, text) > AssertionError: 'RFC' not found in 'l- WN –&,ÛžÆ TNDQ&·sX l-%Zñ¢<³ WN P½RÔ > n®>Ø %˜oh l† .µ ¬( .µ=N' > > ---------------------------------------------------------------------- > > If things were really that garbled, I don't see how it could make a PDF. > > Reported upstream: > > https://trac.ietf.org/trac/xml2rfc/ticket/696 > > In the interim, I think it might make sense to apply the attached patch > and get rid of the failing test. If we go down this path, then this > will also need fixing (get rid of HAVE_CAIRO and HAVE_PANGO): > > xml2rfc-3.12.0/test.py", line 513, in test_included_fonts > > if xml2rfc.HAVE_WEASYPRINT and xml2rfc.HAVE_PYCAIRO and > xml2rfc.HAVE_CAIRO and xml2rfc.HAVE_PANGO:
dkg, Unless you want to object, I think we should go ahead and make this change. I don't get the impression that since the IETF LLC booted Henrik there's much upstream going on, so I don't see much point in waiting for them. Scott K
signature.asc
Description: This is a digitally signed message part.
