[Python-modules-team] Bug#910974: utidylib: FTBFS with new tidy-html5 5.7.16: Build-dep list needs updating, test fails (upstream behaviour change)

[Boyuan Yang]

Source: utidylib
Severity: serious
Version: 0.3-1
X-Debbugs-CC: nijel at debian.org

Dear utidylib maintainers,

Currrent utidylib 0.3-1 is not compatible with new tidy-html5.
New tidy-html5 renamed libtidy5 to libtidy5.6, thus it is necessary to
add libtidy5.6 into build-dependency and dependency alternatives.

After fixing that, there is also another problem that lies in a test:

running build_ext
test_bad_options (tidy.test_tidy.TidyTestCase) ... ok
test_big (tidy.test_tidy.TidyTestCase) ... ok
test_encodings (tidy.test_tidy.TidyTestCase) ... ok
test_error_lines (tidy.test_tidy.TidyTestCase) ... ok
test_errors (tidy.test_tidy.TidyTestCase) ... ok
test_missing_load (tidy.test_tidy.TidyTestCase) ... ok
test_nonexisting (tidy.test_tidy.TidyTestCase) ... FAIL
test_options (tidy.test_tidy.TidyTestCase) ... ok
test_parse (tidy.test_tidy.TidyTestCase) ... ok
test_write (tidy.test_tidy.TidyTestCase) ... ok

======================================================================
FAIL: test_nonexisting (tidy.test_tidy.TidyTestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/<<PKGBUILDDIR>>/tidy/test_tidy.py", line 52, in test_nonexisting
    self.assertEquals(str(doc), '')
AssertionError: '\n' != u''

Besides that assertion error, the following several lines would also
have assertion errors. I figured out that it was due to a behaviour
change introduced in tidy-html5 5.5.19 (ce105dcf) that upstream now
emits FILE_NOT_FILE message instead of FILE_CANT_OPEN when the input
file does not exist.

Please consider fixing the test suite to fit the behaviour of new
tidy-html5 or disable this test.

Thanks!

--
Regards,
Boyuan Yang