Description of problem: Today in Fedora, we have minizip-compat-1.2.x (coming from zlib component) and minizip-3.0.x (a separate component which is actually minizip-ng in upstream). There is a discussion on github about what names for those projects are best to use, so once there is a conclusion, this bug is supposed to track the changes done in Fedora. https://github.com/zlib-ng/minizip-ng/issues/358
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
Hello all, Thanks @hhorak for this ticket :) Since a moment, it is really clear, original code/place and NG code/place. To have a perfect compatibility with all, to do not break and do not mix, the goal is to have (like other distos): - zlib - minizip and NG versions: - zlib-ng - minizip-ng Original code is always developed, you can see here: zlib master branch: - https://github.com/madler/zlib/ - https://github.com/madler/zlib/tree/master/contrib/minizip zlib develop branch: - https://github.com/madler/zlib/tree/develop - https://github.com/madler/zlib/tree/develop/contrib/minizip Specified by @hhorak, you can see talk here: - https://github.com/zlib-ng/minizip-ng/issues/358 Thanks a lot in advance. PS: There are release updates.
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle. Changing version to 36.
Clearing needinfo, it's not clear what the info missing was here. Anyway, leaving the next action on the Matej, the assignee.
The Fedora change was created for this. https://fedoraproject.org/wiki/Changes/MinizipRenaming
I'll lead this change and use this BZ as a tracker for the progress along the way
The change has been edited and we will rename only the existing "minizip" package to "minizip-ng". The reason for this is located here: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/FGDEEHM4YANBZUCJIET4LXV2Z34IHBQ5/
This change has been successfully finished. More is tracked in the BZ#2129079