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-server: remove SUBST for none existing file

Remove SUBST and CHECK_INTERPRETER_SKIP for none existing file.

Log message:
Bump PKGREVISIONs for perl 5.30.0

Log message:
mysql56: updated to 5.6.45

Changes in MySQL 5.6.45:

Functionality Added or Changed

Microsoft Windows: A new warning message now reminds DBAs that connections made \ 
using the MySQL named pipe on Windows has limited the permissions a connector \ 
can request on the named pipe.

Previously, the named_pipe_full_access_group system variable was set to a value \ 
that maps to the built-in Windows Everyone group (SID S-1-1-0) by default. \ 
However, this group is not ideal and should be replaced with a group that \ 
restricts its membership for connectors that are unable to request fewer \ 
permissions on the MySQL named pipe.

The new warning is written to the error log at startup if the string value \ 
assigned to named_pipe_full_access_group is '*everyone*' (or the Windows System \ 
Language equivalent) and named pipes are enabled. In addition, the warning is \ 
written to the error log and raised to the client if the system variable is \ 
reset to the Everyone group at runtime.

Bugs Fixed

InnoDB: A query that scanned the primary key of a table did not return the \ 
expected result.

InnoDB: A full-text cache lock taken when data is synchronized was not released \ 
if the full-text cache size exceeded the full-text cache size limit.

InnoDB: Client sessions using different auto_increment_increment values while \ 
performing concurrent insert operations could cause a duplicate key error.

Replication: In query log events in the binary log, the thread ID used for the \ 
execution of DROP TABLE and DELETE statements was identified incorrectly or not \ 
at all. On a multi-threaded replication slave, where temporary tables were \ 
involved (which require the correct thread ID as they are session specific), \ 
this omission resulted in errors when using mysqlbinlog to replay the binary log \ 
for point-in-time recovery. The thread ID is now set correctly.

Installing from RPM packages could result in an error log with incorrect permissions.

Enabling audit log encryption could cause a server exit.

MySQL Installer did not install OpenSSL DLL dependencies if the Development \ 
component was not selected.

The parser could leak memory for certain multiple-statement queries.

MySQL does not support OpenSSL session tickets, but did not set the \ 
SSL_OP_NO_TICKET flag to inform OpenSSL of that. The flag is now set.

UpdateXML() did not always free memory properly in certain cases.

Empty values in the name column of the mysql.plugin system table caused the \ 
server to exit during startup.

Some PROXY grants were not replicated to slaves, causing incorrect replication.

If an INSTALL PLUGIN statement contained invalid UTF-8 characters in the shared \ 
library name, it caused the server to hang (or to raise an assertion in debug \ 
builds).

Log message:
Bump PKGREVISION for addition of USE_GCC_RUNTIME

Log message:
mysql56: updated to 5.6.44

mysql-5.6.44:
Unknown changes

Log message:
mysql56-{client,server}: updated to 5.6.43

Changes in MySQL 5.6.43:

Functionality Added or Changed

Microsoft Windows: The access control granted to clients on the named pipe \ 
created by the MySQL server now is set to the minimum necessary for successful \ 
communication on Windows. Newer MySQL client software can open named pipe \ 
connections without any additional configuration. If older client software \ 
cannot be upgraded immediately, the new named_pipe_full_access_group server \ 
system variable can be used to give a Windows group the necessary permissions to \ 
open a named pipe connection. Membership in the full-access group should be \ 
restricted and temporary.

Bugs Fixed

Replication: A patch to correct the handling of quotes for identifiers in \ 
ROLLBACK TO SAVEPOINT statements in the binary log was not correctly applied to \ 
subsequent MySQL versions.

Replication: In some circumstances, the CHANGE MASTER TO statement could not be \ 
used on a replication slave if the master info log had been changed from a table \ 
(master_info_repository=TABLE) into a file (master_info_repository=FILE).

Replication: The value returned by a SHOW SLAVE STATUS statement for the total \ 
combined size of all existing relay log files (Relay_Log_Space) could become \ 
much larger than the actual disk space used by the relay log files. The I/O \ 
thread did not lock the variable while it updated the value, so the SQL thread \ 
could automatically delete a relay log file and write a reduced value before the \ 
I/O thread finished updating the value. The I/O thread then wrote its original \ 
size calculation, ignoring the SQL thread's update and so adding back the space \ 
for the deleted file. The Relay_Log_Space value is now locked during updates to \ 
prevent concurrent updates and ensure an accurate calculation.

