Percona Server version 5.6.16-64.2
Percona is glad to announce the release of Percona Server 5.6.16-64.2 on March 25th, 2014. Downloads are available here and from the Percona Software Repositories.
Based on MySQL 5.6.16, including all the bug fixes in it, Percona Server 5.6.16-64.1 is the current GA release in the Percona Server 5.6 series. All of Percona’s software is open-source and free, all the details of the release can be found in the 5.6.16-64.2 milestone at Launchpad.
Bugs Fixed:
- The upgrade to Percona Server 5.6.16-64.1 would silently comment out any options in
my.cnfthat have paths specified that containshare/mysql. Bug fixed #1293867. - Percona Server could fail to start after upgrade if the
lc-messages-diroption was set in themy.cnfconfiguration file. Bug fixed #1294067. - Dependency on
mysql-commonpackage, introduced in Percona Server 5.6.16-64.0 could lead to wrongly chosen packages for upgrade, spurious removes and installs with some combination of packages installed which use the mysql libraries. Bug fixed #1294211. - These three bugs were fixed by removing the dependency on mysql-common package.
- Percona Toolkit UDFs were missing from Debian/Ubuntu packages, this regression was introduced in Percona Server 5.6.16-64.0. Bug fixed #1296416.
- Percona Server installer will create the symlinks from
libmysqlclienttolibperconaserverclientduring the installation on CentOS. This was implemented in order to provide the backwards compatibility after thelibmysqlclientlibrary has been renamed tolibperconaserverclient.
Release notes for Percona Server 5.6.16-64.2 are available in our online documentation. Bugs can be reported on the launchpad bug tracker.
I realize it’s possible to fix the “libperconaserverclient.so versus libmysqlclient.so problem” at compile time by patching some of the source files prior to compilation, but I am still reiterating my request that Percona make this a compile-time configuration option.
Percona Server is billed as a “drop-in” replacement for Oracle MySQL. When I build from source, I need the resulting binaries, libraries, and support files to be named exactly as they are in a full Oracle MySQL installation. I understand that some Linux distros split the client-side and server-side components, but others (such as Slackware) do not.
There has got to be a better way of supporting all distros – whether MySQL is monolithic or split into client-server components. Making the choice configurable when building the package would go a long way toward alleviating the problems we are seeing.
Thank you for your consideration.