Source: libgssapi-perl Version: 0.28-1 Severity: serious Tags: wheezy sid User: [email protected] Usertags: qa-ftbfs-20111210 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/libgssapi-perl-d7QxHw/libgssapi-perl-0.28' > PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" > "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t > t/1constants.t ..... ok > t/2status.t ........ ok > t/checkoids.t ...... ok > t/importnames.t .... ok > # KRB5 old Mechtype, Kerberos 5, SPNEGO > t/indicatemechs.t .. ok > > # Failed test '$cred1->inquire_cred($name, $lifetime, $cred_usage, $oidset' > # at t/inquire_cred.t line 47. > # inquire_cred() lifetime: 0 seconds > # inquire_cred() credusage: 0 (GSS_C_BOTH) > (in cleanup) oidset has no value. > # Looks like you failed 1 test of 6. > t/inquire_cred.t ... > Dubious, test returned 1 (wstat 256, 0x100) > Failed 1/6 subtests > t/pod.t ............ ok > t/test.t ........... ok > # > # > # if you want to run tests that do a realworld *use* of your GSSAPI > # start a kinit and try to run > # > # ./examples/getcred_hostbased.pl > # > t/zbugfixes.t ...... ok > > Test Summary Report > ------------------- > t/inquire_cred.t (Wstat: 256 Tests: 6 Failed: 1) > Failed test: 4 > Non-zero exit status: 1 > Files=9, Tests=152, 0 wallclock secs ( 0.05 usr 0.02 sys + 0.40 cusr 0.06 > csys = 0.53 CPU) > Result: FAIL > Failed 1/9 test programs. 1/152 subtests failed. > make[1]: *** [test_dynamic] Error 255 The full build log is available from: http://people.debian.org/~lucas/logs/2011/12/10/libgssapi-perl_0.28-1_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. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
