MySQL 5.0.36 released to the community - MySQL :: MySQL Server Version Reference :: 5.1.38 Changes in - gigj.com

GIGJ.COM
welcome to my space

gigj.com

HOME

Homepage

Add to favorites

HOME

MySQL 5.0.36 released to the community

MySQL 5.0.36 released to the community
Published by: admin 2010-03-18

http://dev.mysql.com/get/Downloads/MySQL-5.0/mysql-5.0.36.tar.gz/from/pick

Are you already on this, Mr. MacVicar? ;)

Anything new/good since 5.0.33 that we should be aware of?

I noticed the MySQL people removed 5.0.36 from the mysql.com download page. I wonder why they did that.

It's to do with layout of the files, nothing much else. I've never actually checked the other optimisation flags and rely purely on the spec files that MySQL provide.

I'll have a closer look at the scripts when I get some time.

To be honest, I don't know the exact difference.

I believe that the only difference between the two is that the RHEL RPMs unpack files in different locations. It probably also includes an RH-specific init script.

Jason I had to change my spec file a little to include 2 missing manual files not important but just so you know. It was timezone related and I've forgotten the other.

I've got 64bit CentOS disks downloaded so I'll have a go at installing them later tonight, need to pry a disk out of my old machine and pop it in. I don't expect too many problems, if I build anything new I'll post in this thread.

At the moment I've got the Windows builds completed and the i386 RHEL and Generic builds.

Good to know, thanks for the heads up.

Still 5.0.27 as far as binaries go.
Glad I'm moving away from mysql.

I noticed the MySQL people removed 5.0.36 from the mysql.com download page. I wonder why they did that.

Just noticed that as well, good that it's not just my imagination :rolleyes:

I was wondering anyway why there hasn't been an announcement on the mailing list yet. Weird.

I still think it is annoying they aren't providing their own official binaries as frequently as they used to.

Definitely. I think they are even still saying that it's not recommended to build from source. Very funny while they stop providing binaries :p

Does the source RPM actually install MySQL on the system, or does it just extract some stuff? For example, I'm guessing I shouldn't try to build my own binaries on a server that is in use?

I think rpm -i *.src.rpm will only extract the files into /usr/src/redhat/SOURCES. So this can be done on a server in use I guess.

MySQL :: MySQL Server Version Reference :: 5.1.38 Changes in ::
This MySQL 5.0.21 release includes the patches for recently reported security Thanks to Jean-David Maillefer for discovering and reporting this problem to the
http://dev.mysql.com/doc/mysqld-version-reference/en/ch05s01s38.htmlHOME

Once your build has been finished you should find the RPMs somewhere at /usr/src/redhat/RPMS. Those RPMs can actually be installed now.

That would be great. Do you have the resources to do 64-bit binaries too?

I still think it is annoying they aren't providing their own official binaries as frequently as they used to.

Jason: Yes, it could be that, but I think it is what Scott said. (Accidentally releasing it.)

Scott: Are you guys running 5.0.36 on vBulletin.com?

Yeah, that seems to be the case as the source is still on the FTP. In any case, I'm building the RH-style RPMs now.

I noticed the MySQL people removed 5.0.36 from the mysql.com download page. I wonder why they did that.

There was probably a serious bug that leaked though. In any case, once it's back up (or maybe that will be 5.0.37...) I'll create the RH-style RPMs and post them up on my site.

