Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1423620

Summary: gmock: FTBFS in rawhide
Product: [Fedora] Fedora Reporter: Fedora Release Engineering <releng>
Component: gmockAssignee: Terje Røsten <terjeros>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: helio, jwakely, terjeros, tstclair
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: 2017-02-18 21:57:57 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: 1423041    
Attachments:
Description Flags
build.log
none
root.log
none
state.log none

Description Fedora Release Engineering 2017-02-17 14:06:33 UTC 
Your package gmock failed to build from source in current rawhide.

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

For details on mass rebuild see https://fedoraproject.org/wiki/Fedora_26_Mass_Rebuild
Comment 1 Fedora Release Engineering 2017-02-17 14:06:38 UTC 
Created attachment 1252236 [details]
build.log
Comment 2 Fedora Release Engineering 2017-02-17 14:06:42 UTC 
Created attachment 1252237 [details]
root.log
Comment 3 Fedora Release Engineering 2017-02-17 14:06:45 UTC 
Created attachment 1252238 [details]
state.log
Comment 4 Jonathan Wakely 2017-02-18 21:38:23 UTC 
Failing due to https://github.com/google/googletest/issues/705 which I thought was already fixed in rawhide, but apparently not.

I've added a patch and started a new build.