This is the initial release for the 5.5 branch into the atomic repository. It contains numerous changes over the 5.1 branch. This update constitutes a major change and additional steps may be required to complete the upgrade.

Release Notes
* %post routine has an upgrade event for the database format changes. This is only triggered for systems running plesk, and can be overridden by setting the following before upgrading:
export ATOMIC_SKIP=1
* Cloudlinux Mysql Governor patches have been merged in to this release.

Changelog:
http://dev.mysql.com/doc/refman/5.5/en/news-5-5-16.html

To Upgrade:
yum upgrade mysql

Remi?

Yeah, take a look at the changelog

Hi,

Could it be possible to also maintain the 5.1 series RPMS in the repository for us who have automated installations of 5.1 and now our Virtuozzo containers won't complete installation because of the 5.1-specific my.cnf we've customized?

Thanks!

After the upgrade I have:

ruby-mysql-2.7-200705221357
mysql-libs-5.5.17-2.el5.art
mysqlclient15-5.0.90-1.el5.art
mysql-bench-5.5.17-2.el5.art
php-mysql-5.2.17-1.el5.art
mysql-libs-5.5.17-2.el5.art
mysql-bench-5.5.17-2.el5.art
mysql-5.5.17-2.el5.art
mysqlclient15-5.0.90-1.el5.art
perl-DBD-mysql-4.014-1.el5.rf
php-mysql-5.2.17-1.el5.art
mysql-5.5.17-2.el5.art
mysql-devel-5.5.17-2.el5.art
mysql-server-5.5.17-2.el5.art
mysql-devel-5.5.17-2.el5.art

..should I be removing mysqlclient15 or anything else? (centos 5, Plesk 9)
I'm seeing crashes ("mysql got signal 11") about once every minute now..

Thanks!
-t

thats just a compat library, removing it would probably break a mountain of other things. I'd take a look at your mysql logs to see if they can shed an light on why its Segfaulting.