Archive for November, 2009
(note: give the mirrors some hours to sync up)
- See the Release Notes for relevant bugfixes.
- Drop-in replacement for stock MySQL 5.0 or 5.1 (If you’re coming from stock MySQL, see the MariaDB extras/differences overview).
- If you are upgrading from 5.0, please review the upgrade information first before diving in.
- The packages take care of backward compatibility with the older .so.15 client library (5.1 has .so.16), including on CentOS 5 (no separate “compat” RPM required).
- This release for the first time also has packages (in YUM repo) for RHEL/CentOS 5. The MariaDB RPMs should purposely conflict with any 5.0, as well as any 5.1 of different origin, so that you consciously have to choose to upgrade and won’t accidentally end up for instance automatically upgrading from 5.0 to 5.1. We say should because while we tested various scenarios, the real world is bound to teach us more. Just be cautious, and please file bugs if you spot anything weird.
- We didn’t build RHEL/CentOS 4 RPMs, because it originally came with MySQL 4.1 which is ancient, this means that other packages on that system have a dependency on libmysqlclient.so.14. If you do have a need for RHEL 4 packages, please let us know.
- Generic Linux binary tarballs and the base source tarball to create all builds are also available, although to recreate one of the packages it’s easiest to use the relevant source package.
If you’d like to keep up to date about MariaDB developments, there is a Planet MariaDB. If you have a feed relevant for MariaDB, you can submit it through the site.
Tags: apt-get, binaries, centos, deb, debian, download, etch, federated, federatedx, hardy, innodb, intrepid, jaunty, karmic, lenny, mariadb, mysql, packages, pbxt, red hat, redhat, rhel, rpm, ubuntu, xtradb, yum
MySQL 5.0.87-d10 OurDelta builds are now available (32 and 64-bit):
- Debian: Etch (4), Lenny (5)
- Ubuntu: Hardy (8.04), Intrepid (8.10), Jaunty (9.04), Karmic (9.10)
- RHEL/CentOS: 4, 5
- Binary tarballs: generic Linux, built on Ubuntu Hardy
Then please contact us: i n f o (at) o u r d e l t a (dot) o r g
What are the requirements? Having a server with HTTP access and no hassles with low traffic limits. At this stage you’ll need about 5GB disk space, and you’ll use rsync to sync from the master servers (we’ll provide you with a script to help with that). Thanks!
With the new releases the traffic is up (not surprising) and while our existing mirrors appear to be doing ok so far, it’ll be good to have more available before we run into capacity or speed problems. We also haven’t yet split for geographic location, that too becomes a possibility with more mirrors.