Dealing with Sphinx: encountered a bug?

First reaction of most people when getting a bug, either unexpected result or program crash is to either fill a bug ticket or report it on the forum.

Is this the best way? Well, you need to do something before jumping on reporting a bug: more exactly, be sure you use latest version.

There are a lot of reports with crashes or “this doesn’t work as it supposed to do”. When you ask, what you find? In general they use 2.0.2-beta or 2.0.1 or worst : 0.9.9.

0.9.9 was released THREE years ago. Sphinx doesn’t even support this version, with exception of express request ( read money ). Some linux distributions still come with 0.9.9 in their repositories. Use a package from Sphinx site. A version like 0.9.9 is old, might have bugs, miss a lot of features and the open-source support will never fix a reported bug for it. Same goes for 1.10. Bugs are fixed for latest stable, latest beta and development version. That is 2.0.6 , 2.1.1 and trunk at the moment of writing this post.

You should always have the latest (stable) of Sphinx. Why ? Two reasons : every maintanance release gets fixes and possible speed improvements. Sphinx includes compability backwards so it’s safe to upgrade. A newer version can handle an upgrade indexes created with an older version. Even between releases as 2.0.6 and 2.1.1. Of course, it’s wise to do a backup of the indexes in case something might go wrong. Upgrading is very easy. If you use a binary package, just install the binary package for the newer version. Sphinx itself consists of several executables and a configuration file. The binary packages will not overwrite your config, in case of an upgrade.


Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.