Source: ikiwiki
Version: 3.20200202.4-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[3]: Entering directory '/<<PKGBUILDDIR>>'
> make[3]: Leaving directory '/<<PKGBUILDDIR>>'
> ok 1
> ok 2
> ok 3 - run ikiwiki
> ok 4 - run CGI
> 1..4
> ok
> t/yesno.t ...................... 
> 1..11
> ok 1 - use IkiWiki;
> ok 2
> ok 3
> ok 4
> ok 5
> ok 6
> ok 7
> ok 8
> ok 9
> ok 10
> ok 11
> ok
> 
> Test Summary Report
> -------------------
> t/po.t                       (Wstat: 256 (exited 1) Tests: 114 Failed: 0)
>   Non-zero exit status: 1
>   Parse errors: No plan found in TAP output
> t/relativity.t               (Wstat: 0 Tests: 177 Failed: 0)
>   TODO passed:   36-37, 92
> Files=71, Tests=3534, 44 wallclock secs ( 0.58 usr  0.14 sys + 34.39 cusr  
> 7.79 csys = 42.90 CPU)
> Result: FAIL
> Failed 1/71 test programs. 0/3534 subtests failed.
> make[2]: *** [Makefile:973: test_dynamic] Error 255
> make[2]: Leaving directory '/<<PKGBUILDDIR>>'
> dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2


The full build log is available from:
http://qa-logs.debian.net/2024/07/02/ikiwiki_3.20200202.4-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240702;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240702&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

Reply via email to