Bug 1583293 - rubygem-hitimes: FTBFS in Fedora 28
Summary: rubygem-hitimes: FTBFS in Fedora 28
Keywords:
Status: CLOSED DUPLICATE of bug 1556366
Alias: None
Product: Fedora
Classification: Fedora
Component: rubygem-hitimes
Version: 28
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Josef Strzibny
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F28FTBFS
TreeView+ depends on / blocked
 
Reported: 2018-05-28 16:10 UTC by Fedora Release Engineering
Modified: 2018-05-28 16:21 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-05-28 16:21:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
root.log (69.98 KB, text/plain)
2018-05-28 16:11 UTC, Fedora Release Engineering
no flags Details
build.log (17.87 KB, text/plain)
2018-05-28 16:11 UTC, Fedora Release Engineering
no flags Details
state.log (651 bytes, text/plain)
2018-05-28 16:11 UTC, Fedora Release Engineering
no flags Details

Description Fedora Release Engineering 2018-05-28 16:10:52 UTC
rubygem-hitimes failed to build from source in Fedora 28

https://koji.fedoraproject.org/koji/taskinfo?taskID=27246231
https://koji.fedoraproject.org/koji/buildinfo?buildID=1086340


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild
Please fix rubygem-hitimes at your earliest convenience and set the bug's status to
ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks,
rubygem-hitimes will be orphaned. Before branching of Fedora 29,
rubygem-hitimes will be retired, if it still fails to build.

For more details on the FTBFS policy, please visit:
https://fedoraproject.org/wiki/Fails_to_build_from_source

Comment 1 Fedora Release Engineering 2018-05-28 16:11:00 UTC
Created attachment 1443523 [details]
root.log

Comment 2 Fedora Release Engineering 2018-05-28 16:11:05 UTC
Created attachment 1443524 [details]
build.log

Comment 3 Fedora Release Engineering 2018-05-28 16:11:09 UTC
Created attachment 1443525 [details]
state.log

Comment 4 Vít Ondruch 2018-05-28 16:21:02 UTC

*** This bug has been marked as a duplicate of bug 1556366 ***


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