Upgrading to MySQL 5.0.41 on RHEL and CentOS

As happened with 5.0.36 and 5.0.37, it looks like the MySQL 5.0.40 Enterprise-only release has been followed almost immediately by a community version of 5.0.41. As the purpose of my Yum repository is to keep your LAMP stack on the bleeding-edge, I bring you RHEL/CentOS RPMs for "MySQL 5.0.41"!

I don't have an actual changelog for 5.0.40 to 5.0.41 because the only changelogs that are published are for 5.0.36 -> 5.0.38 -> 5.0.40 and 5.0.37 -> 5.0.41 for Enterprise and Community releases respectively. That said, if anyone would like to go through the changelogs for 5.0.38, 5.0.40 and 5.0.41 and find a list of differences, I'd be happy to post up the details with proper credit given.

In any case, no significant spec file changes were required from 5.0.40 to 5.0.41 so this was an easy build (but still time consuming, the regression testing takes forever). The release notes and Source RPM (for those that like to punish themselves) are below.

MySQL 5.0.41 Release Notes

MySQL 5.0.41 Source RPM

12 Responses to “Upgrading to MySQL 5.0.41 on RHEL and CentOS”


  1. 1 Jacek

    Thanks so much!

  2. 2 toni

    Thanks for packaging!

  3. 3 dbembibre

    Compiled and installed. All work ok. Thank you so much Jason :)

  4. 4 dbembibre

    Compiled and installed. All work ok. Thank you so much Jason :)

    Only one question (first time in compile mysql) i change the SPEC to --without-innodb because i only use MYISAM, is this correct ??

  5. 5 Jason

    You could do that, but I personally just disable it in the my.cnf file by adding "skip-innodb". That way, if I change my mind at a later date, all I need to do is to remove that line and it starts working.

  6. 6 Jacek

    MySQL 5.0.42 has just been released.
    ftp://ftp.mysql.com/pub/mysql/src/mysql-5.0.42.tar.gz
    Thanks in advance. All the best, Jacek

  7. 7 Jason

    @Jacek

    I'll take care of that tomorrow. Thanks for the notice.

  8. 8 Brent Wilson

    Hi,

    I have installed mysqlclient14 and mysqlclient14-devel but I still get the dependency errors.

    Installed packages:

    # yum list *mysql*
    Setting up repositories
    Reading repository metadata in from local files
    Installed Packages
    MySQL-python.i386 1.2.1_p2-1.el4.1 installed
    libdbi-dbd-mysql.i386 0.6.5-10.RHEL4.1 installed
    mysql.i386 4.1.20-2.RHEL4.1 installed
    mysql-devel.i386 4.1.20-2.RHEL4.1 installed
    mysqlclient10.i386 3.23.58-4.RHEL4.1 installed
    mysqlclient14.i386 4.1.14-4.2.1.jason.1 installed
    mysqlclient14-devel.i386 4.1.14-4.2.1.jason.1 installed
    perl-DBD-MySQL.i386 2.9004-3.1.centos4 installed

    Yet I get this when running yum update:

    # yum update
    Setting up Update Process
    Setting up repositories
    Reading repository metadata in from local files
    Resolving Dependencies
    --> Populating transaction set with selected packages. Please wait.
    ---> Package mod_ssl.i386 1:2.2.4-jason.4 set to be updated
    ---> Package php-pear.noarch 1:1.5.0-3.jason.1 set to be updated
    ---> Package pcre.i386 0:7.0-2.jason.1 set to be updated
    ---> Package httpd-manual.i386 0:2.2.4-jason.4 set to be updated
    ---> Package mysql.i386 0:5.0.41-jason.1 set to be updated
    ---> Package apr.i386 0:1.2.8-4.jason.1 set to be updated
    ---> Package php-ldap.i386 0:5.2.3-jason.1 set to be updated
    ---> Package php.i386 0:5.2.3-jason.1 set to be updated
    ---> Package mysqlclient10.i386 0:3.23.58-9.2.1.jason.1 set to be updated
    ---> Package mod_python.i386 0:3.2.8-3.1.jason.1 set to be updated
    ---> Package mod_perl.i386 0:2.0.2-6.1.jason.1 set to be updated
    ---> Package httpd.i386 0:2.2.4-jason.4 set to be updated
    ---> Package apr-util.i386 0:1.2.8-4.jason.1 set to be updated
    ---> Package mysql-devel.i386 0:5.0.41-jason.1 set to be updated
    --> Running transaction check
    --> Processing Dependency: php-common = 5.2.3-jason.1 for package: php
    --> Processing Dependency: perl(BSD::Resource) for package: mod_perl
    --> Processing Dependency: php-common = 5.2.3-jason.1 for package: php-ldap
    --> Processing Dependency: libmysqlclient.so.14(libmysqlclient_14) for package: dovecot
    --> Processing Dependency: php-cli for package: php-pear
    --> Processing Dependency: php-cli = 5.2.3-jason.1 for package: php
    --> Processing Dependency: libmysqlclient_r.so.14(libmysqlclient_14) for package: MySQL-python
    --> Restarting Dependency Resolution with new changes.
    --> Populating transaction set with selected packages. Please wait.
    ---> Package perl-BSD-Resource.i386 0:1.28-1.jason.1 set to be updated
    ---> Package php-common.i386 0:5.2.3-jason.1 set to be updated
    ---> Package php-cli.i386 0:5.2.3-jason.1 set to be updated
    --> Running transaction check
    --> Processing Dependency: libmysqlclient.so.14(libmysqlclient_14) for package: dovecot
    --> Processing Dependency: libmysqlclient_r.so.14(libmysqlclient_14) for package: MySQL-python
    --> Finished Dependency Resolution
    Error: Missing Dependency: libmysqlclient.so.14(libmysqlclient_14) is needed by package dovecot
    Error: Missing Dependency: libmysqlclient_r.so.14(libmysqlclient_14) is needed by package MySQL-python

    Any ideas?

  9. 9 thomas

    Hi Jason
    I can't access your public GPG key.

  10. 10 Jason

    Works for me, are you sure that you typed the URL correctly?

    http://www.jasonlitka.com/media/RPM-GPG-KEY-jlitka

  11. 11 Jetman

    Brent Wilson, before updating MySQL from Jason's repo, you must update it from CentOSPlus repo, i.e.:
    # remove mysqlclient14: yum remove mysqlclient14*
    # then:
    yum --disablerepo=utterramblings --enablerepo=centosplus update mysql*
    yum update mysql*

  12. 12 Jason

    @Jetman,

    That is not true. I roll out systems all the time that go from vanilla directly to my repository.

    @Brent,

    Did you ever get that working? If not, contact me via the form on my About page; I'm interested in taking a look at your system (if you'll let me).

Leave a Reply

Note: This post is over a year old. You may want to check later in this blog to see if there is new information relevant to your comment.

By submitting a comment here you grant this site a perpetual license to reproduce your words and name/web site in attribution. Use of a non-personal web site or blog in the "Web Site" field and/or leaving a comment that is off-topic or inappropriate may result in the comment being edited or removed at the discretion of the site owner.






Close
Powered by ShareThis