About 30 minutes ago I moved the yum repository files from the "media" folder on this domain to a dedicated subdomain of http://yum.jasonlitka.com. This is simply a housekeeping measure. It's easier to keep track of those files when they're on a separate subdomain and it gives me the flexibility to easily spin them off to a separate server should the bandwidth requirements get out of control. On that, a big thank you to Linode (referral link) for recently increasing your bandwidth limits by 10x and to Cloudflare for absorbing close to 50% of my traffic for the grand total of $0.00/month.
This shouldn't have any impact on running servers using the repository since the old location has a 301 redirect to the new one. If you do hit a problem try a "yum clean all". If that doesn't work then let me know.
On a semi-related note, I migrated servers about a month back and apparently didn't configure outbound email... If you tried to use the contact form since the beginning of February then I didn't get your message. Sorry.
httpd 2.2.22 is now live in the public repos. I didn't get a lot of sleep last week due to a ShoreTel deployment so I decided not to push it live on Friday as originally planned.
httpd 2.2.22 will be posted to my testing repo early next week with a public push at the end of the week. I've gotten swamped with a ShoreTel deployment this week and while I've built the packages for httpd 2.2.22 I haven't actually spent any time testing them.
I've just made httpd 2.2.21 available in my repos. No other packages were updated or rebuilt so with any luck this will be a smooth upgrade for everyone.
For those that don't know, aside from a few bug fixes here and there, httpd 2.2.21 fixes another DoS bug (this time in mod_proxy_ajp) and re-fixes the DoS bug that was fixed in 2.2.20.
Apache's httpd is now 2.2.20 to fix that bit of recent DoS nastyness, PHP is up to 5.2.17, MySQL up to 5.1.58, XCache has been updated to the 1.3.2 release, and a few included deps have been bumped as well.
One thing I've been considering lately is the upgrade to PHP 5.3. I was saying for a long time that I was not going to force people to upgrade because of the sheer volume of systems with outdated ioncube and zend loaders that would break (more zend than ioncube), but to be honest, you've all had a long time to remedy that issue, and with the EOL on PHP 5.2 (5.2.16 was supposed to be the last release, they made a 5.2.17 to cover an issue, who knows how many more times they'll do that), I think it's time to upgrade the repo.
I've personally been running PHP 5.3 on Amazon's EC2 for about 6 months now and have not had a single issue. I can't say none of you will, and you should probably all start reading the PHP 5.3 migration guide, particularly the sections on backwards incompatible changes, removed extensions, and deprecated functions, but I'll help where I can when the day comes to push out the version bump. That's not to say it will be tomorrow, for one, I'm leaving town tomorrow on business, and it won't be next week either, but at some point over the next month or two, I'll be pushing PHP 5.3 updates (with a warning on the site first, check back once in a while or subscribe to the RSS feed).
Oh, and as a reminder to all, updates are available early to those that use my "Testing" repos. These are packages I consider production-quality enough to try on my live systems and typically once a package is pushed to that point I don't rebuild again. I just wait a week and copy them to the GA repos.
httpd 2.2.17, mysql 5.1.52, php 5.2.16, XCache 1.3.1, and APC 3.1.6 (which is FINALLY marked as stable) updates are all published to the regular repo, "yum update" for everyone!
More here tomorrow, I'm tired...
EDIT: Or not, I'm a man of few words.
If you haven't noticed yet, packages for MySQL 5.1 have been moved to the public repos. I whipped up updates for PHP 5.2.14 and httpd 2.2.16 as well. For those that have programs compiled against the mysql 5.0.x client libraries, a mysqlclient15 package has been added.
As I mentioned in an earlier post, there are some potential issues you might run into when upgrading from MySQL 4.1 or 5.0. It is absolutely critical that you run 'mysql_upgrade' after installing the update. Failure to do so will cause serious weirdness with your databases.
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:
- 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.
- 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
Enough said. You know what you've got to do. Issues in the comments as usual. If something goes wrong and you've got a large bit of data you'd like to send me, please send it via the comment form on the About page and don't break the site layout by posting it all as a comment.
Also, it might pay to check out my Twitter feed over on the right side-bar. If you don't you might miss things like updates to this site, my neighbor's house catching on fire this past Saturday and me complaining about various things that annoy me.
According to the MySQL web site, 5.0.86 has been available since September 9th. I honestly have no idea why, just last week, I built packages for 5.0.84 rather than this newest version. Anyway, the repos have been updated with packages for 5.0.86 and I made a small change so I believe these should also update correctly on systems that have a "mysql-libs" package installed without forcing you to first remove your existing install.
Update #1 (2009/09/28): It's been brought to my attention that these packages will overwrite your old my.cnf. This will be fixed in the next release, but for now, make a backup of your config before updating.
Update #2 (2009/09/28): The reason for the config glitch is because I put it into two packages... New RPMs coming later today; MySQL takes forever to build...
Update #3 (2009/09/28): Newer packages are up, ignore previous updates.