F38 proposal: Minizip renaming (Self-Contained Change proposal)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



https://fedoraproject.org/wiki/Changes/MinizipRenaming

This document represents a proposed Change. As part of the Changes
process, proposals are publicly announced in order to receive
community feedback. This proposal will only be implemented if approved
by the Fedora Engineering Steering Committee.

== Summary ==
Renaming the "minizip" package to "minizip-ng" and renaming the
"minizip-compat" zlib subpackage to "minizip" to align with the
upstream naming.

== Owner ==
* Name: [[User:ljavorsk| Lukas Javorsky]]
* Email: ljavorsk@xxxxxxxxxx


== 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. Upstream has also
requested to rename the "minizip-compat" zlib subpackage to "minizip"
which is the right naming for the package.

The "minizip" and "minizip-compat" provides different shared libraries
which prevent us from conflicting sonames.

The plan behind this change can be put into x 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.2-7 and minizip > 3.0.0-1)`

''NOTE: The versions I choose here are the safe versions that create a
space for possible "minizip-compat" rebases''

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
[https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/
Package Retirement Process]

4) Wait for the Fedora 40 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

5) Rename the "minizip-compat" to the "minizip" package and add
`Provides: minizip-compat = %{sameevr}` and `Obsoletes: minizip-compat
< 1.2.12`


== Feedback ==
Early feedback from the community is possite, the feedback is located
in this  [https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/thread/I5WYNPVD3ZOKO3X76LQ5SIRUUXDFUF2Y/
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
several changes in "minizip-compat" package which are 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

=== minizip-compat ===
repoquery --whatrequires "*libminizip.so.1*" | pkgname | uniq

chromedriver

chromium

chromium-headless

domoticz

hashcat

libdigidocpp

minizip-compat-devel

springlobby



== 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 to the deadline, it is possible
to just complete this change with the next release.''


== Documentation ==
[https://github.com/zlib-ng/minizip-ng/issues/358 Upstream issue]
[https://bugzilla.redhat.com/show_bug.cgi?id=2037245 Bugzilla tracker]


-- 
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux