Package: src:libdevice-cdio-perl Version: 0.3.0-5 Severity: important Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -B" but it failed: -------------------------------------------------------------------------------- [...] Test Summary Report ------------------- t/05.ops.t (Wstat: 11 Tests: 0 Failed: 0) Non-zero wait status: 11 Parse errors: Bad plan. You planned 6 tests but ran 0. t/11.dev.t (Wstat: 11 Tests: 1 Failed: 0) Non-zero wait status: 11 Parse errors: No plan found in TAP output Files=15, Tests=93, 2 wallclock secs ( 0.09 usr 0.05 sys + 1.27 cusr 0.24 csys = 1.65 CPU) Result: FAIL Failed 2/15 test programs. 0/93 subtests failed. dh_auto_test: perl Build test --verbose 1 returned exit code 255 debian/rules:27: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 255 make[1]: Leaving directory '/<<PKGBUILDDIR>>' debian/rules:4: recipe for target 'build-arch' failed make: *** [build-arch] Error 2 dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 -------------------------------------------------------------------------------- [ This is just how the build ends ] Apparently the build fails when (and only when) the machine has a CDROM (not that I'm sure about that, but it's the only explanation I found). I attach two build logs, one which fails and another one which does not. This should be easy to reproduce in a linode (where I found this), but I guess a QEMU/KVM virtual machine or even a physical machine having a CDROM (if you can still find one :-) would also work. Thanks.
libdevice-cdio-perl_0.3.0-5_amd64-20170227T212220Z.gz
Description: application/gzip
libdevice-cdio-perl_0.3.0-5_amd64-20170227T212222Z.gz
Description: application/gzip
