Log message:
Changes 5.5.46:
* yaSSL was upgraded to version 2.3.8.
* InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the \ 
correct fences when setting or unsetting the lock word.
* InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary \ 
index resulted in a constraint violation. Thanks to Alexey Kopytov for the \ 
patch.
* InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in \ 
the leaf page than was actually available.
* InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system \ 
could result in a hang condition when running an INSERT INTO ... SELECT ... FROM \ 
tbl_name operation with the wrong tbl_name letter case. An error message is now \ 
printed and the server exits when attempting to start the server with \ 
--lower_case_table_names=0 on a case-insensitive file system.
* Partitioning: CREATE TABLE statements that used an invalid function in a \ 
subpartitioning expression did not always fail gracefully as expected.
* Partitioning: ALTER TABLE when executed from a stored procedure did not always \ 
work correctly with tables partitioned by RANGE.
* Certain subqueries as arguments to PROCEDURE ANALYSE() could cause a server exit.
* mysql_ssl_rsa_setup could create an unwanted .rnd file in the data directory. \ 
(The file is actually created by openssl, which mysql_ssl_ras_setup invokes. \ 
mysql_ssl_rsa_setup now cleans up the file.)
* An assertion could be raised due to incorrect error handling if a SELECT ... \ 
FOR UPDATE subquery resulted in deadlock and caused a rollback.
* Servers linked against yaSSL and compiled with GCC 4.8.2 could fail to respond \ 
correctly to connection attempts until several seconds after startup.
* For tables with subpartitions, the server could exit due to incorrect error \ 
handling during partition pruning if the partition could be identified but not \ 
the subpartition.
* DELETE could check privileges for the wrong database when table aliases were used.
* Within a trigger, use of a cursor that accessed OLD or NEW values from a row \ 
could cause a server exit.
* MySQL sometimes produced no warning when it was unable to interpret a \ 
character in a given character set.
* For MySQL distributions linked against yaSSL, a corrupt client key file could \ 
cause clients to exit.
* Execution of certain BINLOG statements while temporary tables were open by \ 
HANDLER statements could cause a server exit.

Log message:
Changes 5.5.45:
* Security Fix: Due to the LogJam issue (https://weakdh.org/), OpenSSL has \ 
changed the Diffie-Hellman key length parameters for openssl-1.0.1n and up. \ 
OpenSSL has provided a detailed explanation at \ 
http://openssl.org/news/secadv_20150611.txt. To adopt this change in MySQL, the \ 
key length used in vio/viosslfactories.c for creating Diffie-Hellman keys has \ 
been increased from 512 to 2,048 bits.
* InnoDB: On Unix-like platforms, os_file_create_simple_no_error_handling_func \ 
and os_file_create_func opened files in different modes when innodb_flush_method \ 
was set to O_DIRECT.
* InnoDB: An assertion was raised when InnoDB attempted to dereference a NULL \ 
foreign key object.
* InnoDB: An index record was not found on rollback due to inconsistencies in \ 
the purge_node_t structure.
* The Spencer regex library used for the REGEXP operator could be subject to \ 
heap overflow in some circumstances.
* A buffer-overflow error could occur for mysqlslap during option parsing.
* GROUP BY or ORDER BY on a CHAR(0) NOT NULL column could lead to a server exit.
* mysql-systemd-start failed if datadir was set in /etc/my.cnf.
* On OS X 10.10 (Yosemite), mysqld failed to start automatically. The startup \ 
item has been replaced with a launchd job, which enables the preference pane \ 
checkbox for automatic startup to work again.

Log message:
Changes 5.5.44:
Bugs fixed:
* InnoDB; Partitioning: The CREATE_TIME column of the INFORMATION_SCHEMA.TABLES \ 
table now shows the correct table creation time for partitioned InnoDB tables. \ 
The CREATE_TIME column of the INFORMATION_SCHEMA.PARTITIONS table now shows the \ 
correct partition creation time for a partition of partitioned InnoDB tables.

The UPDATE_TIME column of the INFORMATION_SCHEMA.TABLES table now shows when a \ 
partitioned InnoDB table was last updated by an INSERT, DELETE, or UPDATE. The \ 
UPDATE_TIME column of the INFORMATION_SCHEMA.PARTITIONS table now shows when a \ 
partition of a partitioned InnoDB table was last updated.

* InnoDB: An assertion was raised on shutdown due to XA PREPARE transactions \ 
holding explicit locks.

* InnoDB: Removal of a foreign key object from the data dictionary cache during \ 
error handling caused the server to exit.

* InnoDB: SHOW ENGINE INNODB STATUS output showed negative reservation and \ 
signal count values due to a counter overflow error.

* InnoDB: Estimates that were too low for the size of merge chunks in the result \ 
sorting algorithm caused a server exit.

* SHOW VARIABLES mutexes were being locked twice, resulting in a server exit.

* A Provides rule in RPM .spec files misspelled “mysql-embedded” as \ 
“mysql-emdedded”.

* Under certain conditions, the libedit command-line library could write outside \ 
an array boundary and cause a client program crash.

* Host value matching for the grant tables could fail to use the most specific \ 
of values that contained wildcard characters.

* A user with a name of event_scheduler could view the Event Scheduler process \ 
list without the PROCESS privilege.

* SHOW GRANTS after connecting using a proxy user could display the password \ 
hash of the proxied user.

* For a prepared statement with an ORDER BY that refers by column number to a \ 
GROUP_CONCAT() expression that has an outer reference, repeated statement \ 
execution could cause a server exit.

* Loading corrupt spatial data into a MyISAM table could cause the server to \ 
exit during index building.

* Certain queries for the INFORMATION_SCHEMA TABLES and COLUMNS tables could \ 
lead to excessive memory use when there were large numbers of empty InnoDB \ 
tables.

* MySQL failed to compile using OpenSSL 0.9.8e.

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:
The bundled SMF manifest should not have a project called for. This had been
added erroneously, based on modified Joyent manifests. Bump PKGREVISION for
the MySQL cluster/server packages.

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:
Pipe mysqld_safe's stdout and stderr to syslog to avoid the problem
in PR pkg/48271. (There's a mysqld_safe switch to log to syslog,
which would also work around the problem, at the expense mutually
exclusivity with normal MySQL logging). Bump PKGREVISIONs.

Log message:
Changes 5.5.41:
Unknown

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