[MDEV-4151] Error message on an attempt of RPM upgrade from one major version to another mixes up MySQL and MariaDB Created: 2013-02-08  Updated: 2020-11-09

Status: Open
Project: MariaDB Server
Component/s: Packaging
Affects Version/s: 10.0.1, 5.5.29
Fix Version/s: 10.2

Type: Bug Priority: Minor
Reporter: Elena Stepanova Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: beginner-friendly

Issue Links:
Duplicate
is duplicated by MDEV-7302 rpm upgrade error message gives wrong... Closed
PartOf
is part of MDEV-22315 MySQL -> MariaDB upgrades Open
is part of MDEV-22329 Packages issues when upgrading Open
Relates
relates to MDEV-9584 Upgrading MariaDB 5.5 to 10.1.11 fail... Stalled

 Description   

When RPM/yum upgrade from one major version to another is attempted, it fails with a verbose error message. The text explains why such an upgrade is not recommended and suggests the right way to do it. Sometimes it mentions MySQL instead of MySQL/MariaDB which makes it rather unclear. More importantly, it suggests to find conflicting packages by grepping for 'mysql' which simply doesn't work if the old version is also MariaDB.

An example of the text generated on upgrade from MariaDB 5.5.29 to MariaDB 10.0.1 is below.

A MySQL or MariaDB server package (MariaDB-server-5.5.29-1) is installed.
 
Upgrading directly from MySQL 5.5 to MariaDB 10.0 may not
be safe in all cases.  A manual dump and restore using mysqldump is
recommended.  It is important to review the MariaDB manual's Upgrading
section for version-specific incompatibilities.
 
A manual upgrade is required.
 
- Ensure that you have a complete, working backup of your data and my.cnf
  files
- Shut down the MySQL server cleanly
- Remove the existing MySQL packages.  Usually this command will
  list the packages you should remove:
  rpm -qa | grep -i '^mysql-'
 
  You may choose to use 'rpm --nodeps -ev <package-name>' to remove
  the package which contains the mysqlclient shared library.  The
  library will be reinstalled by the MariaDB-shared package.
- Install the new MariaDB packages supplied by Monty Program AB
- Ensure that the MariaDB server is started
- Run the 'mysql_upgrade' program
 
This is a brief description of the upgrade process.  Important details
can be found in the MariaDB manual, in the Upgrading section.A MySQL or MariaDB server package (MariaDB-server-5.5.29-1) is installed.
 
Upgrading directly from MySQL 5.5 to MariaDB 10.0 may not
be safe in all cases.  A manual dump and restore using mysqldump is
recommended.  It is important to review the MariaDB manual's Upgrading
section for version-specific incompatibilities.
 
A manual upgrade is required.
 
- Ensure that you have a complete, working backup of your data and my.cnf
  files
- Shut down the MySQL server cleanly
- Remove the existing MySQL packages.  Usually this command will
  list the packages you should remove:
  rpm -qa | grep -i '^mysql-'
 
  You may choose to use 'rpm --nodeps -ev <package-name>' to remove
  the package which contains the mysqlclient shared library.  The
  library will be reinstalled by the MariaDB-shared package.
- Install the new MariaDB packages supplied by Monty Program AB
- Ensure that the MariaDB server is started
- Run the 'mysql_upgrade' program
 
This is a brief description of the upgrade process.  Important details
can be found in the MariaDB manual, in the Upgrading section.



 Comments   
Comment by Elena Stepanova [ 2014-12-12 ]

Raised the priority a bit because there is another bug report MDEV-7302 about the same problem.

Comment by Kolbe Kegel (Inactive) [ 2014-12-12 ]

Open nearly 2 years! Can we just get this fixed up? It seems really like an easy fix!

Generated at Thu Feb 08 06:54:11 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.