Bug 1622100

Summary: mingw-opusfile needs update to handle new mingw-openssl
Product: [Fedora] Fedora Reporter: Richard W.M. Jones <rjones>
Component: mingw-opusfileAssignee: David King <amigadave>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: amigadave
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: 2019-02-13 11:36:28 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:

Description Richard W.M. Jones 2018-08-24 12:54:18 UTC
Description of problem:

mingw-openssl in Rawhide is now based on 1.1.0h which has a bunch
of CVE fixes, but also has a slightly new API.

mingw-opusfile does not build against this, and it appears to
require changes to deal with the new API.

Most likely synchronizing mingw-opusfile and ordinary Fedora
opusfile packages will fix this.

Version-Release number of selected component (if applicable):

mingw-opusfile-0.8-6.fc30

Additional info:

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

Comment 1 Yaakov Selkowitz 2018-08-29 12:31:34 UTC
It seems a rebase to 0.10 (to match the native package in Fedora) should suffice.

Comment 2 David King 2018-08-29 12:35:02 UTC
(In reply to Yaakov Selkowitz from comment #1)
> It seems a rebase to 0.10 (to match the native package in Fedora) should
> suffice.

I kicked off a scratch build, but suffice to say, a rebase to a newer version of opusfile is not sufficient on its own:

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

The Windows-specific SSL code will need some porting to the new API in 1.1.

Comment 3 David King 2019-02-13 11:36:28 UTC

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