libpetal-utils-perl version 0.06-1 failed to build in oneiric
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libpetal-utils-perl (Debian) |
Fix Released
|
Unknown
|
|||
libpetal-utils-perl (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Oneiric |
Fix Released
|
High
|
Unassigned |
Bug Description
libpetal-utils-perl version 0.06-1 failed to build in oneiric
Link to failed build: https:/
Details about the rebuild:
http://
Direct link to the build log: https:/
This log snippet might be of interest, since it triggered the matcher 'Purging chroot-autobuild'.
Excerpt 484 lines into the build log:
Parse errors: No plan found in TAP output
t/24__Substr.t (Wstat: 65280 Tests: 0 Failed: 0)
Non-zero exit status: 255
Parse errors: No plan found in TAP output
t/25__Decode.t (Wstat: 65280 Tests: 0 Failed: 0)
Non-zero exit status: 255
Parse errors: No plan found in TAP output
t/26__Printf.t (Wstat: 65280 Tests: 0 Failed: 0)
Non-zero exit status: 255
Parse errors: No plan found in TAP output
Files=15, Tests=37, 2 wallclock secs ( 0.05 usr 0.04 sys + 2.03 cusr 0.22 csys = 2.34 CPU)
Result: FAIL
Failed 13/15 test programs. 0/37 subtests failed.
make: *** [build-stamp] Error 255
dpkg-buildpackage: error: debian/rules build gave error exit status 2
*******
Build finished at 20110824-0453
FAILED [dpkg-buildpackage died]
Purging chroot-
Changed in libpetal-utils-perl (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in libpetal-utils-perl (Debian): | |
status: | Unknown → Fix Released |
This bug was fixed in the package libpetal-utils-perl - 0.06-2
---------------
libpetal-utils-perl (0.06-2) unstable; urgency=low
[ Nathan Handler ]
* debian/watch: Update to ignore development releases.
[ Ansgar Burchardt ]
* debian/control: Convert Vcs-* fields to Git.
[ Damyan Ivanov ] )dependencies to 2.19-2
* Bump libpetal-perl (build-
Ensures Petal that is not broken by Safe in Perl 5.12.1
Closes: #627271 -- FTBFS
* Use tiny debhelper debian/rules and compatibility level 8
* Use source format '3.0 (quilt)'
* Claim conformance with Policy 3.9.2
-- Damyan Ivanov <email address hidden> Sun, 14 Aug 2011 15:00:22 +0300