MySQL 5.6.23 has been released by Oracle on February 2nd 2015. Please read the full Changelog fore more details.
The corresponding packages are now available for Debian 7 “Wheezy”, on both amd64 and i386 architectures.
MySQL 5.6.23 has been released by Oracle on February 2nd 2015. Please read the full Changelog fore more details.
The corresponding packages are now available for Debian 7 “Wheezy”, on both amd64 and i386 architectures.
Thank you for this update.
The installation process crashed : Preparing to replace mysql-server-5.6 5.6.21-1
dotdeb.1 (using …/mysql-server-5.6_5.6.23-1dotdeb.1_amd64.deb) … Stopping MySQL database server: mysqld. Stopping MySQL database server: mysqld. cp: cannot overwrite directory `/var/lib/mysql-upgrade/DATADIR.link/mysql’ with non-directory dpkg: error processing /var/cache/apt/archives/mysql-server-5.6_5.6.23-1~dotdeb.1_amd64.deb (–unpack): subprocess new pre-installation script returned error exit status 1uname -a
Linux ns4 3.10.23-xxxx-std-ipv6-64 #1 SMP Tue Mar 18 14:48:24 CET 2014 x86_64 GNU/Linux
@Guillaume Plessis : Sorry too for my late answer ! The datadir is already good in /etc/mysql/my.cnf.
At the second upgrade I have now the following error :
Preparing to replace mysql-server-5.6 5.6.21-1
dotdeb.1 (using …/mysql-server-5.6_5.6.23-1dotdeb.1_amd64.deb) … Stopping MySQL database server: mysqld. Stopping MySQL database server: mysqld. cp: cannot overwrite directory `/var/lib/mysql-upgrade/DATADIR.link/mysql’ with non-directory dpkg: error processing /var/cache/apt/archives/mysql-server-5.6_5.6.23-1~dotdeb.1_amd64.deb (–unpack): subprocess new pre-installation script returned error exit status 1Bt when I execute the following line :
mysql –version
mysql Ver 14.14 Distrib 5.6.23, for debian-linux-gnu (x86_64) using EditLine wrapper
This is strange, The MySQL version returned by the server is 5.6.23 !
@Grégoire, @Frank : the latest build should fix your issue. Installing MySQL 5.6 with a custom datadir works fine now :
https://github.com/gplessis/dotdeb-mysql/commit/e6961bc12d73a89ba0928ef3f929fbc485037c57
Had a hard time tracking this issue down…
On start, no matter what open file limits are set I was getting out of resource errors.
Turns out check_for_crashed_tables in /etc/mysql/debian-start was the culprit. I commented it out and now the server starts. Is there an underlying problem I am not aware of?
(addition to previous comment)
Especially talking about php 5.5 as 5.6 is not ready for production without xdebug and memcached without JSON.