Your message dated Sun, 28 Jul 2013 12:26:41 +0200 with message-id <201307281226.41102.david.sephi...@gmail.com> and subject line Re: Bug#718117: Acknowledgement (librdf-ns-perl: FTBFS: Failed 1/6 test programs. 0/66 subtests failed.) has caused the Debian Bug report #718117, regarding librdf-ns-perl: FTBFS: Failed 1/6 test programs. 0/66 subtests 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.) -- 718117: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718117 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: librdf-ns-perl Version: 20130402-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130726 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»' > Skip blib/lib/auto/share/dist/RDF-NS/prefix.cc (unchanged) > PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" > "test_harness(1, 'blib/lib', 'blib/arch')" t/*.t > t/compile.t ..... > ok 1 - use RDF::NS; > 1..1 > ok > t/history.t ..... > ok 1 - 791 prefixes at 20120521 > ok 2 - 716 prefixes at 20111208 > ok 3 - 709 prefixes at 20111124 > ok 4 - 700 prefixes at 20111031 > ok 5 - 701 prefixes at 20111102 > ok 6 - 698 prefixes at 20111028 > ok 7 - 780 prefixes at 20120426 > ok 8 - 733 prefixes at 20120124 > ok 9 - 830 prefixes at 20120827 > ok 10 - old prefix > ok 11 - prefix changed > 1..11 > ok > t/namespaces.t .. > ok 1 - rdf: namespace not changed > ok 2 - rdfs: namespace not changed > ok 3 - $ns->rdf > ok 4 - $ns->rdf_ > ok 5 - $ns->rdf_type > ok 6 - $ns->rdf_type > ok 7 - $ns->rdf("f-o") > ok 8 - $ns->rdf("0") > ok 9 - $ns->URI("rdf:type") > ok 10 - $ns->URI("rdf_type") > ok 11 - $ns->URI("<rdf:type>") > ok 12 - SPARQL("rdf") > ok 13 - TTL("rdfs") > ok 14 - order ok > ok 15 - order ok > ok 16 - SPARQL(...) > ok 17 - TTL(...) > ok 18 - XMLNS(...) > ok 19 - SPARQL(...) > ok 20 - TTL(...) > ok 21 - XMLNS(...) > ok 22 - SPARQL(...) > ok 23 - TTL(...) > ok 24 - XMLNS(...) > ok 25 - SPARQL(...) > ok 26 - TTL(...) > ok 27 - XMLNS(...) > ok 28 - SELECT (list) > ok 29 - SELECT (scalar) > ok 30 - empty prefix allowed > ok 31 - blessed alone, one-letter prefix > ok 32 > ok 33 > ok 34 > ok 35 > ok 36 > 1..36 > ok > t/prefix.t ...... > ok 1 - PREFIX > ok 2 - PREFIXES has dc, dc11 > ok 3 - reverse > ok 4 - reverse > 1..4 > ok > Bad blank node identifier: # Tests were run but no plan was declared and > done_testing() was not seen. > t/trine.t ....... > ok 1 - use RDF::NS::Trine; > ok 2 - The object isa RDF::Trine::Node::Resource > ok 3 - The object isa RDF::Trine::Node::Resource > ok 4 - The object isa RDF::Trine::Node::Resource > ok 5 - SPARQL("rdf") > ok 6 - TTL("rdfs") > ok 7 - XMLNS("rdfs") > ok 8 - The object isa RDF::Trine::Node::Blank > ok 9 - blank node > ok 10 - blank node > Dubious, test returned 255 (wstat 65280, 0xff00) > All 10 subtests passed > t/uris.t ........ > ok 1 > ok 2 > ok 3 > ok 4 > 1..4 > ok > > Test Summary Report > ------------------- > t/trine.t (Wstat: 65280 Tests: 10 Failed: 0) > Non-zero exit status: 255 > Parse errors: No plan found in TAP output > Files=6, Tests=66, 1 wallclock secs ( 0.06 usr 0.02 sys + 0.98 cusr 0.16 > csys = 1.22 CPU) > Result: FAIL > Failed 1/6 test programs. 0/66 subtests failed. > make[1]: *** [test_dynamic] Error 255 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/07/26/librdf-ns-perl_20130402-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.
--- End Message ---
--- Begin Message ---Hi, Closing one of duplicate bugs; #718117, #718116 (mta problems, sorry) David
--- End Message ---
