Upgrading to MySQL 5.0.46 on RHEL and CentOS

August 9, 2007 by · 4 Comments 

MySQL 5.0.46 is the newest release available to MySQL Enterprise customers. As with prior versions I've built my customary "Red Hat"-style RPMs. The source code for this release has since been removed from the main MySQL FTP site (don't worry, it wasn't pulled due to bugs, more on this in a later article) but I grabbed it before it disappeared.

As with all of my releases, all you’ll need to do is run a ‘yum update’ if you’re a user of my repository. Those wishing to compile from source can do so with the src.rpm at the bottom of this post but unless you’ve got a good reason, I wouldn’t recommend it because it takes forever and a day for the testing to run to completion and it will fail near the end if you’re one of those people that likes to compile as ‘root’.

MySQL 5.0.46 Release Notes

Update (9/24/2009): Packages deleted, use the yum repository instead.

Comments

4 Responses to “Upgrading to MySQL 5.0.46 on RHEL and CentOS”
  1. Greetings. I followed the instructions of the repositoy but when I try to rum

    yum update

    I just get:
    Setting up Update Process
    Setting up repositories
    Reading repository metadata in from local files
    Excluding Packages in global exclude list
    Finished
    No Packages marked for Update/Obsoletion

    And nothing more. The mysql is not updated :|

    Ideas?

  2. Jason says:

    Well, there are three main possibilities.

    First, you don't actually have my repo enabled. This could be caused by pasting the data on the "Yum Repository" page into the wrong location, or modifying it so that you've set "enabled" to "0".

    Second, you're using the "protectbase" or "priorities" plugins for yum and have set the "base", "updates", and/or "centosplus" repos to a higher priority than "utterramblings".

    Finally, you may not have installed MySQL via RPMs. Try running "rpm -qa | grep mysql" and seeing what you get. If you don't get at least 2 or 3 packages that start with "mysql" then you either don't have MySQL installed at all or you installed it via source (which I believe is what CPanel does). If you don't have it installed at all then you may want to start with a "yum install mysql mysql-server". If you've installed from source then I would not recommend that you use the packages I've created.

  3. Allan Wang says:

    Hmm, I thought I posted already, but:

    I'm trying to upgrade to mysql-5.0.48-jason.1 on x86_64 from 5.0.46-jason.1, however I'm getting the following messages when I run yum update:

    file /usr/share/info/mysql.info.gz from install of mysql-5.0.48-jason.1 conflicts with file from package mysql-5.0.46-jason.1
    file /usr/share/man/man1/mysql.1.gz from install of mysql-5.0.48-jason.1 conflicts with file from package mysql-5.0.46-jason.1
    file /usr/share/man/man1/mysqlaccess.1.gz from install of mysql-5.0.48-jason.1 conflicts with file from package mysql-5.0.46-jason.1
    file /usr/share/man/man1/mysqladmin.1.gz from install of mysql-5.0.48-jason.1 conflicts with file from package mysql-5.0.46-jason.1
    ...

    How can I resolve this without removing all deps of mysql and reinstalling? I already had to do that to upgrade to 5.0.46 in the first place.

  4. Jason says:

    @Allan,

    Hmmm... That's a new one. I've upgraded 4 production MySQL servers (plus my 4 development systems) and more than 20 web servers and none have had that problem. Are you using the EL4 or EL5 packages?

    The fact that you had to "remove all deps of mysql and reinstall" in order to use my 5.0.46 packages concerns me as I have never had that issue. In general, installing packages from my repository is as simple as adding the yum repo to the system and then typing "yum update".

    Finally, please post regarding this issue over in the comments for the 5.0.48 post as it really has more to do with 5.0.48 than 5.0.46.

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.