Bug#886416: libnih: uninstallable, and FTBFS when rebuilt: FAIL test_parse (unexpected line numbering)
Control: retitle -1 libnih: FTBFS with expat 2.2.5: "FAIL test_parse (unexpected line numbering)" and is now uninstallable due now failing BinNMU
Hi,
Simon McVittie wrote:
> > Testing parse_xml()
> > ...
> > BAD: wrong content in file 0x13be5e730 (output), expected 'test:foo:2:0: Invalid object path in <node> name attribute
> > ' got 'test:foo:1:36: Invalid object path in <node> name attribute
> > '
> > at tests/test_parse.c:7954 (test_parse_xml).
> > FAIL test_parse (exit status: 134)
>
> I don't know whether the test failure is triggered by glibc 2.26, or by
> something else that changed since November.
It doesn't seem to be caused glibc 2.26, because if I try to compile
libnih on Sid without having glibc updated from 2.25 to 2.26 yet (due
to libnih), it still FTBFS in the same way:
BAD: wrong content in file 0x5653145373a0 (output), expected 'test:foo:2:0: Invalid object path in <node> name attribute
' got 'test:foo:1:36: Invalid object path in <node> name attribute
'
at tests/test_parse.c:7954 (test_parse_xml).
FAIL test_parse (exit status: 134)
The reproducible build saw its first FTBFS on 2017-12-23 (sid) and
2017-12-30 (buster), and the last successful build on 2017-12-14 (sid)
2017-12-25 (buster):
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libnih.html
Looking at libnih's build dependencies, the expat upstream version
bump on 2017-12-16 in Sid and on 2017-12-25 in buster fits quite well.
Another hint towards expat is the fact that the failing test involves
XML parsing.
Regards, Axel
--
,''`. | Axel Beckert <abe@debian.org>, https://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Reply to: