Just a quick note, I did a respin of MySQL 5.0.54 with a patch for bug #33814. This wasn't really necessary since my binaries use OpenSSL rather than yaSSL (and the vulnerability is with the bundled yaSSL) but I know that quite a few people download my source RPMs and rebuild them, so I updated it just in case.
Since the source package used is still 5.0.54 and I am manually patching during the build process I have kept the version number at "5.0.54" and just incremented the release to "jason.2". Rest assured though, it is equivalent to 5.0.54a.
I've been a bit lax over the past week or so, but there's been a few packages I've updated since the last post. On January 8th I updated XCache to 1.2.2. On January 15th I updated mod_security to eliminate that config bug that affected some 32-bit users. Finally, yesterday, January 22nd, I updated Apache's httpd to 2.2.8.
On that last one, there were two versions of httpd posted yesterday: "jason.2" and "jason.3". If you've got "jason.2" then I'd suggest you run another "yum update" as I decided to make a last minute change to stomp out a possible initscript issue that may have affected some users. If you get a couple warning messages during the upgrade you can ignore them; they aren't important and they won't come back once you are on "jason.3".
It's been a while (3 months) since I've posted a MySQL update. The Enterprise release of 5.0.50, the Community release of 5.0.51, and the Enterprise release of 5.0.52 all refused to pass the testing at the end of the build process. Thankfully though, they got that worked out (MySQL bug 33050), so I'm now making binaries for MySQL 5.0.54 available in my repo.
I forgot to mention, but I updated a couple packages the end of last week. ModSecurity (mod_security) was updated to 2.1.4 and MySQL 5.0.48 (still haven't gotten 5.0.50 or 5.0.51 to pass testing) was rebuilt to add the cluster components ('mysql-cluster').
After a little more than 2 months of waiting since the last release, PHP has been updated once again, this time to 5.2.5. The 5.2.5 release brings several security enhancements, more than 60 bug fixes, and improved performance for those of you that like arrays (and really, who doesn't?).
PHP 5.2.5 also updated the bundled version of PCRE to 7.3, although if you're a user of my repository you've been using that version for quite some time now, and the timezone database to 2007.9.
I was sitting here the other day saying to myself, you know, wouldn't it be nice if I could use the Var cache in XCache to eliminate some of the (far too numerous) queries used by WordPress? Well, I set myself on building a plugin to do just that, but it turns out that someone else actually already did it!
Now, before I go any further I should mention that this isn't actually a plugin, it's more of an extension of existing functionality. It doesn't go in your 'wp-content/plugins' folder (that was the first mistake I made, I never read the directions), it doesn't show up in your plugins list (making you check manually for updates, even under WordPress 2.3), and it doesn't have a pretty GUI in 'wp-admin'.
What it does do is eliminate a number of common queries that get run over and over for every single page view. On this site it eliminated a total of 8 queries per page load. While that only dropped the page generation time by about 0.1 seconds, every little bit counts.
Earlier today I rolled out a bunch of updates to the packages in the repo. If you use any of these you'll need to run a "yum update" to pull them in. Complete details on the updates are at the bottom of this post.
The only update I would consider "critical" is MySQL. Bug #31001 was found after the release of the sources and is probably a deal-breaker for anyone using InnoDB tables as "ORDER BY DESC" no longer works. This respin includes a patch to fix that glitch.
Yeah, I know last month I said that I probably wouldn't be doing any more releases of MySQL from the Enterprise-only sources but I guess I lied. As soon as I saw that 5.0.48 was out I checked it out from BitKeeper and started working to turn that into a package that I could use to build my RPMs. Not wanting to unleash an untested copy of MySQL on the masses, and not knowing how my readers would react to my releasing packages made from an unofficial source tarball, I decided to keep that one private for a while and test it on my own systems.
Well, just about when it got to the point when I was going to release it to the wild, some kind soul went and released the official tarball for 5.0.48 Enterprise. The 5.0.48 binaries currently in my repo are made from the official sources, not my original BitKeeper sources. That said, given how well they worked out for me I am still not opposed to, in the future, releasing Enterprise versions of MySQL that are made from the BitKeeper sources and then later doing a respin if the official source tarball leaks out. If you have a concern about that, let me know.
Whew! Given that it's been 8 months since the release of Apache's httpd 2.2.4 I was starting to wonder whether or not the httpd developers were on an extended vacation. That said, they've just released version 2.2.6 of their wonderful web server. That vacation theory must have been wrong, given that they skipped version 2.2.5 (something that is rarely done) and went straight to 2.2.6. This release is a big one, fixing five potential security issues and numerous bugs to provide a more stable platform.
Well, it's been 3 months since the last release of PHP 5.2 but 5.2.4 is finally here. Unlike the earlier releases of PHP 5.2 which have included both performance/memory optimizations as well as fixes for critical bugs (security issues and otherwise), this release is aimed at improving the overall stability of the 5.2 release chain (no doubt aiming to improve the image of PHP 5.2 with 4.4 being discontinued at the end of the year) by fixing more than 120 small bugs, as well as taking the opportunity to fix a few low-level security holes.
The PHP development team didn't slap a "0mg!!! j00 m|_|$7 |_|pd473 j00r php 0r 3l$3 j00 \/\/1ll b3 h4ck3d!!!" tag on this one but stability is always a good thing so I would recommend that all of my readers upgrade when they get a chance. Really though, since I do all the work, do you really have an excuse NOT to update?