Log message:
Remove example rc.d scripts from PLISTs.

These are now handled dynamically if INIT_SYSTEM is set to "rc.d", or
ignored otherwise.

Log message:
Recursive PKGREVISION bump for OpenSSL API version bump.

Log message:
Changes 5.5.36:

Functionality Added or Changed

CMake now supports a -DTMPDIR=dir_name option to specify the default tmpdir \ 
value. If unspecified, the value defaults to P_tmpdir in <stdio.h>. Thanks \ 
to Honza Horak for the patch.

Bugs Fixed

InnoDB: Table renaming errors would appear in the LATEST FOREIGN KEY ERROR \ 
section of the SHOW ENGINE INNODB STATUS output.

Partitioning: Queries using the index_merge optimization (see Index Merge \ 
Optimization) could return invalid results when run against tables that were \ 
partitioned by HASH.

Partitioning: When no partition had returned a row since the last \ 
HA_ERR_KEY_NOT_FOUND error, the use of uninitialized memory in the priority \ 
queue used for returning rows in sorted order could lead to a crash of the \ 
server.

Replication: mysqlbinlog --verbose failed when it encountered a corrupt row \ 
event in the binary log. Such a row event could also cause the slave to fail.

Replication: When log_warnings is greater than 1, the master prints binary log \ 
dump thread information—containing the slave server ID, binary log file \ 
name, and binary log position—in mysqld.1.err. A slave server ID greater \ 
than 2 billion was printed with a negative value in such cases.

Replication: Invalid event offsets in the binary log were not always handled \ 
correctly, which could lead to replication failure.

The cache used for the Index Merge access method was freed only after successful \ 
retrieval of all rows. Interruption or failure of the operation led to a file \ 
descriptor leak.

For utf8 and utf8mb4 strings, handler functions unnecessarily called a Unicode \ 
conversion function.

Use of a nonmulti-byte algorithm for skipping leading spaces in multi-byte \ 
strings could cause a server exit.

For the utf8_bin collation, ORDER BY LOWER(col_name) could produce incorrect \ 
ordering.

On Windows, the --local-service server option did not work, and was not \ 
displayed in the --help message.

The prototype of the Performance Schema instrumentation API \ 
mysql_cond_timedwait() call was fixed to be drop-in compatible with \ 
pthread_cond_timedwait(). This fix affects only implementers of third-party \ 
plugins.

For the path specified with the --basedir option, mysql_plugin attempted to \ 
unlink the path rather than free the memory in which the path was stored.

COUNT(DISTINCT) sometimes produced an incorrect result when the last read row \ 
contained a NULL value.

Some scripts displayed out-of-date information regarding where to report bugs.

Updating a FEDERATED table with UPDATE... JOIN caused a server exit when the \ 
local table contained a single row and that row could be joined to a row in the \ 
FEDERATED table.

mysql_install_db referred to the obsolete mysqlbug script for reporting \ 
problems. It now refers to http://bugs.mysql.com/ instead.

Log message:
Remove CONFLICTS with ${PKGBASE}, these are automatic.

Avoids unnecessary pkgin warning.

Log message:
Changes 5.5.35:
* Previously, MySQL Server distributions included the MySQL Reference Manual in \ 
Info format (the Docs/mysql.info file). Because the license for the manual \ 
restricts redistribution, its inclusion in Community packages caused problems \ 
for downstream redistributors, such as those who create Linux distributions. \ 
Community distributions of MySQL Server no longer include the mysql.info file, \ 
to make the repackaging and redistribution process easier (for example, the \ 
source tarball and its checksum can be used directly). This change applies to \ 
all source and binary Community packaging formats. Commercial (Enterprise) \ 
distributions are unchanged.
* A new CMake option, WITH_ASAN, permits enabling address sanitization for \ 
compilers that support it.
* Attempts to use the thread_concurrency system variable (which has an effect \ 
only for Solaris 8 and earlier) now indicate that it has no effect when that is \ 
the case.
* Bugs Fixed

