Package Review Exception - mysql9.7 #1551

Closed
opened 2026-06-25 15:01:24 +00:00 by mschorm · 1 comment
Member

Hello,
I'd like to apply for an exception from Package Review Guidelines.

TL;DR:
MySQL in Fedora is packaged as versioned packages (mysql8.0, mysql8.4)
I want to introduce new LTS version of MySQL as a new package (mysql9.7).
It is done by rebase on top of the latest MySQL versioned package (mysql8.4).

I seek your blessing to skip the package review process, since it is a close alternative version of what is already packaged.

This request is an analogue of an older accepted one I had with MariaDB: #1523
pretty much everything there applies here as well.


Rebase is prepared here: https://src.fedoraproject.org/fork/mschorm/rpms/mysql8.4/c/e7487260a5ae5f9959361845db6309e276051719?branch=rebase_to_9.7_LTS

and successfuly built here:
https://copr.fedorainfracloud.org/coprs/mschorm/MySQL-9.7-LTS/builds/

Hello, I'd like to apply for an exception from Package Review Guidelines. TL;DR: MySQL in Fedora is packaged as versioned packages (`mysql8.0`, `mysql8.4`) I want to introduce new LTS version of MySQL as a new package (`mysql9.7`). It is done by rebase on top of the latest MySQL versioned package (`mysql8.4`). I seek your blessing to **skip the package review process**, since it is a close alternative version of what is already packaged. This request is an analogue of an older accepted one I had with MariaDB: https://forge.fedoraproject.org/packaging/guidelines/issues/1523 pretty much everything there applies here as well. --- Rebase is prepared here: https://src.fedoraproject.org/fork/mschorm/rpms/mysql8.4/c/e7487260a5ae5f9959361845db6309e276051719?branch=rebase_to_9.7_LTS and successfuly built here: https://copr.fedorainfracloud.org/coprs/mschorm/MySQL-9.7-LTS/builds/
james closed this issue 2026-06-25 16:26:07 +00:00
Owner

Exception was granted, and we are changing the wording so it should be automatic next time.

Exception was granted, and we are changing the wording so it should be automatic next time.
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
packaging/guidelines#1551
No description provided.