Bug 1583288

Summary: rubygem-database_cleaner: FTBFS in Fedora 28
Product: [Fedora] Fedora Reporter: Fedora Release Engineering <releng>
Component: rubygem-database_cleanerAssignee: Vít Ondruch <vondruch>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 28CC: vondruch
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-28 16:19:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1555378    
Attachments:
Description Flags
root.log
none
build.log
none
state.log none

Description Fedora Release Engineering 2018-05-28 16:07:32 UTC 
rubygem-database_cleaner failed to build from source in Fedora 28

https://koji.fedoraproject.org/koji/taskinfo?taskID=27246143
https://koji.fedoraproject.org/koji/buildinfo?buildID=1086325


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild
Please fix rubygem-database_cleaner 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-database_cleaner will be orphaned. Before branching of Fedora 29,
rubygem-database_cleaner 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:07:39 UTC 
Created attachment 1443501 [details]
root.log
Comment 2 Fedora Release Engineering 2018-05-28 16:07:43 UTC 
Created attachment 1443502 [details]
build.log
Comment 3 Fedora Release Engineering 2018-05-28 16:07:47 UTC 
Created attachment 1443503 [details]
state.log
Comment 4 Vít Ondruch 2018-05-28 16:19:44 UTC 

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