Your message dated Thu, 25 Sep 2014 14:28:15 -0400
with message-id <20140925182815.ga23...@calvin1.nccs.nasa.gov>
and subject line Fixed in 0.5.0-1
has caused the Debian Bug report #759970,
regarding libebook-tools-perl: FTBFS: tests failed
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
759970: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759970
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libebook-tools-perl
Version: 0.4.9-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140830 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/«PKGBUILDDIR»'
> /usr/bin/perl Build --makefile_env_macros 1 test
> Module::Build will be removed from the Perl core distribution in the next
> major release. Please install the separate libmodule-build-perl package. It
> is being used at Build, line 40.
> t/00-errorhandling.t ....... ok
>
> not well-formed (invalid token) at line 24, column 25, byte 1230 at
> /usr/lib/x86_64-linux-gnu/perl5/5.20/XML/Parser.pm line 187.
> at /«PKGBUILDDIR»/blib/lib/EBook/Tools.pm line 672.
> # Looks like you planned 79 tests but ran 7.
> # Looks like your test exited with 255 just after 7.
> t/01-init_and_accessors.t ..
> Dubious, test returned 255 (wstat 65280, 0xff00)
> Failed 72/79 subtests
> t/02-fix_methods.t ......... ok
> t/10-fix_datestring.t ...... ok
> t/15-misc_procedures.t ..... ok
> Wide character in print at /usr/share/perl5/XML/Twig.pm line 8331.
>
> not well-formed (invalid token) at line 13, column 27, byte 689 at
> /usr/lib/x86_64-linux-gnu/perl5/5.20/XML/Parser.pm line 187.
> at /«PKGBUILDDIR»/blib/lib/EBook/Tools.pm line 672.
> # Looks like you planned 48 tests but ran 43.
> # Looks like your test exited with 255 just after 43.
> t/20-unpack.t ..............
> Dubious, test returned 255 (wstat 65280, 0xff00)
> Failed 5/48 subtests
> t/21-mobi_languages.t ...... ok
> EBook::Tools::IMP::image(): no image type specified!
> at t/25-imp.t line 54.
> EBook::Tools::IMP::image(): ID not specified!
> at t/25-imp.t line 55.
> t/25-imp.t ................. ok
> t/40-lzss.t ................ ok
> t/50-user_scripts.t ........ skipped: Automated testing often breaks on
> actual scripts.
> t/98-pod.t ................. skipped: Test::Pod 1.00 required for testing POD
> t/99-pod_coverage.t ........ skipped: Test::Pod::Coverage 1.00 required for
> testing POD coverage
>
> Test Summary Report
> -------------------
> t/01-init_and_accessors.t (Wstat: 65280 Tests: 7 Failed: 0)
> Non-zero exit status: 255
> Parse errors: Bad plan. You planned 79 tests but ran 7.
> t/20-unpack.t (Wstat: 65280 Tests: 43 Failed: 0)
> Non-zero exit status: 255
> Parse errors: Bad plan. You planned 48 tests but ran 43.
> Files=12, Tests=378, 4 wallclock secs ( 0.09 usr 0.10 sys + 3.39 cusr
> 0.68 csys = 4.26 CPU)
> Result: FAIL
> Failed 2/12 test programs. 0/378 subtests failed.
> make[1]: *** [test] Error 255
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2014/08/30/libebook-tools-perl_0.4.9-1_unstable.log
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 EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures. The build
was done with DEB_BUILD_OPTIONS="parallel=4", so if your packaging tries
to support this, it might be a good idea to explore whether this might
be the cause of the failure.
--- End Message ---
--- Begin Message ---
This particular problem is fixed as of 0.5.0-1, but that version also
has an incorrect dependency listing, so 0.5.1-1 will be coming today
as well.
--- End Message ---
