Bug 1856759 - perl-XXX-0.35-3.fc33 FTBFS: t/env.t: Can't locate ColorThemeRole/ANSI.pm in @INC at /usr/share/perl5/vendor_perl/Role/Tiny.pm line 52
Summary: perl-XXX-0.35-3.fc33 FTBFS: t/env.t: Can't locate ColorThemeRole/ANSI.pm in @...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-JSON-Color
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jitka Plesnikova
QA Contact: Fedora Extras Quality Assurance
URL: https://koschei.fedoraproject.org/pac...
Whiteboard:
Depends On: 1856854
Blocks: F33FTBFS
TreeView+ depends on / blocked
 
Reported: 2020-07-14 12:03 UTC by Petr Pisar
Modified: 2020-07-15 09:35 UTC (History)
3 users (show)

Fixed In Version: perl-JSON-Color-0.130-2.fc33
Clone Of:
Environment:
Last Closed: 2020-07-15 09:35:37 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Petr Pisar 2020-07-14 12:03:01 UTC 
perl-XXX-0.35-3.fc33 fails to build in Fedora 33, because a test fails:

t/author-pod-syntax.t .... skipped: these tests are for testing by the author
Can't locate ColorThemeRole/ANSI.pm in @INC (you may need to install the ColorThemeRole::ANSI module) (@INC contains: /builddir/build/BUILD/XXX-0.35/blib/lib /builddir/build/BUILD/XXX-0.35/blib/arch /usr/local/lib64/perl5/5.32 /usr/local/share/perl5/5.32 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at /usr/share/perl5/vendor_perl/Role/Tiny.pm line 52.
# Looks like your test exited with 2 before it could output anything.
t/env.t .................. 
Dubious, test returned 2 (wstat 512, 0x200)
Failed 1/1 subtests 

A difference between passing and failing build root is at <https://koschei.fedoraproject.org/build/8579216>.
Comment 1 Jitka Plesnikova 2020-07-14 15:09:37 UTC 
It is caused by update JSON-Color. It requires ColorThemeRole::ANSI since version 0.130.

https://metacpan.org/release/JSON-Color/source/lib/JSON/Color.pm#L190

ColorThemeRole::ANSI has to be packaged.
Note You need to log in before you can comment on or make changes to this bug.