35 Responses to “MySQL 5.1.32 is now available”

  1. Marcos Neves

    I am trying to install it with:
    apt-get -y install mysql-server-5.1
    but I get this error:

    The following packages have unmet dependencies:
    mysql-server-5.1: Depends: mysql-client-5.1 (>= 5.1.32-0.dotdeb.1) but it is not going to be installed
    Depends: libc6 (>= 2.7-1) but 2.3.6.ds1-13etch9+b1 is to be installed
    Depends: libmysqlclient16 (>= 5.1.21-1) but it is not going to be installed
    E: Broken packages

  2. Anton

    а вот у меня при обновлении вылетает такая ошибка:

    dpkg: не удалось обработать параметр /var/cache/apt/archives/mysql-server-5.1_5.1.32-0.dotdeb.1_i386.deb (–unpack):
    попытка перезаписать /usr/sbin/mysqld, который уже имеется в пакете mysql-server-core-5.0
    dpkg-deb: подпроцесс paste убит по сигналу (Broken pipe)
    При обработке следующих пакетов произошли ошибки:
    /var/cache/apt/archives/mysql-server-5.1_5.1.32-0.dotdeb.1_i386.deb
    E: Sub-process /usr/bin/dpkg returned an error code (1)

    Ubuntu jaunty (9.04)

  3. Guillaume Plessis

    @Anton : please write in english.

    About your problem, keep in mind that Dotdeb is made for Debian Etch or Debian Lenny. Ubuntu should be compatible, but full support is not garanted. It seems that mysql-server-5.1 conflicts with mysql-server-core-5.0. Remove this last package and all should work fine.

  4. Anton

    >please write in english.
    sorry, my english is very bad…

    >Remove this last package
    tnx, all work!!!

  5. Anton

    …but!
    mysql-server-core-5.0 is require for KDE
    and now kde is not working… only gnome =((

  6. Guillaume Plessis

    This is also a tipical case where Dotdeb does not work for Ubuntu. Sorry. It is strange that Ubuntu implements packages’ names that don’t fit to the standard debian naming rules.

  7. Polk

    I have Mysql5.0 and want to UPGRADE to Mysql5.1.32. Debian Lenny.

    I tried once and got:
    /var/cache/apt/archives/mysql-server-5.1_5.1.32-0.dotdeb.1_i386.deb
    E: Sub-process /usr/bin/dpkg returned an error code (1)
    and completely messed up mysql server. the only way I could fix it is to remove the mysql and install it again v5.0.

    now when I do apt-get upgrade, I get this:
    The following packages have been kept back:
    mysql-client mysql-server
    0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.

    obviously, because there is newer 5.1 is available, but I’m now afraid to do the upgrade because don’t want to brake this server. Is there any proper way to UPGRADE?

  8. Polk

    I’m on Debian Lenny. My sources.list:

    deb http://ftp.us.debian.org/debian/ lenny main
    deb-src http://ftp.us.debian.org/debian/ lenny main

    deb http://security.debian.org/ lenny/updates main
    deb-src http://security.debian.org/ lenny/updates main

    deb http://volatile.debian.org/debian-volatile lenny/volatile main
    deb-src http://volatile.debian.org/debian-volatile lenny/volatile main

    deb http://packages.dotdeb.org stable all
    deb-src http://packages.dotdeb.org stable all

    Thanks for your reply. Hope you can help.

  9. Guillaume Plessis

    @Polk : I had no problem upgrading from 5.0 to 5.1. Please note that each time, I install the new my.cnf file. I backport my changes after the upgrade.

    If this is dependency problem, try to use such a tool as dselect or aptitude to fine-tune the installable and removable packages.

  10. Karim

    Hi, great site! I’ve added your packages to my sources list and installed php529 and mysql 5132, however in phpmyadmin i now get this error:
    Your PHP MySQL library version 5.0.51a differs from your MySQL server version 5.1.32. This may cause unpredictable behavior.

    Any idea?

  11. Guillaume Plessis

    @Karin : That’s just a warning and there is no way to fix this without causing segfaults in the LAMP stack. Anyway, there’s no reason for incompatibilities between 5.0 libraries and a 5.1 server in the PHPMyAdmin case (let me know if I’m wrong). It should be fixed in PHP 5.3 with the inclusion of the MySQL native driver.

    Try to comment this warning in PHPMyAdmin (main.php).

  12. Karim

    Guillaume: Alright i’ll keep my eyes open for strange things, so far i’ve commented the warning and its gone.
    Thanks for your fast response 🙂

  13. Peter Brodersen

    Hi,

    Is the command line client for 5.1 compiled without readline support?

    I can’t use Ctrl-R for backwards search or Ctrl-W to delete a single word – instead the whole line is deleted. It doesn’t matter whether TERM is xterm, linux or screen.

    I use 5.1.32-0.dotdeb.1-log.

    – Peter

  14. greatman

    Hi!

    When i try to update my system, i got this:

    The following packages have been kept back :
    courier-authlib courier-authlib-userdb libmysqlclient-dev libmysqlclient15-dev libmysqlclient16 mysql-client-5.1 mysql-server-5.1 php-pear php5-cgi php5-cli php5-common php5-curl php5-dev php5-gd php5-http php5-imagick php5-imap php5-mcrypt php5-mhash php5-mysql php5-sqlite
    0 paquets mis à jour, 0 nouvellement installés, 0 à enlever et 21 not updated.

    Thanks for help
    Greatman

  15. Jean-Michel

    Hi Guillaume,

    mysql can’t restart after upgrade to mysql 5.1.32 from 5.0.x

    > apt-get install mysql-server-5.1
    […]
    Paramétrage de mysql-server-5.1 (5.1.32-0.dotdeb.0) …
    Installation de la nouvelle version du fichier de configuration /etc/init.d/mysql …
    Stopping MySQL database server: mysqld.
    Starting MySQL database server: mysqld . . . . . . . . . . . . . . failed!
    invoke-rc.d: initscript mysql, action “start” failed.
    dpkg : erreur de traitement de mysql-server-5.1 (–configure) :
    le sous-processus post-installation script a retourné une erreur de sortie d’état 1
    Des erreurs ont été rencontrées pendant l’exécution :
    mysql-server-5.1
    E: Sub-process /usr/bin/dpkg returned an error code (1)
    zsh: exit 100 apt-get install mysql-server-5.1
    >
    —–
    Any subsequent try to start mysql has failed.

    The config files my.conf and debian.conf have not been changed by the install process.
    Maybe some params are not compatible with mysql 5.1 ?

    Any idea ?

  16. Guillaume Plessis

    @Jean-Michel : take a look at /var/log/syslog, MySQL will report there any error preventing it to start.

    @Greatman : use aptitutde or dselect to fine-tune the to-be-installed/removed/kept packages and to have a better idea of the dependencies. It should solve your problem.

  17. Jean-Michel

    Thanks !
    I’ve found this in the logs :
    /usr/sbin/mysqld: unknown option ‘–skip-bdb’

    How can I fix that ?
    TIA

  18. sunfire

    Hi,
    i got a problem when i create a database with “-”

    example: data-base –> data@002dbase

    How can i fix it?

    Thanks for feedback.

  19. sunfire

    Hi,
    thanks for the link.
    It’s normal storing of special characters in mysql 5.1 .

  20. Sébastien B.

    After the upgrade to this version, I got this replication’s error :

    > SHOW SLAVE STATUS;

    Error ‘You cannot ‘ALTER’ a log table if logging is enabled’ on query. Default database: ‘mysql’. Query: ‘ALTER TABLE general_log MODIFY COLUMN server_id INTEGER UNSIGNED NOT NULL’

    Any idea to fix ?

  21. Sébastien B.

    @Guilllaume,
    Thanks, I did on both master and slave:

    STOP SLAVE;
    SET SQL_LOG_BIN=0;
    SET GLOBAL general_log = ‘OFF’;
    USE mysql;
    ALTER TABLE general_log MODIFY COLUMN server_id INTEGER UNSIGNED NOT NULL;
    SET GLOBAL general_log = ‘ON’;
    SET SQL_LOG_BIN=1;
    START SLAVE;

    But got always the same error.
    Is it a good idead to re-run the upgrade script ? Where is it located ?

  22. Sébastien B.

    I re-run /usr/bin/mysql_upgrade –force script and got these errors :
    mysql.general_log
    Error : You can’t use locks with log tables.
    status : OK
    mysql.slow_log
    Error : You can’t use locks with log tables.
    status : OK

    I’m going to have a look for the second solution.

  23. Michael Stubblefield

    For everyone having problems with the upgrade:

    If you keep your my.cnf file, you will get errors, causing an incomplete installation and possibly issues downgrading to mysql 5.0

    To avoid this, backup your my.cnf file and overwrite it, then just go through and redo any changes you had made before.

    If you have this problem and now your db is hosed and can’t revert to 5.0, and can’t install 5.1:

    go into your my.cnf file. comment out the line (mentioned above):

    skip-bdb

    do this and retry install. Should work now.

  24. Chris Trahey

    I am having problems with the password() function… it is possible this is by design, but I couldn’t find documentation.
    It is returning the same value as old_password() (16 byte). It is as if password() is aliased in this (dotdeb) release.

    I have another machine running 5.1.33 community, and the issue is not present.

    Is this something in the config I can change?
    Thanks!

  25. Guillaume Plessis

    @Chris Trahey : Please check that the “old-passwords” option is unset or set to 0 in your my.cnf (/etc/mysql/my.cnf, ~/.my.cnf)

  26. Chris Trahey

    Thanks, Guillaume.
    Sure thing, it’s in the .cnf file.
    Is that default from the MySQL Distro, or a dotdeb thing?

  27. Guillaume Plessis

    That’s an old Debian (therefore Dotdeb) compatibility setting. It will disapear in the next mysql-common package (upcoming 5.1.36?).