Log message:
mysql56: updated to 5.6.48

Changes in MySQL 5.6.48

Bugs Fixed

InnoDB: A tablespace import operation that failed due to the source and \ 
destination tables being defined with different DATA DIRECTORY clauses reported \ 
an insufficiently descriptive schema mismatch error. Moreover, if a .cfg file \ 
was not present, the same operation would raise an assertion failure. A more \ 
informative error message is now reported in both cases before the import \ 
operation is terminated due to the data directory mismatch.

InnoDB: Updating certain InnoDB system variables that take string values raised \ 
invalid read errors during Valgrind testing.

Replication: In the event of an unplanned disconnection of a replication slave \ 
from the master, the reference to the master's dump thread might not be removed \ 
from the list of registered slaves, in which case statements that accessed the \ 
list of slaves would fail. The issue has now been fixed.

Replication: With the settings binlog_format=MIXED, tx_isolation=READ-COMMITTED, \ 
and binlog_row_image=FULL, an INSERT ... SELECT query involving a transactional \ 
storage engine omitted any columns with a null value from the row image written \ 
to the binary log. This happened because when processing INSERT ... SELECT \ 
statements, the columns were marked for inserts before the binary logging format \ 
was selected. The issue has now been fixed.

The Event Scheduler had a memory leak.

Under certain circumstances, a memcached command could result in reading an \ 
uninitialized memory buffer, causing a failure.

CONCAT() and CONCAT_WS() could produce incorrect results in rare cases due to \ 
incorrect substring handling.

Scheduling of events could be disturbed by removing events.

Client programs could load authentication plugins from outside the plugin library.

A query with a WHERE clause whose predicate contained a numeric value in \ 
scientific notation was not handled correctly.

In addition, attempting to insert a particular integer specified as a string \ 
caused a server exit when the string-to-integer conversion was not successful.

The client library could dereference a null pointer while fetching result set \ 
metadata from the server.

Log message:
databases/mysql56-client: allow no-op SUBST block

In an unprivileged bulk build on NetBSD 8.0, the WRAPPER_BINDIR was not
found in the file.  Maybe there are other systems that need it.

Log message:
databases/mysql56-client: allow no-op SUBST class

Log message:
mysql56: updated to 5.6.47

Changes in MySQL 5.6.47:

Bugs Fixed

Replication: When GTIDs are enabled on a replication master and slave, and the \ 
slave connects to the master with the MASTER_AUTO_POSITION=1 option set, the \ 
master must send the slave all the transactions that the slave has not already \ 
received, committed, or both. If any of the transactions that should be sent by \ 
the master have been already purged from the master's binary log, the master \ 
sends the error ER_MASTER_HAS_PURGED_REQUIRED_GTIDS (1789) to the slave, and \ 
replication does not start.

The message provided for the error ER_MASTER_HAS_PURGED_REQUIRED_GTIDS has been \ 
changed to provide advice on the correct action in this situation, which is for \ 
the slave to replicate the missing transactions from another source, or for the \ 
slave to be replaced by a new slave created from a more recent backup. The \ 
message advises that the master's binary log expiration period can be revised to \ 
avoid the situation in future. In addition, the master now identifies the GTIDs \ 
of the purged transactions and supplies them in its error log in the warning \ 
message ER_FOUND_MISSING_GTIDS (11809), so that you do not need to calculate the \ 
missing GTIDs manually.

With multiple sessions executing concurrent INSERT ... ON DUPLICATE KEY UPDATE \ 
statements into a table with an AUTO_INCREMENT column but not specifying the \ 
AUTO_INCREMENT value, inserts could fail with a unique index violation.

A SELECT using a WHERE condition of the form A AND (B OR C [OR ...]) resulting \ 
in an impossible range led to an unplanned exit of the server.

An incomplete connection packet could cause clients not to properly initialize \ 
the authentication plugin name.

Log message:
databases/mysql*: Update DESCR with EOL status

Log message:
*: Recursive revision bump for openssl 1.1.1.

Log message:
mysql56-client: remove unused patches

Log message:
mysql56: updated to 5.6.46

Changes in MySQL 5.6.46

Configuration Notes

It is now possible to compile MySQL 5.6 using OpenSSL 1.1.1, enabling \ 
compilation support for MySQL 5.6 against OpenSSL even when OpenSSL 1.0.2 \ 
reaches End of Life status at the end of 2019.

In addition, MySQL 5.6 now supports TLSv1.1 and TLSv1.2 protocols for encrypted \ 
connections. This applies to MySQL Server, MySQL clients such as mysql and \ 
mysqldump, and master/slave replication. Previously, MySQL 5.6 supported only \ 
TLSv1, so TLSv1.1/TLSv1.2 support enables use of more secure TLS protocols. It \ 
also enables connecting from MySQL 5.6 clients and replication slaves to MySQL \ 
5.7 and higher servers that have TLSv1 disabled, which previously was not \ 
possible. It also means that MySQL 5.7 and higher clients that do not want to \ 
use TLSv1 can connect to MySQL 5.6 servers.

All MySQL 5.6 builds now use OpenSSL. MySQL no longer supports using yaSSL as \ 
the SSL library, and source distributions no longer include yaSSL.

The WITH_SSL CMake option no longer permits bundled (use yaSSL) as a valid \ 
value, and the default option value has changed from bundled to system (use the \ 
version of OpenSSL installed on the host system).

Bugs Fixed

Improper locking during storage engine initialization could cause a server exit.

A query with a WHERE clause whose predicate contained a numeric value in \ 
scientific notation was not handled correctly.

VS2019 produced compilation errors with debug compilation selected due to use of \ 
the /ZI flag. Now /Z7 is used instead.

Password masking was incomplete for SHOW PROCESSLIST and some INFORMATION_SCHEMA \ 
and Performance Schema tables.

The -DWITH_EXAMPLE_STORAGE_ENGINE=1 CMake option was ignored but should not have \ 
been. If -DWITH_EXAMPLE_STORAGE_ENGINE=0 is given, the EXAMPLE storage engine is \ 
built as a plugin.

Log message:
databases/mysql56-client: allow build with OpenSSL 1.1.x

* Allow mysql56-{client,server} build with OpenSSL 1.1.x.
* Reduce a few useless warnings.

Log message:
Bump PKGREVISIONs for perl 5.30.0