Bug#886416: libnih: uninstallable, and FTBFS when rebuilt: FAIL test_parse (unexpected line numbering)

2018-01-06 Thread Niko Tyni
On Sat, Jan 06, 2018 at 02:03:21PM +0100, Axel Beckert wrote: > Yes, indeed, that looks much more sane now. Might be related to this > bug fix in expat 2.2.5: > >#137 #138 Fix a case of mistakenly reported parsing success where > XML_StopParser was called from an

Bug#886416: libnih: uninstallable, and FTBFS when rebuilt: FAIL test_parse (unexpected line numbering)

2018-01-06 Thread Axel Beckert
Control: tag -1 + pending Hi Simon, Simon McVittie wrote: > > > - TEST_FILE_EQ (output, ("test:foo:2:0: " > > > + TEST_FILE_EQ (output, ("test:foo:1:36: " > > >"Invalid object path in > > > name attribute\n")); […] > It

Processed: Re: Bug#886416: libnih: uninstallable, and FTBFS when rebuilt: FAIL test_parse (unexpected line numbering)

2018-01-06 Thread Debian Bug Tracking System
Processing control commands: > tag -1 + pending Bug #886416 [src:libnih] libnih: FTBFS with expat 2.2.5: "FAIL test_parse (unexpected line numbering)" and is now uninstallable due now failing BinNMU Added tag(s) pending. -- 886416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886416

Bug#886416: libnih: uninstallable, and FTBFS when rebuilt: FAIL test_parse (unexpected line numbering)

2018-01-06 Thread Simon McVittie
On Sat, 06 Jan 2018 at 03:01:35 +0100, Axel Beckert wrote: > Axel Beckert wrote: > > I don't know if that test suite failure shows that expat broke libnih > > or if the test suite just needs to be adapted to the new expat > > version. > > > > - TEST_FILE_EQ (output, ("test:foo:2:0:

Bug#886416: libnih: uninstallable, and FTBFS when rebuilt: FAIL test_parse (unexpected line numbering)

2018-01-05 Thread Axel Beckert
Control: tag -1 + patch Hi again, Axel Beckert wrote: > I don't know if that test suite failure shows that expat broke libnih > or if the test suite just needs to be adapted to the new expat > version. > > Iff the later is the case, the following patch fixes the FTBFS: > > ---

Processed: Re: Bug#886416: libnih: uninstallable, and FTBFS when rebuilt: FAIL test_parse (unexpected line numbering)

2018-01-05 Thread Debian Bug Tracking System
Processing control commands: > tag -1 + patch Bug #886416 [src:libnih] libnih: FTBFS with expat 2.2.5: "FAIL test_parse (unexpected line numbering)" and is now uninstallable due now failing BinNMU Added tag(s) patch. -- 886416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886416 Debian

Bug#886416: libnih: uninstallable, and FTBFS when rebuilt: FAIL test_parse (unexpected line numbering)

2018-01-05 Thread Axel Beckert
Hi again, Axel Beckert wrote: > BAD: wrong content in file 0x5653145373a0 (output), expected 'test:foo:2:0: > Invalid object path in name attribute > ' got 'test:foo:1:36: Invalid object path in name attribute > ' > at tests/test_parse.c:7954 (test_parse_xml). > FAIL test_parse (exit

Bug#886416: libnih: uninstallable, and FTBFS when rebuilt: FAIL test_parse (unexpected line numbering)

2018-01-05 Thread Axel Beckert
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

Processed: Re: Bug#886416: libnih: uninstallable, and FTBFS when rebuilt: FAIL test_parse (unexpected line numbering)

2018-01-05 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 libnih: FTBFS with expat 2.2.5: "FAIL test_parse (unexpected line > numbering)" and is now uninstallable due now failing BinNMU Bug #886416 [src:libnih] libnih: uninstallable, and FTBFS when rebuilt: FAIL test_parse (unexpected line nu

Bug#886416: libnih: uninstallable, and FTBFS when rebuilt: FAIL test_parse (unexpected line numbering)

2018-01-05 Thread Simon McVittie
Source: libnih Version: 1.0.3-9 Severity: serious Justification: fails to build from source (but built successfully in the past) Affects: systemd-shim libnih was made uninstallable by the glibc 2.26 transition, because it uses internal glibc symbols. Normally this would be handled by a simple