MySQL 5.1 coming to yum repo, info & warnings within…

August 13, 2010 by · 15 Comments 

My original thoughts were to roll out packages for MySQL 5.1 and PHP 5.3 at the same time. Given the issues with Zend getting loaders for 5.3 out the door, and the complications with developers needing a newer version of Zend Guard and having to recompile everything in order for it to work with those loaders, I'm now reconsidering that plan.

The current plan is to get packages for 5.1 out the door before the end of August. That gives me a couple weeks to get them working correctly and you plenty of time to decide whether or not you want to continue using my repository.

There are some breaking changes between MySQL 5.0 and 5.1.  The link at the bottom of this post covers them all, but two critical ones are worth mentioning here:

  1. Upgrading from MySQL 4.1 to 5.1 is not possible so users on RHEL/CentOS 4 who have NOT already upgraded to 5.0.x using my repo or some other repo will NOT be able to do an in-place upgrade to 5.1.  They will need to dump their databases under 4.1, uninstall 4.1, remove the binary data files, install 5.1, and then restore their backups.
  2. When I release packages for MySQL 5.1 there will NOT be support for MySQL Cluster.  I don't use it, no one I know uses it, and now that it's a separate product, it's way too much hassle for me to keep updated.  If you use MySQL Cluster you will need to remove my packages from your system and move to the official MySQL Cluster Community Edition packages on mysql.com

Info on Zend issues: Zend Optimizer for PHP 5.3
Info on MySQL 5.0 to 5.1 upgrades: Upgrading from MySQL 5.0 to 5.1

Comments

15 Responses to “MySQL 5.1 coming to yum repo, info & warnings within…”
  1. complex web development says:

    Waiting for the MySQL 5.1. Thanks!

  2. Igal says:

    first of all thanks for this repo, you doing a great job, I'm a web developer (freelance) and it keeps my CentOS server on the RACKSPACE Cloud always in a good shape.

    i understand it got some problems with updating to 5.3 because of Zend. that sucks :) because 5.3 is such a huge improvement over 5.2 i can't even start describe it on words.

    when do you think 5.3 will be available on your repo? can't wait start using it on my server, i'm deploying a lot of Kohana3 applications there, and can't wait to use 5.3 in my production env.

  3. Ken says:

    My understanding is that the Zend issue is a near complete stopper for PHP 5.3 upgrades. I did a grep for zend on my server, and there are a zillion files (is this a reasonable way to identify files that are Zend encoded/encrypted/processed?)

  4. Jason says:

    I finished the builds on Friday and stuck them on some of my servers for a live test. Assuming all goes well, i'll make them public on Monday.

  5. Jason says:

    Honestly, I don't know. I have some internal builds but the issues with Zend scare me. I really don't want to be responsible for breaking servers. I've got to put in some dep checking to make sure that it only installs if you've got a newer version of Zend installed.

  6. Igal says:

    now i know there's a good reason I'm not using Zend =)

  7. Jason says:

    I ran into a problem with one CentOS 4 OpenVZ container where php-mysql was missing after the update. I think that system had a corrupt RPM database to start with, so I don't actually believe the new packages caused the failure, but I'm going to hold on to these for another day or two to see if I can replicate the issue.

    For those that are impatient, there are now instructions on the "Yum Repository" page for enabling my "Testing" repos. With the exception of the week prior to the release of new updates, the testing and production repos are typically sync'd up. In my case, "testing" refers to something I consider close enough to production-quality to test on my own live servers. I do not post the early builds that I run on throw-away VMs.

  8. londoh says:

    Just a quick note to say thanks.

    I u/g'ed php > 5.2.14 & mysql from 5.0.77 to 5.1.50 on centos 5.5 virtualmin. no probs.

    It would saved a couple minutes panic if I'd actually bothered to read the link you gave re upgrading mysql from 5.0 to 5.1 -- there were a few issues with some old tables but mysql_upgrade did the trick.
    self::RTFM(First_Not_Last);

  9. Jeff says:

    @ Jason, you posted... I've got to put in some dep checking to make sure that it only installs if you've got a newer version of Zend installed.

    This is from my php_nfo, would it meet the criteria? It is from your latest 5.2.14 build with ioncube and xcache installed:

    This program makes use of the Zend Scripting Language Engine:
    Zend Engine v2.2.0, Copyright (c) 1998-2010 Zend Technologies
    with the ionCube PHP Loader v3.3.5, Copyright (c) 2002-2009, by ionCube Ltd., and
    with XCache v1.3.0, Copyright (c) 2005-2009, by mOo

    Would that work natively with your pending 5.3 build?

  10. Jason says:

    @Jeff,

    Different Zend. That note was about the Zend Optimizer. You'll be fine on that front. What won't be fine is your static loading of ionCube which suffers from a similar problem but a much easier fix. Once I make PHP 5.3 packages (for which there will be fair warning, just as with MySQL 5.1, but no current ETA) you'll just need to download and reinstall the ioncube loaders and everything should start working again.

  11. Jeff says:

    Great, thanks. I actually updated that today after I made the post above, so I know how/where to drop the 5.3 file and update the .ini file. Now running ionCube PHP Loader v3.3.20 (for 5.2)

  12. Igal says:

    thanks for MySQL 5.1, updated on CentOS 5.5, no probs also!

  13. william says:

    Where can I find the *.repo to downloads ?

  14. Rachel says:

    Just like William, I am also interested to know where to find the repo ?

    rachel

  15. juries says:

    I know this had been a long time post and its been widely used. But like others I want know the repo downloads? Thank you much!

Speak Your Mind

Tell us what you're thinking...
and oh, if you want a pic to show with your comment, go get a gravatar!

 

Note: This post is over 5 years 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.