Source: libwiki-toolkit-plugin-diff-perl Version: 0.12-3 Severity: serious User: [email protected] Usertags: qa-ftbfs-20091210 qa-ftbfs Justification: FTBFS on amd64
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory > `/build/user-libwiki-toolkit-plugin-diff-perl_0.12-3-amd64-6VyEol/libwiki-toolkit-plugin-diff-perl-0.12' > PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" > "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t > Unhandled error: [DBD::SQLite::db do failed: SQL logic error or missing > database > cannot start a transaction within a transaction at > /usr/share/perl5/Wiki/Toolkit/Store/SQLite.pm line 73. > ] at /usr/share/perl5/Wiki/Toolkit.pm line 847 > # Looks like you planned 19 tests but ran 1. > # Looks like your test exited with 255 just after 1. > t/02_diff.t ....... > Dubious, test returned 255 (wstat 65280, 0xff00) > Failed 18/19 subtests > t/pod.t ........... skipped: Test::Pod 1.00 required for testing POD > Failed 1/3 test programs. 0/2 subtests failed. > t/pod_coverage.t .. ok > > Test Summary Report > ------------------- > t/02_diff.t (Wstat: 65280 Tests: 1 Failed: 0) > Non-zero exit status: 255 > Parse errors: Bad plan. You planned 19 tests but ran 1. > Files=3, Tests=2, 0 wallclock secs ( 0.03 usr 0.00 sys + 0.18 cusr 0.02 > csys = 0.23 CPU) > Result: FAIL > make[1]: *** [test_dynamic] Error 255 The full build log is available from: http://people.debian.org/~lucas/logs/2009/12/10/libwiki-toolkit-plugin-diff-perl_0.12-3_lsid64.buildlog 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! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- | Lucas Nussbaum | [email protected] http://www.lucas-nussbaum.net/ | | jabber: [email protected] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
