Bug 1124400 - perl-MetaCPAN-Client-1.006000-1.fc22 FTBFS:
Summary: perl-MetaCPAN-Client-1.006000-1.fc22 FTBFS:
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-MetaCPAN-Client
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-07-29 12:17 UTC by Petr Pisar
Modified: 2014-08-19 15:39 UTC (History)
2 users (show)

Fixed In Version: perl-MetaCPAN-Client-1.007000-1.fc22
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-19 15:39:19 UTC


Attachments (Terms of Use)

Description Petr Pisar 2014-07-29 12:17:49 UTC
perl-MetaCPAN-Client-1.006000-1.fc22 fails to build in F22 due to tests:

#   Failed test 'Pod coverage on MetaCPAN::Client::ResultSet'
#   at /usr/share/perl5/vendor_perl/Test/Pod/Coverage.pm line 126.
# Coverage for MetaCPAN::Client::ResultSet is 87.5%, with 1 naked subroutine:
# 	has_scroller
# Looks like you failed 1 test of 12.
t/release-pod-coverage.t .. 
Dubious, test returned 1 (wstat 256, 0x100)
Failed

Build root difference between last working and this build is:

Removed packages:
	coreutils-8.22
	findutils-4.5.13
	gdb-7.7.90.20140711
	perl-Class-Load-0.21
	perl-Devel-PartialDump-0.15
	perl-Dist-CheckConflicts-0.11
	perl-Eval-Closure-0.08
	perl-Moo-1.003001
	perl-Moose-2.1005
	perl-MRO-Compat-0.12
	perl-Package-DeprecationManager-0.13
	setup-2.9.0
Added packages:
	coreutils-8.23
	findutils-4.5.14
	gdb-7.8
	perl-Import-Into-1.002002
	perl-Moo-1.005000
	setup-2.9.1

Comment 1 Paul Howarth 2014-07-29 14:01:59 UTC
This has been triggered by the recent update of Moo to 1.005000. I think it's probably an issue in either Moo or Pod::Coverage but I'm asking upstream's opinion first:

https://github.com/CPAN-API/metacpan-client/issues/16

Comment 2 Paul Howarth 2014-08-19 15:39:19 UTC
I've worked around this for 1.007000 by disabling the release tests, which would fail anyway due to missing optional test dependencies if RELEASE_TESTING was set.


Note You need to log in before you can comment on or make changes to this bug.