Bug 1497193 - perl-Pinto-0.14-1.fc27 FTBFS: Attribute (target_perl_version) does not pass the type constraint because: perl version (5.026001) is unknown
Summary: perl-Pinto-0.14-1.fc27 FTBFS: Attribute (target_perl_version) does not pass t...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-Pinto
Version: 26
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jitka Plesnikova
QA Contact: Fedora Extras Quality Assurance
URL: https://apps.fedoraproject.org/kosche...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-29 12:43 UTC by Petr Pisar
Modified: 2017-10-03 12:12 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-10-03 12:12:37 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Petr Pisar 2017-09-29 12:43:11 UTC
perl-Pinto-0.14-1.fc27 fails to build in F27:

t/02-bowels/05-compare.t .............. ok
Attribute (target_perl_version) does not pass the type constraint because: perl version (5.026001) is unknown to me; try updating Pinto's copy of Module::CoreList at reader Pinto::Config::target_perl_version (defined at /builddir/build/BUILD/Pinto-0.14/blib/lib/Pinto/Config.pm line 161) line 11
[...]

This is caused by a hard-coded maximal supported Perl version in Pinto. It's triggered by upgrading Perl in to 5.26.1 and 5.24.3. F27 and F26 are affected. I did not try F25. This seems to be fixed in Pinto 0.14:

0.14      2017-08-06 00:09:07-07:00 America/Los_Angeles
      - Upgraded to latest Module::CoreList to support newer perls.

Either back-port the fix or unbundle Pinto'd Module::CoreList.

Comment 1 Jitka Plesnikova 2017-10-03 12:12:37 UTC
Module::CoreList is not bundled in Pinto. 

The issue was caused because perl-Pinto was build against Perl 5.26.1/5.24.3, but the latest Module::CoreList (which defined these version) was not in build-root yet. It will be solved, when the latest Module::CoreList is in updates.


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