Minizip Renaming
Summary
Renaming the "minizip" package to "minizip-ng" to align with the upstream naming.
Owner
- Name: Lukas Javorsky
- Email: ljavorsk@redhat.com
Current status
- Targeted release: Fedora Linux 38
- Last updated: 2022-09-22
- devel thread
- FESCo issue: #2857
- Tracker bug: #2129079
- Release notes tracker: #880
Detailed Description
Upstream has changed the naming of the "minizip" package to "minizip-ng" and we should follow their naming so there is no confusion about which package is the right one.
The "minizip" and "minizip-compat" provides different shared libraries which prevent us from conflicting sonames.
The plan behind this change can be put into 4 steps which will be completed separately and in the given order:
NOTE: All of the Provides and Obsoletes will be added to the *-devel subpackages as well.
1) Create a new package "minizip-ng" which will Provides: minizip = %{sameevr} and Obsoletes: minizip < 3.0.3
2) Rebuild all of the packages that BuildRequire/Require "minizip" package to BuildRequire/Require new "minizip-ng" package
3) Retire the "minizip" package following the Package Retirement Process
4) Wait for the Fedora 42 when it's ensured that every user has updated at least to the Fedora 38. Remove the Provides and Obsoletes from the "minizip-ng" package
Feedback
Early feedback from the community is positive, the feedback is located in this Email thread
Benefit to Fedora
Fedora should always respect upstream package naming, so the users are not confused about which package are they installing. This naming change will align the naming with the upstream.
Scope
- Proposal owners: New package "minizip-ng" will be created and the "minizip" package will be retired. More described in the Detailed Description.
- Other developers: Change the names of their BuildRequires/Requires accordingly.
- Release engineering: No action required
- Policies and guidelines: N/A (not needed for this Change)
- Trademark approval: N/A (not needed for this Change)
- Alignment with Objectives:
Upgrade/compatibility impact
When following the plan in Detailed Description there will be no need for manual action. Everything will be handled by the automated dnf upgrade.
How To Test
User Experience
Dependencies
List of the packages from Fedora 37
minizip
repoquery --whatrequires "*libminizip.so.3*" | pkgname | uniq
R-libSBML
collada-dom
dolphin-emu
dolphin-emu-tool
java-libsbml
keepassxc
libnuml
librasterlite2
libsbml
libspatialite
libxlsxwriter
minizip-devel
perl-LibSBML
python3-libsbml
ruby-SBML
sigil
vxl
xiphos
zfstream
Contingency Plan
- Contingency mechanism: Remove the builds created and revert shipped changes. Done by any Fedora packager (preferred by the one who knows about this change)
- Contingency deadline: Beta freeze
- Blocks release? No
NOTE: If we don't finish this change by the deadline, it is possible to just complete this change with the next release.
Documentation
Upstream issue Bugzilla tracker