Log message:
Changes 5.5.43:
* CMake support was updated to handle CMake version 3.1.
* The server now includes its version number when it writes the initial \ 
“starting” message to the error log, to make it easier to tell which \ 
server instance error log output applies to. This value is the same as that \ 
available from the version system variable.
* Bug fixes.

Log message:
Fix MESSAGE_SRC for the sphinx option. Bump PKGREVISION.

Log message:
Changes 5.5.42:
* Support for the SSL 2.0 and SSL 3.0 protocols has been disabled because they \ 
provide weak encryption.
* yaSSL was upgraded to version 2.3.7.
* The valid date range of the SSL certificates in mysql-test/std_data has been \ 
extended to the year 2029.
* Bugs Fixed

Log message:
Add lost sphinxsearch hashes, make sure they are not lost next time.

Log message:
Changes 5.5.41:
Unknown

Log message:
Don't use 0 as va_list.

Log message:
Add optional Sphinx SE plugin support to MySQL 5.5 and 5.6.
Intented as a clean implementation (replacement) of wip/mysql-sphinxse.

SphinxSE is MySQL storage engine which can be compiled into MySQL server 5.x
using its pluggable architecture. Despite the name, SphinxSE does not
actually store any data itself. It is actually a built-in client which
allows MySQL server to talk to searchd, run search queries, and obtain
search results. All indexing and searching happen outside MySQL.

See http://sphinxsearch.com/docs/current.html#sphinxse-overview

Log message:
Remove SVR4_PKGNAME, per discussion on tech-pkg.

Log message:
Changes 5.5.40:
InnoDB: An ALTER TABLE ... ADD FOREIGN KEY operation could cause a serious error.
InnoDB: With a transaction isolation level less than or equal to READ COMMITTED, \ 
gap locks were not taken when scanning a unique secondary index to check for \ 
duplicates. As a result, duplicate check logic failed allowing duplicate key \ 
values in the unique secondary index.
InnoDB: During recovery, a segmentation fault would occur when marking a table \ 
as corrupt.
yaSSL client code did not validate the encryption size or session ID length, \ 
which could cause the client to exit.
MySQL installation from RPM packages could fail if Postfix had been installed \ 
using yum.
yaSSL could fail preauthorization if the client supplied inaccurate buffer lengths.
Competition between threads could lead to timeout failure trying to rotate the \ 
audit log file.
On Linux (OEL6), if Sun DTrace was installed, the MySQL build failed.
LPAD() and RPAD() could cause a server exit if the pad string argument was not \ 
well formed.
The optimizer could create a zero-length column for a temporary table, causing a \ 
server exit.

Log message:
Remove WRAPPER_BINDIR references in mysqlbug.