request-tracker4: FTBFS: "Can't locate Plack/Handler/Starlet.pm in @INC"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
request-tracker4 (Debian) |
Fix Released
|
Unknown
|
|||
request-tracker4 (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
Imported from Debian bug http://
Package: request-tracker4
Severity: serious
Version: 4.0.17-2
Hello there,
I tried building your package, but it failed in a clean sbuild chroot:
> SOME DEPENDENCIES WERE MISSING.
> PSGI missing dependencies:
> Plack::
> Can't locate Plack/Handler/
> make[1]: *** [testdeps] Error 1
> make[1]: Leaving directory `/«PKGBUILDDIR»'
> make: [build-stamp] Error 2 (ignored)
This seems to be a case of a missing Build-Depends on the "starlet"
package. However, even with that added, I get test failures:
> # Failed test 'found correct number of ticket(s) by 'RefersTo != 5 AND MemberOf = 5''
> # at t/ticket/
> # got: '0'
> # expected: '1'
> t/ticket/
>
> # Failed test 'found correct number of ticket(s) by 'RefersTo IS NULL AND MemberOf IS NOT NULL''
> # at t/ticket/
> # got: '0'
> # expected: '1'
> # Some tests failed or we bailed out, tmp directory '/«PKGBUILDDIR»
> # Looks like you failed 2 tests of 99.
and
> ==( 18056;152 38/? 0/? )======
> # Failed test 'Now not a member of the supergroup'
> # at t/web/owner_
> # Structures begin differing at:
> # $got->[0] = Does not exist
> # $expected->[0] = 'Supergroup'
> # Some tests failed or we bailed out, tmp directory '/root/
> # Looks like you failed 1 test of 48.
> t/web/owner_
> Failed 1/48 subtests
Changed in request-tracker4 (Ubuntu): | |
importance: | Undecided → High |
description: | updated |
tags: | added: ftbfs trusty |
Changed in request-tracker4 (Debian): | |
importance: | Undecided → Unknown |
Changed in request-tracker4 (Debian): | |
status: | New → Incomplete |
Changed in request-tracker4 (Debian): | |
status: | Incomplete → Fix Released |
Changed in request-tracker4 (Ubuntu): | |
status: | Invalid → Fix Released |
Looks like this bug should probably be closed as it was in Debian. The problem just "went away".