Log message:
Changes 5.5.34:
* MySQL 5.7 changed audit log file output to a new format that has better \ 
compatibility with Oracle Audit Vault. This format has been backported to MySQL \ 
5.5 and it is possible to select either the old or new format using the new \ 
audit_log_format system variable, which has permitted values of OLD and NEW \ 
(default OLD). For details about each format, see The Audit Log File.
* InnoDB; Partitioning: Following any query on the INFORMATION_SCHEMA.PARTITIONS \ 
table, InnoDB index statistics as shown in the output of statements such as \ 
SELECT * FROM INFORMATION_SCHEMA.STATISTICS were read from the last partition, \ 
instead of from the partition containing the greatest number of rows.
* InnoDB: The row_sel_sec_rec_is_for_clust_rec function would incorrectly \ 
prepare to compare a NULL column prefix in a secondary index with a non-NULL \ 
column in a clustered index.
* InnoDB: An incorrect purge would occur when rolling back an update to a \ 
delete-marked record.
* InnoDB: InnoDB would rename a user-defined foreign key constraint containing \ 
the string “_ibfk_” in its name, resulting in a duplicate constraint.
* InnoDB: Rolling back an INSERT after a failed BLOB write would result in an \ 
assertion failure. The assertion has been modified to allow NULL BLOB pointers \ 
if an error occurs during a BLOB write.
* InnoDB: A regression introduced with the fix for Bug 11762038 would cause \ 
InnoDB to raise an incorrect error message. The message stated that, \ 
“InnoDB cannot delete/update rows with cascading foreign key constraints \ 
that exceed max depth of 20”. The error message would occur when killing \ 
connections reading from InnoDB tables that did not have foreign key \ 
constraints.
* InnoDB: The documentation incorrectly stated that START TRANSACTION WITH \ 
CONSISTENT SNAPSHOT provides a consistent snapshot only if the current isolation \ 
level is REPEATABLE READ or SERIALIZABLE. START TRANSACTION WITH CONSISTENT \ 
SNAPSHOT only works with REPEATABLE READ. All other isolation levels are \ 
ignored. The documentation has been revised and a warning is now generated \ 
whenever the WITH CONSISTENT SNAPSHOT clause is ignored.
* InnoDB: The srv_master_thread background thread, which monitors server \ 
activity and performs activities such as page flushing when the server is \ 
inactive or in a shutdown state, runs on a one second delay loop. \ 
srv_master_thread would fail to check if the server is in a shutdown state \ 
before sleeping.
more...

Log message:
Changes 5.5.33:

* Previously, program options could be specified in full or as any unambiguous \ 
prefix. For example, the --compress option could be given to mysqldump as \ 
--compr, but not as --comp because the latter is ambiguous. Option prefixes now \ 
are deprecated. They can cause problems when new options are implemented for \ 
programs. A prefix that is currently unambiguous might become ambiguous in the \ 
future. If an unambiguous prefix is given, a warning now occurs to provide \ 
feedback. For example:

Warning: Using unique option prefix compr instead of compress is
deprecated and will be removed in a future release. Please use the
full name instead.

Option prefixes are no longer supported in MySQL 5.7; only full options are accepted.

* comp_err now checks to make sure that new errors are not being added to MySQL \ 
5.1 or 5.5 because the set of errors for these series is frozen.

* Bugs Fixed

Log message:
Distfile got changed (licence clause in mans). Revision bump.
Don't use mk/readline.buildlink3.mk! Must be devel/readline/buildlink3.mk!

Log message:
Bump PKGREVISION of all packages which create users, to pick up change of
sysutils/user_* packages.

Log message:
Changes 5.5.32:
* mysql_upgrade now verifies that the server version matches the version against \ 
which it was compiled, and exits if there is a mismatch. In addiion, a \ 
--version-check option permits specifying whether to enable version checking \ 
(the default), or disable checking if given as --skip-version-checking.
* Bugs Fixed