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 1604378

Summary: ipmiutil: FTBFS in Fedora rawhide
Product: [Fedora] Fedora Reporter: Mohan Boddu <mboddu>
Component: ipmiutilAssignee: Andy Cress <arcress>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: arcress
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ipmiutil-3.1.2-3.el6 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-07-23 21:31:31 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: 1602938    
Attachments:
Description Flags
build.log
none
root.log
none
state.log none

Description Mohan Boddu 2018-07-19 22:24:14 UTC
ipmiutil failed to build from source in Fedora rawhide

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild
Please fix ipmiutil 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,
ipmiutil will be orphaned. Before branching of Fedora 30,
ipmiutil 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 Mohan Boddu 2018-07-19 22:24:20 UTC
Created attachment 1463024 [details]
build.log

file build.log too big, will only attach last 32768 bytes

Comment 2 Mohan Boddu 2018-07-19 22:24:27 UTC
Created attachment 1463025 [details]
root.log

file root.log too big, will only attach last 32768 bytes

Comment 3 Mohan Boddu 2018-07-19 22:24:30 UTC
Created attachment 1463026 [details]
state.log

Comment 4 Andy Cress 2018-07-20 14:28:40 UTC
The ipmiutil package built fine as recently as July 11.  Not sure what changed.  Investigating.

Comment 5 Andy Cress 2018-07-20 20:18:47 UTC
Aha.  I think found the problem.  Those targets need $(EXEEXT) added.

util/Makefile.am:183: warning: deprecated feature: target 'iseltime' overrides 'iseltime$(EXEEXT)'
util/Makefile.am:183: change your target to read 'iseltime$(EXEEXT)'
util/Makefile.am:62:   while processing program 'iseltime'

Comment 6 Fedora Update System 2018-07-23 13:31:33 UTC
ipmiutil-3.1.2-3.el6 has been submitted as an update to Fedora EPEL 6. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-386207bbd5

Comment 7 Andy Cress 2018-07-23 13:40:39 UTC
Note that the rawhide/fc29 branch has been updated to ipmiutil-3.1.2-3.fc29 with this fix to util/Makefile.am, but I was unable to use fedpkg update to attach that branch/build to this bug.

build (rawhide, /rpms/ipmiutil.git:f873f1d11cf0d7afd612e825d2a47fe3e4fe03a6)

Comment 9 Fedora Update System 2018-07-23 19:58:34 UTC
ipmiutil-3.1.2-3.el6 has been pushed to the Fedora EPEL 6 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-386207bbd5

Comment 10 Igor Raits 2018-07-23 21:31:31 UTC
There has been at least one successfull build after this bug got created.

ipmiutil-3.1.2-3.fc29: https://koji.fedoraproject.org/koji/buildinfo?buildID=1129269

Comment 11 Fedora Update System 2018-08-08 16:14:44 UTC
ipmiutil-3.1.2-3.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.