Posts Tagged ‘yum’

MariaDB 10.0.3: installing the additional engines

So MariaDB 10.0.3 Alpha is out. Download it and remember to provide feedback.

When you run SHOW ENGINES by default, you don’t get CassandraSE or the CONNECT engine. Make sure you do a yum install MariaDB-cassandra-engine and a yum install MariaDB-connect-engine

You will run into conflicts if you had an older MariaDB-CassandraSE engine (so yum remove MariaDB-CassandraSE).

Once you’ve got the packages installed, you can either install the plugin or just restart mysqld.

Happy testing!

Updating PHP in RHEL/CentOS 5.6 for WordPress 3.2

Try doing yum install php53 on a RHEL 5.6/CentOS 5.6 system, and see the following:

--> Finished Dependency Resolution
php53-common-5.3.3-1.el5_6.1.x86_64 from updates has depsolving problems
  --> php53-common conflicts with php-common
Error: php53-common conflicts with php-common
 You could try using --skip-broken to work around the problem
 You could try running: package-cleanup --problems
                        package-cleanup --dupes
                        rpm -Va --nofiles --nodigest

Not pleasant right? Seems the only workaround is to issue a yum remove php php-cli php-common, watch the dependencies and reinstall everything. The only thing that seems to be missing? php53-tidy.

Restart Apache (service httpd restart). Update WordPress. If you miss on restarting the web server, it won’t detect the newer PHP install and WordPress will just show you a magical message as follows: “You cannot update because WordPress 3.2.1 requires PHP version 5.2.4 or higher. You are running version 5.1.6.”

CentOS 5.3, yum update fails?

I’m a big CentOS fan. I think servers these days should either be Ubuntu Servers or CentOS based, and nothing else, if you’re going the Linux route.

CentOS 5.3, on the x86_64 platform, seemed to have an issue where yum would cause a traceback, with file.x86_64 0:4.17-15.el5_3.1. There is a bug open for it, but it apparently doesn’t happen on all systems.

The magic around this is to really just run yum clean all, and then run yum update. What that basically does is it cleans all packages that are cached in the system, as well as removes all header files used for dependency resolution.

I haven’t heard jokes about RPM hell in a long time… I am thinking that its mostly disappeared, and largely this is thanks to dependency resolution provided for by yum.