Bug 1406919

Summary: saxpath-1.0-11.fc24 FTBFS
Product: [Fedora] Fedora Reporter: Merlin Mathesius <mmathesi>
Component: saxpathAssignee: Mikolaj Izdebski <mizdebsk>
Status: CLOSED NEXTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: akurtako, dbhole, fnasser, mizdebsk, psabata, sgallagh
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 1.0-13 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-05 09:52:16 UTC Type: Bug
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: 1400162    
Deadline: 2017-01-04   
Attachments:
Description Flags
proposed patch to correct FTBFS issue none

Description Merlin Mathesius 2016-12-21 20:33:18 UTC
saxpath-1.0-11.fc24 fails to build from source.

This affects Base Runtime, Rawhide, and F25.

The reason for this is an undeclared build dependency on java-devel.

This can be corrected by adding a BuildRequires for java-devel.

Comment 1 Merlin Mathesius 2016-12-21 20:35:26 UTC
Created attachment 1234492 [details]
proposed patch to correct FTBFS issue

Comment 2 Merlin Mathesius 2016-12-21 20:36:36 UTC
Please apply the patch or respond with a reason it should not be applied within two weeks. After that time, a provenpackager will go ahead and apply it.

Comment 4 Mikolaj Izdebski 2017-01-05 02:07:57 UTC
Fixed in saxpath-1.0-13

Comment 5 Mikolaj Izdebski 2017-01-05 09:52:16 UTC
I believe that this bug is fixed in saxpath-1.0-13,
which is available in Fedora Rawhide, so I am closing this bug now.

The build containing the fix can be found at Koji:
http://koji.fedoraproject.org/koji/buildinfo?buildID=831289

This bug was fixed in the next release of Fedora, and it is currently
not planned to be fixed in the release it was filed against.
You can update to the newer release of Fedora to get the fix.