#3420 Change: switch distribution default MySQL from 8.0 to 8.4
Closed: Accepted by zbyszek. Opened by amoloney.

MySQL is packages now use the versioned package layout. Currently we have packages mysql8.0 and mysql8.4 which both provides their respective versioned named sub-packages (e.g. mysql8.0-server or mysql8.4-errmsg etc.)

A "distribution default" version is the one, that also provides the unversioned names (e.g. mysql-server or mysql-errmsg etc.)

Currently the "distribution default" version of MySQL is 8.0. Let's switch to 8.4.
* Change proposal
* devel-announce post
* Discourse discussion
* Owners: @mschorm

Owners, do not implement this work until the FESCo vote has explicitly ended.
The Fedora Program Manager will create a tracking bug in Bugzilla for this Change, which is your indication to proceed. See the FESCo ticket policy and the Changes policy for more information.

REMINDER: This ticket is for FESCo members to vote on the proposal. Further discussion should happen in the Discourse discussion linked above. Additional discussion may happen on the Fedora Devel mailing list.


Clarification: MySQL 8.0 to MySQL 8.4

Considering that MySQL 8.0 seems to have and EOL in April 2026, moving to MySQL 8.4 seems the right approach to me.

+1

@mschorm Please rename the wiki page.

+1 otherwise

@zbyszek I tried to rename the page via the move button on the top right of the web page, while logged in, but I got a backtrace:

Internal error
...
ACCESS_REFUSED - Login was refused using authentication mechanism EXTERNAL.
...

I may retry later this week, after the datacenter move.
Or you can retry, to check if it really is some kind of authentication / permission problem.

@mschorm, this error is most probably related to the DC migration

After a week:
APPROVED (+4, 0, 0)

Metadata Update from @zbyszek:
- Issue tagged with: pending announcement

Wiki page rename works now, done.

Announced: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/4EHEV57OLAUEYPABK75J6QXZKPSRWXQR/

Metadata Update from @zbyszek:
- Issue untagged with: pending announcement
- Issue close_status updated to: Accepted
- Issue status updated to: Closed (was: Open)

Metadata