Bug 1134856 - perl-Test-CheckChanges-0.14-10.fc22 FTBFS: build-time dependency on Module::Build::Version is not declared
Summary: perl-Test-CheckChanges-0.14-10.fc22 FTBFS: build-time dependency on Module::B...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-Test-CheckChanges
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Paul Howarth
QA Contact: Fedora Extras Quality Assurance
URL: http://koji.fedoraproject.org/koji/ta...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-28 11:12 UTC by Petr Pisar
Modified: 2014-08-28 14:16 UTC (History)
2 users (show)

Fixed In Version: perl-Test-CheckChanges-0.14-11.fc22
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-28 14:16:00 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Petr Pisar 2014-08-28 11:12:39 UTC 
perl-Test-CheckChanges-0.14-10.fc22 fails to build in F22 because build-time dependency on Module::Build::Version is not declared:

+ ./Build test
Can't locate Module/Build/Version.pm in @INC (you may need to install the Module::Build::Version module) (@INC contains: /home/test/fedora/perl-Test-CheckChanges/Test-CheckChanges-0.14/blib/lib /home/test/fedora/perl-Test-CheckChanges/Test-CheckChanges-0.14/blib/arch /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at /home/test/fedora/perl-Test-CheckChanges/Test-CheckChanges-0.14/blib/lib/Test/CheckChanges.pm line 123.
# Looks like your test exited with 2 before it could output anything.
t/changes.t .........
Dubious, test returned 2 (wstat 512, 0x200)
Failed 1/1 subtests

This is caused by upgrading perl-Module-Build from 0.42.06 to 0.24.08 which moved the module into different package.
Comment 1 Paul Howarth 2014-08-28 14:16:00 UTC 
There were quite a few missing buildreqs that were getting pulled in implicitly as it happens. Fixed in -11.
Note You need to log in before you can comment on or make changes to this bug.