fails to build from source: libparse-debianchangelog-perl

Bug #569828 reported by Matthias Klose
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libparse-debianchangelog-perl (Debian)
Fix Released
Unknown
libparse-debianchangelog-perl (Ubuntu)
Fix Released
High
Unassigned
Lucid
Fix Released
High
Unassigned

Bug Description

Binary package hint: libparse-debianchangelog-perl

see https://launchpad.net/ubuntu/+archive/test-rebuild-20100407/+build/1668177

# oldest_version=961025-1
# Looks like you failed 1 test of 90.
t/Parse-DebianChangelog.t .................
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/90 subtests

Test Summary Report
-------------------
t/Parse-DebianChangelog.t (Wstat: 256 Tests: 90 Failed: 1)
  Failed test: 82
  Non-zero exit status: 1
Files=3, Tests=111, 2 wallclock secs ( 0.05 usr 0.00 sys + 1.86 cusr 0.26 csys = 2.17 CPU)
Result: FAIL
Failed 1/3 test programs. 1/111 subtests failed.
make[1]: *** [test] Error 1
make[1]: Leaving directory `/build/buildd/libparse-debianchangelog-perl-1.1.1'
make: *** [install-stamp] Error 2

Matthias Klose (doko)
Changed in libparse-debianchangelog-perl (Ubuntu):
importance: Undecided → High
milestone: none → ubuntu-10.04
status: New → Confirmed
Changed in libparse-debianchangelog-perl (Debian):
status: Unknown → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libparse-debianchangelog-perl - 1.1.1-2ubuntu2

---------------
libparse-debianchangelog-perl (1.1.1-2ubuntu2) lucid; urgency=low

  * Strip out duplicate references to bugs, fixing a test suite failure with
    the current dpkg and solving a build failure. Closes: #560634,
    LP: #569828.
 -- Steve Langasek <email address hidden> Mon, 26 Apr 2010 15:50:57 +0000

Changed in libparse-debianchangelog-perl (Ubuntu Lucid):
status: Confirmed → Fix Released
Changed in libparse-debianchangelog-perl (Debian):
status: New → Fix Committed
Changed in libparse-debianchangelog-perl (Debian):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.