Replication: If the relay log index file was temporarily locked for viewing by a \ 
backup process for a replication slave, and MySQL Server also attempted to \ 
access the file at that time for rename or delete operations, the backup \ 
completed with warnings, but MySQL Server experienced an unexpected halt. MySQL \ 
Server now retries the file access operation a number of times in case this or a \ 
similar scenario is the explanation and the file becomes available again before \ 
long.

The server permitted creation of databases with the same name as redo log files, \ 
which could result in unexpected server behavior. Such names are no longer \ 
permitted as database names.

When a subquery contained a UNION, the count of the number of subquery columns \ 
was calculated incorrectly.

Comparing log file names as strings using the memcmp() function resulted in \ 
uninitialized memory read errors. The comparison now uses the strncmp() \ 
function. Thanks to Zsolt Parragi and Laurynas Biveinis for their contributions.

The transformation of IN subquery predicates into semijoins was not handled \ 
correctly for a very large number of tables.

Executing a prepared statement to do a multiple-row insert with large number of \ 
placeholders consumed excessive memory and could execute slowly.

The parser accepted invalid SET statement syntax in trigger definitions that \ 
could result in a server exit.

MyISAM index corruption could occur for bulk-insert and table-repair operations \ 
that involve the repair-by-sorting algorithm and many (more than 450 million) \ 
rows.

A query employing a dynamic range and an index merge could use more memory than \ 
expected.

Log message:
mysql56: updated to 5.6.42

Changes in MySQL 5.6.42

Functionality Added or Changed

* Previously, file I/O performed in the I/O cache in the mysys library was not \ 
instrumented, affecting in particular file I/O statistics reported by the \ 
Performance Schema about the binary log index file. Now, this I/O is \ 
instrumented and Performance Schema statistics are accurate. Thanks to Yura \ 
Sorokin for the contribution.

* The zlib library version bundled with MySQL was raised from version 1.2.3 to \ 
version 1.2.11. MySQL implements compression with the help of the zlib library.

* The zlib compressBound() function in zlib 1.2.11 returns a slightly higher \ 
estimate of the buffer size required to compress a given length of bytes than it \ 
did in zlib version 1.2.3. The compressBound() function is called by InnoDB \ 
functions that determine the maximum row size permitted when creating compressed \ 
InnoDB tables or inserting rows into compressed InnoDB tables. As a result, \ 
CREATE TABLE ... ROW_FORMAT=COMPRESSED or INSERT operations with row sizes very \ 
close to the maximum row size that were successful in earlier releases could now \ 
fail.

Bugs Fixed

* InnoDB: An ALTER TABLE operation that added a primary key produced a \ 
segmentation fault.

* InnoDB: An assertion was raised during an OPTIMIZE TABLE operation.

* InnoDB: A foreign key constraint name was duplicated during a rename table \ 
operation, causing a failure during later query execution.

* InnoDB: The location of the Innodb Merge Temp File that reported by the \ 
wait/io/file/innodb/innodb_temp_file Performance Schema instrument was \ 
incorrect.

* Replication: When FLUSH statements for specific log types (such as FLUSH SLOW \ 
LOGS) resulted in an error, the statements were still written to the binary log. \ 
This stopped replication because the error had occurred on the master, but did \ 
not occur on the slave. MySQL Server now checks on the outcome of these FLUSH \ 
statements, and if an error occurred, the statement is not written to the binary \ 
log.

* Microsoft Windows: On Windows, uninstallation of the MySQL Server MSI package \ 
through MySQL Installer produced a spurious popup window.

* Concurrent INSERT and SELECT statements on a MERGE table could result in a \ 
server exit.

* MySQL Server and test RPM packages were missing perl-Data-Dumper as a dependency.

* For the mysql client, the -b short option was associated with two long \ 
options, --no-beep and --binary-as-hex. The -b option now is associated only \ 
with --no-beep.

* Very long table keys were handled incorrectly on replication slaves.

* During server startup/shutdown, PID files could be mishandled.

* For MEMORY tables, memory overflow errors could occur.

