Bug 1424337 - rubygem-minitest: FTBFS in rawhide
Summary: rubygem-minitest: FTBFS in rawhide
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: rubygem-minitest
Version: 26
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mo Morsi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F26FTBFS
TreeView+ depends on / blocked
 
Reported: 2017-02-17 16:46 UTC by Fedora Release Engineering
Modified: 2017-05-05 16:21 UTC (History)
3 users (show)

Fixed In Version: rubygem-minitest-5.10.1-100.fc27
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-05 16:21:54 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
build.log (11.36 KB, text/plain)
2017-02-17 16:46 UTC, Fedora Release Engineering
no flags Details
root.log (73.44 KB, text/plain)
2017-02-17 16:46 UTC, Fedora Release Engineering
no flags Details
state.log (655 bytes, text/plain)
2017-02-17 16:46 UTC, Fedora Release Engineering
no flags Details

Description Fedora Release Engineering 2017-02-17 16:46:08 UTC
Your package rubygem-minitest failed to build from source in current rawhide.

https://koji.fedoraproject.org/koji/taskinfo?taskID=17790414

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

Comment 1 Fedora Release Engineering 2017-02-17 16:46:13 UTC
Created attachment 1254287 [details]
build.log

Comment 2 Fedora Release Engineering 2017-02-17 16:46:16 UTC
Created attachment 1254288 [details]
root.log

Comment 3 Fedora Release Engineering 2017-02-17 16:46:19 UTC
Created attachment 1254289 [details]
state.log

Comment 4 Fedora End Of Life 2017-02-28 12:08:56 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.

Comment 5 Upstream Release Monitoring 2017-05-05 15:18:34 UTC
mtasaka's rubygem-minitest-5.10.1-100.fc27 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=887065


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