[MDEV-15582] Typo errors in MariaDB upgrade logs Created: 2018-03-16  Updated: 2023-04-27

Status: Confirmed
Project: MariaDB Server
Component/s: Packaging
Affects Version/s: 10.0, 10.1, 10.2.13, 10.2, 10.3
Fix Version/s: 10.4

Type: Bug Priority: Minor
Reporter: Zdravelina Sokolovska (Inactive) Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: beginner-friendly


 Description   

Typo errors in MariaDB upgrade logs
1. Upgrading directly from MySQL 10.1 to MariaDB 10.2
2. rpm qa | grep -i '^mysql'
3. A manual dump and restore using mysqldump is recommended

1 – it's not upgrade from MySQL 10.1 but from MariaDB 10.1
2 – rpm qa | grep -i '^mysql' returns nothing , it has to be also rpm qa | grep -i '^MariaDB'
3 – mysqldump is recommended – mariabackup is not added as option 

A MySQL or MariaDB server package (MariaDB-server-10.1.31-1.el7.centos.x86_64) is installed.
 
 
 
Upgrading directly from MySQL 10.1 to MariaDB 10.2 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-'



 Comments   
Comment by Elena Stepanova [ 2018-03-16 ]

10.0

 
support-files/rpm/server-prein.sh:Upgrading directly from MySQL $old_family to MariaDB $new_family may not
 
support-files/mysql.spec.sh:Upgrading directly from MySQL $old_family to MySQL $new_family may not

10.3

 
support-files/rpm/server-prein.sh:Upgrading directly from MySQL $old_family to MariaDB $new_family may not

Generated at Thu Feb 08 08:22:29 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.