Bug #93086 Upgrading from mysql57-community-release to mysql80-community-release steps
Submitted: 5 Nov 2018 18:38 Modified: 6 Dec 2018 8:17
Reporter: Daniël van Eeden (OCA) Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Package Repos and Docker Images Severity:S3 (Non-critical)
Version:fc29-1 OS:Any
Assigned to: CPU Architecture:Any

[5 Nov 2018 18:38] Daniël van Eeden
Description:
I had mysql57-community-release-fc27-10.noarch installed on fc29

To move to mysql80-community-release-fc29-1.noarch required me to run dnf install --allowerasing mysql80-community-release-fc29-1.noarch

How to repeat:
Have mysql57-community-release installed and try to move to mysql80-community-release

Suggested fix:
Have mysql80-community-release set to obsolete mysql57-community-release
[6 Nov 2018 8:17] Terje Røsten
Hi!

Thanks for your report!

This is by design, mysql57-community-release has MySQL 5.7 as default MySQL server repo, while mysql80-community-release has MySQL 8.0 server repo as default. Both packages are in both repos. If mysql80-community-release was set to obsolete mysql57-community-release almost *all* users of MySQL 5.7 repo would be force upgraded to MySQL 8.0. That's not wanted. Users should be able to choose to run MySQL 5.7 to 8.0
and get minor version upgrades via repo.

The mechanism for making the choice is to install wanted release package: mysql57-community-release or mysql80-community-release.
[7 Dec 2018 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".