* When converting from a BLOB (or TEXT) type to a smaller BLOB (or TEXT) type, \ 
no warning or error was reported informing about the truncation or data loss. \ 
Now an appropriate error is issued in strict SQL mode and a warning in nonstrict \ 
SQL mode.

* Failure to create a temporary table during a MyISAM query could cause a server \ 
exit. Thanks to Facebook for the patch.

* An attempted read of an uncommitted transaction raised an assertion.

* ALTER TABLE ... REORGANIZE PARTITION ... could result in incorrect behavior if \ 
any partition other than the last was missing the VALUES LESS THAN part of the \ 
syntax.

* yum update did not properly update from RHEL5 RPM packages to current packages.

* It was possible for a subquery that used a unique key on a column allowing \ 
NULL to return multiple rows.

Log message:
Recursive bump for perl5-5.28.0

Log message:
mysql56: updated to 5.6.39

MySQL 5.6.39

Configuration Notes
* For RHEL, SLES, and Fedora RPMs, the default plugin directory for debug builds \ 
has been changed from /usr/lib64/mysql/plugin to /usr/lib64/mysql/plugin/debug.

Security Notes
* Incompatible Change: Passwords are now restricted to a maximum of 256 \ 
characters for the sha256_password authentication plugin, and for the PASSWORD() \ 
function when old_passwords=2. Also, the number of password hashing rounds is \ 
capped to limit CPU time used.
* The linked OpenSSL library for the MySQL Commercial Server has been updated to \ 
version 1.0.2n. Issues fixed in the new OpenSSL version are described at \ 
http://www.openssl.org/news/vulnerabilities.html.
* This change does not affect the Oracle-produced MySQL Community build of MySQL \ 
Server, which uses the yaSSL library instead.

Test Suite Notes
* Documentation for the MySQL Test Suite is now maintained in the MySQL source \ 
tree using Doxygen (see \ 
http://dev.mysql.com/doc/dev/mysql-server/latest/PAGE_MYSQL_TEST_RUN.html). The \ 
related Unix man pages that previously were produced from the old test suite \ 
manual are no longer updated and have gone out of date. Consequently, they are \ 
no longer included in MySQL distributions.

Bugs Fixed
* InnoDB: An ALTER TABLE operation caused the server to halt.
* InnoDB: A FLUSH TABLES operation failed to drop an aborted index. While \ 
removing the table from the cache, the clustered index was dropped prior to \ 
checking for the aborted index.
* InnoDB: Warnings that should only appear in a debug version of MySQL were \ 
printed to the error log when the length of the history list exceeded 2000000.
* InnoDB: Full-text search on indexed columns that use a binary collation did \ 
not return case sensitive matches.
* Partitioning: In certain cases when fetching heap records a partition ID could \ 
be set to zero.
* Replication: With semisynchronous replication in use, if RESET MASTER was \ 
issued while an active transaction was waiting for an acknowledgement from the \ 
slave, the count of waiting sessions in the Rpl_semi_sync_master_wait_sessions \ 
server status variable was incorrect after the wait was completed.
* Microsoft Windows: On Windows, with the myisam_use_mmap and flush system \ 
variables enabled, MyISAM did not always flush table files properly.
* Microsoft Windows: On Windows, resolution was improved of a timer used for \ 
query performance assessment.
* VALUES() was not handled correctly in some cases.
* The Performance Schema now stores rewritten rather than raw SQL statement text \ 
when available.
* Incorrect results or a server exit could result when SHA2() was passed a \ 
user-defined variable in some character sets.
* Creating a table with excessive index information could cause a server exit.
* REFERENCES privilege checking could use the incorrect database in some cases.
* Some statements could cause a buffer overflow in the digest code. Thanks to \ 
Laurynas Biveinis and Roel van de Paar for the patch.
* Incorrect results could occur on a table with a unique index when the \ 
optimizer chose a loose index scan even though the unique index had no index \ 
extensions.
* Executing a stored procedure containing a statement that created a table from \ 
the contents of certain SELECT statements could result in a memory leak.
* For geometry calculations, invalid input parameters could lead to an incorrect \ 
result buffer and cause an assertion to be raised or a server exit.
* Setting the MYSQL_GROUP_SUFFIX environment variable had no effect.
* A circular dependency problem involving sql/sql_builtin.cc was resolved.
* A prepared statement containing an ORDER BY list that referred to a parameter \ 
was not always handled correctly.