Hello, I'd like to stop building a number of module streams for Fedora; and also I want some to be removed from Fedora 39 before it's GA. (So the last stable release they are in is the Fedora 38)
Name of the module: mariadb
Stream names and the new EOL date: -- 10.7: EOL ASAP -- 10.8: EOL ASAP -- 10.9: EOL ASAP
Any extra information: MariaDB 10.7 and 10.8 reached EOL on upstream. MariaDB 10.9 will reach EOL on upstream in 3-4 weeks.
I'm the maintainer of both MariaDB package and modules.
Metadata Update from @phsmoura: - Issue tagged with: medium-gain, medium-trouble, ops
Hi, since the change to remove modularity from f39+ is approved and we will drop modularity from 39. Is the removal of specific streams needed?
Hmm, right. I've overlooked that.
However after reading through the Fedora change: https://fedoraproject.org/wiki/Changes/RetireModularity#For_maintainers_of_modules
Please retire your modules appropriately, so users are migrated to suitable non-modular content. If you wish to continue shipping multiple different versions or editions of your packages, please follow Multiple packages with the same base name, as was a recommendation of the policy for many years.
I'm not sure what the first sentence ^ means in practice. So I'd better say, yes please, retire those streams as it might make the demise of Modularity less painful for its users.
I don't know how exactly the EOL interacts with DNF though.
The only interaction with DNF, I believe, is when running "dnf system-upgrade". Then DNF resets streams which do not exist in the new repository. That allows upgrading modular packages to nonmodular ones.
For resetting EOLed streams which actually exists in repositories, e.g. if you wanted to prevent people upgrading from Fedora 37 to Fedora 38 to keep using mariadb:10.7, one can populate https://pagure.io/releng/fedora-module-defaults.
Metadata Update from @jnsamyak: - Issue assigned to jnsamyak
The PR is up here on fedora-module-default: https://pagure.io/releng/fedora-module-defaults/pull-request/247
I think this is all done now, please re-open if there's anything further to do.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)