Hi,

While the text that the upgrade offers is weird and should be fixed, in the essence it holds true:

Upgrading directly from MySQL <unrecognized version package MariaDB-server-5.5.36-1.el6.x86_64

MariaDB-server-5.5.36-1.el6.x86_64 is not installed> 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

serg,

Even if we don't support major upgrade via yum, there is still something to fix there. First, the complaint about a different vendor is just weird, since both packages are ours, and something is really wrong with this message:

The current MariaDB server package is provided by a different

vendor (package MariaDB-server-5.5.36-1.el6.x86_64

MariaDB-server-5.5.36-1.el6.x86_64 is not installed) than Monty Program AB.

Secondly, this part doesn't look right either (the cause is probably the same):

Upgrading directly from MySQL <unrecognized version package MariaDB-server-5.5.36-1.el6.x86_64

MariaDB-server-5.5.36-1.el6.x86_64 is not installed> to MariaDB 10.0 may not

Thank you for checking this - Manual upgrade path went smoothly ok.

It would be good to state in the upgrade text that major update via yum is not supported and manual upgrade path needs to applied. Currently that has not been stated in the Release Notes or in Installing MariaDB with yum document page. At least I was having impression that upgrade using yum would be possible (like in minor upgrades).

These messages are still wrong. Here's what I get updating from 10.0.9 to 10.0.10 on CentOS 6

******************************************************************
A MySQL or MariaDB server package () is installed.

The current MariaDB server package is provided by a different
vendor (package is not installed) than Monty Program AB. Some files may be installed
to different locations, including log files and the service
startup script in /etc/init.d/.

Upgrading directly from MySQL <unrecognized version package is not installed> 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.
******************************************************************

Yes, unfortunately it's a new bug, now filed as MDEV-5986.