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

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

Avoids unnecessary pkgin warning.

Log message:
Changes 5.6.15:
* 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.
* Incompatible Change: Several statement instruments in the setup_instruments \ 
table are used by the Performance Schema during the early stages of statement \ 
classification before the exact statement type is known.
* The Performance Schema now instruments the read/write lock Delegate::lock
* A new CMake option, WITH_ASAN, permits enabling address sanitization for \ 
compilers that support it.
* The hash function used for metadata locking was modified to reduce overhead.
* Bugs Fixed

Log message:
Changes 5.6.14:
* 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.6 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.
* Important Change; Replication: START SLAVE UNTIL SQL_AFTER_GTIDS did not cause \ 
the slave to stop until the next GTID event was received following execution of \ 
the transaction having the indicated GTID, which could cause issues in the case \ 
when the next GTID event is delayed, or does not exist. Now the slave stops \ 
after completing the transaction with that GTID.
* 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: When logging the delete-marking of a record during online ALTER \ 
TABLE...ADD PRIMARY KEY, InnoDB writes the transaction ID to the log as it was \ 
before the deletion or delete-marking of the record. When doing this, InnoDB \ 
would overwrite the DB_TRX_ID field in the original table, which could result in \ 
locking issues.
* 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: An assertion would be raised in fil_node_open_file due to a missing \ 
.ibd file. Instead of asserting, InnoDB should return false and the caller of \ 
fil_node_open_file should handle the return message.
* InnoDB: The assertion ut_ad(oldest_lsn <= cur_lsn) in file buf0flu.cc would \ 
fail because the current max LSN would be retrieved from the buffer pool before \ 
the oldest LSN.
* InnoDB: InnoDB memcached add and set operations would perform more slowly than \ 
SQL INSERT operations.
* InnoDB: The InnoDB memcached plugin could be initialized to insert into an \ 
InnoDB table with an INTEGER primary key.
More...

Log message:
Changes 5.6.13:

* Important Change; Replication: By default, when promoting integers from a \ 
smaller type on the master to a larger type on the slave (for example, from a \ 
SMALLINT column on the master to a BIGINT column on the slave), the promoted \ 
values are treated as though they are signed. Now in such cases it is possible \ 
to modify or override this behavior using one or both of ALL_SIGNED, \ 
ALL_UNSIGNED in the set of values specified for the slave_type_conversions \ 
server system variable. For more information, see Row-based replication: \ 
attribute promotion and demotion, as well as the description of the variable.

* 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.

* The C API libmysqlclient shared-library .so files now have version 18.1.0 (up \ 
from version 18.0.0 used in MySQL 5.5).

* In batch mode, mysql formatted result status messages such as \ 
“"Query OK, 1 row affected"” but did not print them. Now \ 
these messages are not formatted.

* Bugs Fixed

Log message:
* .include "../../devel/readline/buildlink3.mk" with USE_GNU_READLINE=yes
  are replaced with .include "../../devel/readline/buildlink3.mk", and
  USE_GNU_READLINE are removed,

* .include "../../devel/readline/buildlink3.mk" without USE_GNU_READLINE
  are replaced with .include "../../mk/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.6.12:
* 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

Log message:
Do not poison build flags with mysql-client bl3 dirs.

Log message:
Explicitly set WITH_EMBEDDED_SERVER=OFF, because the default OFF doesn't
seem to be respected.