MySQL 5.1.41 is available for Debian “Lenny” and “Etch”

MySQL 5.1.41 is now available on Dotdeb for Debian 5.0 “Lenny” / Debian 4.0 “Etch” in amd64/i386 flavours.

This maintenance release fixes a lot of bugs (please read the Changelog for more details). Please note the the InnoDB plugin has been updated to 1.0.5.

28 replies on “MySQL 5.1.41 is available for Debian “Lenny” and “Etch””

I am using MySQL 5.0.51a-24+lenny2 and want to upgrade to “MySQL 5.1.41”.

I tried “apt-get upgrade” but I get this error:

~# apt-get upgrade
Reading package lists… Done
Building dependency tree
Reading state information… Done
The following packages have been kept back:
mysql-client mysql-server
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.

How can I upgrade MySQL?

@kevin : try to use a tool such as dselect or aptitude to know why these two meta-packages (they’re empty, teh real packages are mysql-client-5.1 and mysql-server-5.1) are kept back.
Perhaps they’re “frozen” in your package selection.


I updated to the new version. But I get the following error:
ERROR: object ‘/usr/lib/’ from LD_PRELOAD cannot be preloaded: ignored.

So I commented the following line in /etc/init.d/mysql:
export LD_PRELOAD=”/usr/lib/″

It’s for the Google Perftools. Is there a way to use the Perftools with the new MySQL version?


I tried the upgrade and it seemed to work fine, however phpinfo() is reporting:

Client API version – 5.0.51a

I had upgraded PHP separately first before upgrading MySQL…any way to fix this?

i get also the error:
cp: cannot overwrite directory `/var/lib/mysql-upgrade/’ with non-directory

can anybody help?

@WebGoddess : phpinfo() shows PHP client-side pieces of information. PHP is built against the old libmysqlclient15off (5.0.51a) to avoid Apache-related issues and segfaults.

This has nothing to deal with the MySQL server infos. There’s no doubt that your server has been upgraded to 5.1.41 (“mysqladmin version” will confirm that).

FYI, 5.0.51a-linked clients interacts with a 5.1.41 server without any issue. PHPMyAdmin could show some warnings. Just ignore them.

no. Datadir in /etc/mysql/my.cnf is /srv/mysql and /var/lib/mysql is a symlink to /srv/mysql.
But previous versions works without problems.

@Shadow-Dragon :
* take a look at the DATADIR variable in /var/lib/dpkg/info/mysql-server-5.1.preinst and try to set it to your config before configuring the mysql-server-5.1
* you can also try to “export DATADIR=/srv/mysql” before launching the upgrade process
* at last, you could “mount –bind /srv/mysql /var/lib/mysql” to simulate a standard Debian/MySQL config.

@Guillaume – thanks so much for clarifying this for me, yes I do have 5.1.41 installed I just was confused about the PHP Client API mis-match.

For some reason when I upgraded to 5.1.41 mysql wouldn’t start; I had to revert to the distro my.cnf file to get it to work, then re-add the config options after finishing the upgrade.

with 5.0 support officially ending at the end of the year, how will this affect debian based on the fact that it currently runs 5.0.51 which is what you base your php lib on?

will you update your lib for for the new mysql lib so that the php5-mysql lib will now match the correct mysql server version?

@Anthony : MySQL AB stops the active (commercial) support on the 5.0 branch, but the community support (especially Debian’s one) does not stop. Nothing will change on the Debian/Dotdeb side.

About “matching the correct version”, as said in many comments on this blog, it’s not a big deal having a delta between the client and the server. For example, MySQL native driver of PHP 5.3 won’t match the MySQL server but will work great with any MySQL server.
Tell me if you encounter issue, I’ll solve them.

thanks very much for the clarification, it somewhat eases my mind, i have not had any issues with the dotdeb packages so far except in install but thats a seperate topic regarding different config files and my insistance to retain the previous config files rather than merge tweaks into a new file

RE: Debian 5.03 Lenny

I seem to have an odd issue installing mysql-server-5.1. Both apt-get and dpkg hang forever while unpacking the .deb file. The .deb unpacks fine using ar. It may not be a dotdeb specific issue since mysql-5.1 is available in lenny backports and the same thing happens when trying to install from there as well.

Relevant output:

~ $ aptitude install mysql-server-5.1
Reading package lists… Done
Building dependency tree
Reading state information… Done
Reading extended state information
Initializing package states… Done
Writing extended state information… Done
Reading task descriptions… Done
The following NEW packages will be installed:
mysql-client-5.1{a} mysql-server-5.1
The following packages will be REMOVED:
libterm-readkey-perl{u} mysql-client{a} mysql-client-5.0{a} mysql-server{a} mysql-server-5.0{u}
0 packages upgraded, 2 newly installed, 5 to remove and 2 not upgraded.
Need to get 19.8MB of archives. After unpacking 55.9MB will be freed.
Do you want to continue? [Y/n/?]
Writing extended state information… Done
Get:1 lenny-backports/main mysql-client-5.1 5.1.41-3~bpo50+1 [8254kB]
Get:2 lenny-backports/main mysql-server-5.1 5.1.41-3~bpo50+1 [11.6MB]
Fetched 19.8MB in 10s (1862kB/s)
Preconfiguring packages …
(Reading database … 151149 files and directories currently installed.)
Removing libterm-readkey-perl …
Removing mysql-client …
Removing mysql-server …
Removing mysql-server-5.0 …
Stopping MySQL database server: mysqld.
Removing mysql-client-5.0 …
Processing triggers for man-db …
Selecting previously deselected package mysql-client-5.1.
(Reading database … 149153 files and directories currently installed.)
Unpacking mysql-client-5.1 (from …/mysql-client-5.1_5.1.41-3~bpo50+1_i386.deb) …
Unpacking mysql-server-5.1 (from …/mysql-server-5.1_5.1.41-3~bpo50+1_i386.deb) …

NOTE the two attempts to unpack the archive simultaneously.

The deb installed fine on my other Debian 5.03 (PIII coppermine) server.
This is the only package that hangs while installing.
The updated libmysql installs fine.
The mysql-client-5.1 installs fine.

Any ideas?

The package never installed so there is no /etc/init.d/mysql. The only notice is a user abort notice when I abort the installation.

DPKG hangs running the pre-install script(s) so I think I have a messed up system somewhere.

I was hoping someone else had this issue and some advice but I don’t think it’s your package.


I hate to break it to you, Siggma, but I do have the same issue with mysql-server-5.0_5.0.67-0ubuntu6_i386.deb on Ubuntu.

It’s almost definitely not the package; it’s something in our systems.

I just upgraded from Lenny’s 5.0 to dotdeb’s 5.1 and MySQL won’t start now. syslog doesn’t show any reason for it. The init.d script just sort of hangs while trying to start the server. Help!?

@Norio : try to use the maintainer’s /etc/mysql/my.cnf while upgrading or comment “skip-bdb” in your existing configuration file.
Then check that no mysql_safe or mysqld processes are running and launch “/etc/init.d/mysql start”.
If errors occur, they should be reported in /var/log/syslog. If not, edit /etc/init.d/mysql and put some breakpoints in it to see where the script hangs.

I can confirm that it’s a good idea to use the maintainer’s my.cnf.

Took a whole lot of futzing to get apt to offer to replace my.cnf that second time. No problem from there.

Hi Guillaume,

“aptitude search mysql-server” on lenny shows only 5.0. Yes, your sources are into sources.lst, and get a hit on aptitude update.

what do i wrong?


Comments are closed.