Bug 1239778 - perl-MooseX-Workers: FTBFS in rawhide
Summary: perl-MooseX-Workers: FTBFS in rawhide
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-MooseX-Workers
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Petr Pisar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F23FTBFS
TreeView+ depends on / blocked
 
Reported: 2015-07-05 21:11 UTC by Dennis Gilmore
Modified: 2016-04-07 13:44 UTC (History)
5 users (show)

Fixed In Version: perl-MooseX-Workers-0.23-4
Clone Of:
Environment:
Last Closed: 2015-07-07 11:48:17 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
build.log (6.56 KB, text/plain)
2015-07-05 21:11 UTC, Dennis Gilmore 		no flags Details
root.log (83.66 KB, text/plain)
2015-07-05 21:11 UTC, Dennis Gilmore 		no flags Details
state.log (665 bytes, text/plain)
2015-07-05 21:11 UTC, Dennis Gilmore 		no flags Details
View All

Description Dennis Gilmore 2015-07-05 21:11:42 UTC 
Your package perl-MooseX-Workers failed to build from source in current rawhide.

http://koji.fedoraproject.org/koji/taskinfo?taskID=10129979

For details on mass rebuild see https://fedoraproject.org/wiki/Fedora_23_Mass_Rebuild
Comment 1 Dennis Gilmore 2015-07-05 21:11:44 UTC 
Created attachment 1047649 [details]
build.log
Comment 2 Dennis Gilmore 2015-07-05 21:11:45 UTC 
Created attachment 1047650 [details]
root.log
Comment 3 Dennis Gilmore 2015-07-05 21:11:46 UTC 
Created attachment 1047651 [details]
state.log
Comment 4 Emmanuel Seyman 2015-07-07 11:48:17 UTC 
Rebuilt by ppisar in Rawhide.
Comment 5 Petr Pisar 2015-07-07 11:50:59 UTC 
The build.log reports time out. I could not reproduce it nor find any similar failure in Koschei or CPAN testers history. Either it's a very rare race condition or the builder was ill.

I rebuilt the package with fine-tuned dependencies.
Comment 6 Petr Pisar 2016-04-07 13:44:41 UTC 
Few days ago, I got similar failure with perl-MooseX-Workers-0.24-5.fc25.
Note You need to log in before you can comment on or make changes to this bug.