Bug 1609830

Summary: drop minizip-compat (was: package minizip separately from zlib)
Product: [Fedora] Fedora Reporter: Pavel Raiskup <praiskup>
Component: zlibAssignee: Pavel Raiskup <praiskup>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: jaromir.capik, jchaloup, Neustradamus, praiskup
Target Milestone: ---Keywords: Tracking
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-09-24 11:49:23 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: 1615381, 1623787    
Bug Blocks:    

Description Pavel Raiskup 2018-07-30 15:08:13 UTC
The minizip code is totally unsupported by zlib upstream, I tried to submit
some pull requests - but per README file it was my mistake.

I tried to contact original authors of minizip as a last resort today,
and I'm waiting for reply -> but most probably we should simply stop building that code in zlib.spec and provide minizip.spec separately (built from one of
the existing forks, or simply provide new one that is 1:1 compatible with
zlib's version - because that's what Fedora packages expect).

Comment 2 Jan Kurik 2018-08-14 11:01:57 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle.
Changing version to '29'.

Comment 3 Pavel Raiskup 2018-09-05 07:31:25 UTC
Second step is done:

  Rename   'minizip' -> 'minizip-compat'
  Rename   'minizip-devel' -> 'minizip-devel-compat'
  New pkg  'minizip'

I tried to port two packages, and it turns out to be not that trivial:

https://github.com/psi-im/psi/issues/388
https://github.com/assimp/assimp/issues/2121

Comment 5 Pavel Raiskup 2018-09-24 11:49:23 UTC
Even though this is older issue, close this instead of the other duplicate
to avoid additional bugzilla mail traffic.

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