MySQL :: MySQL 5.0 Reference Manual :: C.1.31 Release Notes ::
This is a Service Pack release of the MySQL Enterprise Server 5.0. to the version and features you use, please consider subscribing to MySQL Enterprise (a
http://dev.mysql.com/doc/refman/5.0/en/news-5-0-60sp1.htmlHOME

MySQL 5.0.36 Changelog (http://dev.mysql.com/doc/refman/5.0/en/releasenotes-es-5-0-36.html)

Upgrading to MySQL 5.0.36 on RHEL and CentOS 4 (http://www.jasonlitka.com/2007/03/06/upgrading-to-mysql-5036-rhel-centos/)

Oh, and as with all of the RPMs I build, these are in use on the servers that host all of my forums. :)
now i'm a bit confused.. there shouldn't be any difference between Scott's RHEL4 binaries http://www.vbulletin.com/forum/showpost.php?p=1316958&postcount=5 and yours right ?

I'm not at home just now so I can't build it, when I get home on Monday night I'll build the Linux versions and the Windows on Tuesday. Unless the 5.0.35 builds are out by then.

CPanel doesn't use the RHEL/CentOS binaries, it uses the version from MySQL.com.

EDIT: People using the Plesk control panel will quickly find that their server will stop working properly if they use the mysql.com binaries. There are a few other packages that will break as well.

Download the source rpm file thats there, its the one that ends in .src.rpm

Install the source rpm.

rpm -i <...>.src.rpm

That should extract a spec file into some diretory, from there you can use rpmbuild.

rpmbuild -bb mysql-5.0.36.spec

MySQL :: MySQL 5.0 Reference Manual :: C.1.30 Release Notes ::
This is a Monthly Rapid Update release of the MySQL Enterprise Server 5.0. the last MySQL Enterprise Server release (5.0.60). If you would like to receive more fine
http://dev.mysql.com/doc/refman/5.0/en/news-5-0-62.htmlHOME

if thats the filename, in the end you should get a .rpm for your architecture.

I need to dual boot my machine anyway, just needed a proper reason to take the time.

If you've been using the "generic RPMs" from mysql.com then that is what you should continue to use (MySQL-server-5.0.36-0.glibc23.i386.rpm).

If you were using the "RHEL RPMs" from mysql.com then that is what you should continue to use (MySQL-server-standard-5.0.36-0.rhel4.i386.rpm).

If you were using the RPMs that came with RHEL/CentOS, or the ones from the "centosplus" repo, you should use mine (which, by the way, have been updated to "jason.3" for better compatibility with the default packages).

There's nothing that says that you can't switch from one to the other, but the more you do, the more likely you'll break something.

I could do 64bit binaries if I installed a copy of a 64bit OS on the machine, most likely a CentOS build.

I think they removed the downloads since it was an accident, its an enterprise build and not a community build according to their naming scheme.

I'm about to start the Windows binaries building just now.

Thank you very much, Jason.

My last question:

Is there any benefit to using the "RHEL RPMs" versus the "generic RPMS?" If not, then why do/did they even release "RHEL RPMs?"

Alright, I am a little bit confused about all of the different packages.

We use, and have always used, the following binaries from MySQL.com:

Linux x86 generic RPM (dynamically linked) downloads
MySQL-server-5.0.27-0.glibc23.i386.rpm
MySQL-devel-5.0.27-0.glibc23.i386.rpm
MySQL-client-5.0.27-0.glibc23.i386.rpm
MySQL-shared-5.0.27-0.glibc23.i386.rpm

and

Linux AMD64 / Intel EM64T generic RPM downloads
MySQL-server-5.0.27-0.glibc23.x86_64.rpm
MySQL-devel-5.0.27-0.glibc23.x86_64.rpm
MySQL-client-5.0.27-0.glibc23.x86_64.rpm
MySQL-shared-5.0.27-0.glibc23.x86_64.rpm

So, I see our options are the following:

1. From MySQL.com: Red Hat Enterprise Linux 4 RPM (x86) downloads (i.e. MySQL-server-standard-5.0.27-0.rhel4.i386.rpm)
2. From Scott: MySQL-server-5.0.36-0.glibc23.i386.rpm
3. From Scott: MySQL-server-standard-5.0.36-0.rhel4.i386.rpm
4. From Jason: mysql-server-5.0.36-jason.1.i386.rpm

I'm guessing that Jason's binaries would not be the optimal choice for us, judging by the file name.

I'm just wondering which ones could we use safely, which ones shouldn't we use, and which one is the most recommended.

By the way Scott, you have a broken link here: http://server.macvicar.net/downloads/
The "RHEL 4 / CentOS 4" links to the generic downloads.
Which ones of these can we use, and which would cause problems?

What mix said is correct.

Installing the source rpm just puts the source and the spec file in the folder and rpmbuild just builds the rpm, there is no installation.

thanks for the clearing it up... guess the confusion comes from

CentOS basically same as RHEL4

WHM/CPanel + CentOS upgrades fine using mysql.com rpm binaries

So thought RHEL4 with mysql.com rpm binaries would be the same

Does the source RPM actually install MySQL on the system, or does it just extract some stuff? For example, I'm guessing I shouldn't try to build my own binaries on a server that is in use?

It would be great if you could provide 64-bit too. I hear it's the wave of the future. ;)

Kaj Arn� of MySQL AB mentioned some time ago:

We strive to release MySQL Enterprise Server on a monthly basis. While we don�t have a specific schedule or policy for when MySQL Community Server is released in binary form, I expect the next Community release, 5.0.35, to be available as source and binaries for the same platforms as MySQL Enterprise Server and as the previous MySQL Community Server binary release 5.0.27. Until that point in time, the 5.0.27 binaries will be the ones listed on the normal MySQL 5.0 download pages at dev.mysql.com/downloads/mysql/5.0.html (http://dev.mysql.com/downloads/mysql/5.0.html).
So let's see then ...

Nice :) Thank you.

Any idea if we'll get the x86_64 binaries from mysqlperformanceblog.com too?

I don't want to inconvenience you by asking you to install a 64-bit OS just to make 64-bit binaries for me ;) Is there any way you could just tell me how I could create my own? (We've been using the generic ones.)

Alright, my RH-style RPMs are available. Sorry, but they're i386 only for now because I don't have a spare 64-bit development system (and my VMWare broke about 2 hours ago when I tried to install the 6.0 beta so Vista would work correctly).

Please feel free to build x86_64 packages from the src.rpm though, if you do, let me know and I'll host them if you like.

MySQL 5.0.36 Changelog (http://dev.mysql.com/doc/refman/5.0/en/releasenotes-es-5-0-36.html)

Upgrading to MySQL 5.0.36 on RHEL and CentOS 4 (http://www.jasonlitka.com/2007/03/06/upgrading-to-mysql-5036-rhel-centos/)

Oh, and as with all of the RPMs I build, these are in use on the servers that host all of my forums. :)

Official MySQL RHEL 4 rpms and Red Hat provided rpms have different package names, it makes no sense but someone at MySQL AB / Red Hat decided this was a good idea.

I build my rpms with the official MySQL spec file and I think Jason uses a similar version but aimed specifically at replacing Red Hat provided binaries.

That's exactly correct. Assuming that you install all of the packages, there are no functionality differences between Scott's packages and mine.

However, mine are created with the RH-style layout meaning that all of the package names are in lower-case and that the "MySQL-client" & "MySQL-common" packages have been combined into a single "mysql" package that contains the client and the shared libraries. There are also a few other minor changes, such as renaming the init script from "mysql" to "mysqld" so that applications requiring that script name don't break.

This repackaging tends to make them a bit easier to use to upgrade with when using the default RHEL RPMs or the ones out of the "centosplus" repo because there are a couple packages that will break if you don't have packages & files with the "correct" names.

That said, if you have already upgraded your system with the RPMs from mysql.com and nothing broke, you should probably switch to mine.

I've posted them now to http://server.macvicar.net/downloads/mysql/ all were tested against the mysql suite and worked fine.

Our maintenance window is a Monday morning and I was away today so we won't be doing any upgrades until next week.

Just finishing the windows no install version.