Bug 1239899 - rubygem-coveralls: FTBFS in rawhide
Summary: rubygem-coveralls: FTBFS in rawhide
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: rubygem-coveralls
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Troy Dawson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F23FTBFS
TreeView+ depends on / blocked
 
Reported: 2015-07-05 21:18 UTC by Dennis Gilmore
Modified: 2015-07-27 19:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-07-27 19:12:18 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
build.log (17.74 KB, text/plain)
2015-07-05 21:18 UTC, Dennis Gilmore
no flags Details
root.log (74.63 KB, text/plain)
2015-07-05 21:18 UTC, Dennis Gilmore
no flags Details
state.log (661 bytes, text/plain)
2015-07-05 21:18 UTC, Dennis Gilmore
no flags Details

Description Dennis Gilmore 2015-07-05 21:18:14 UTC
Your package rubygem-coveralls failed to build from source in current rawhide.

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

For details on mass rebuild see https://fedoraproject.org/wiki/Fedora_23_Mass_Rebuild

Comment 1 Dennis Gilmore 2015-07-05 21:18:15 UTC
Created attachment 1048012 [details]
build.log

Comment 2 Dennis Gilmore 2015-07-05 21:18:16 UTC
Created attachment 1048013 [details]
root.log

Comment 3 Dennis Gilmore 2015-07-05 21:18:17 UTC
Created attachment 1048014 [details]
state.log

Comment 4 Jan Kurik 2015-07-15 13:29:08 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle.
Changing version to '23'.

(As we did not run this process for some time, it could affect also pre-Fedora 23 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23


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