Log message:
*: bump for openssl 3

Log message:
mysql56-server: note this version is EOL

Log message:
*: recursive bump for perl 5.34

Log message:
mysql56: updated to 5.6.51

Changes in MySQL 5.6.51

Security Notes

The linked OpenSSL library for MySQL Server has been updated to version 1.1.1i. \ 
Issues fixed in the new OpenSSL version are described at \ 
https://www.openssl.org/news/cl111.txt and \ 
https://www.openssl.org/news/vulnerabilities.html.

Bugs Fixed

InnoDB: The full-text search synchronization thread attempted to read a \ 
previously-freed word from the index cache.

The server did not handle all cases of the WHERE_CONDITION optimization correctly.

Privileges for some INFORMATION_SCHEMA tables were checked incorrectly.

In certain cases, the server did not handle multiply-nested subqueries correctly.

A buffer overflow in the client library was fixed.

Log message:
Update MySQL 5.6 to 5.6.50.

Note that the 5.6 series will be end of life in February 2021.  The
current major version is 8.0, which isn't in pkgsrc yet.  You CAN NOT
upgrade directly from 5.6 to 8.0, therefore it is recommended for anybody
running 5.6 to upgrade to this version, then upgrade to 5.7.

Changes in MySQL 5.6.50 (2020-10-19, General Availability)

Functionality Added or Changed

    LOCK TABLES privilege checking for views was improved. (Bug #31304432)

Bugs Fixed

    InnoDB: In session started with START TRANSACTION WITH CONSISTENT
    SNAPSHOT, a range query returned a truncated result. The end
    range flag was not reset at the beginning of the index read
    resulting in an aborted read and missing rows. (Bug #30950714,
    Bug #98642)

    References: This issue is a regression of: Bug #23481444.

    In bootstrapping mode, certain multiple-statement transactions
    could cause unexpected server behavior. (Bug #31650096)

    Assigning CONCAT('') or CONCAT_WS('') to a variable set the
    variable to NULL, not the empty string. (Bug #31320716, Bug
    #99485, Bug #31413167, Bug #99722)

    ORDER BY queries were not executed correctly when sort_buffer_size
    and max_sort_length were set to values which caused the internal
    limit on the maximum number of keys allowed per sort buffer to
    be set to 0. (Bug #30175483)

    The internal method Field_tiny::pack() did not always perform
    bounds checking as expected. (Bug #29948029)

    References: See also: Bug #31591391.

    A large number of nested arguments in full-text search query
    caused an error. (Bug #29929684)

    An assertion could be raised when the SQL layer passed incorrect
    information to InnoDB about the type of operation to be performed
    on a temporary table. (Bug #22503696)

Log message:
*: bump PKGREVISION for perl-5.32.

Log message:
mysql56: updated to 5.6.49

Changes in MySQL 5.6.49

Configuration Notes

tcmalloc is no longer a permitted value for the mysqld_safe --malloc-lib option.

Security Notes

Incompatible Change: Access to the INFORMATION_SCHEMA.FILES table now requires \ 
the PROCESS privilege.

This change affects users of the mysqldump command, which accesses tablespace \ 
information in the FILES table, and thus now requires the PROCESS privilege as \ 
well. Users who do not need to dump tablespace information can work around this \ 
requirement by invoking mysqldump with the --no-tablespaces option.

The linked OpenSSL library for MySQL Server has been updated to version 1.1.1g. \ 
Issues fixed in the new OpenSSL version are described at \ 
https://www.openssl.org/news/cl111.txt and \ 
https://www.openssl.org/news/vulnerabilities.html.

Bugs Fixed

Partitioning: A query against a partitioned table, which used an ORDER BY, \ 
returned unordered results under the following conditions:

The table had a composite index with a prefix on one of the columns.

The query's WHERE clause contained an equality condition on the prefixed column.

The column with the prefix was the leftmost column in the index.

The column used in the ORDER BY was the rightmost column in the index.

The index was used for handling the ORDER BY.

Our thanks to Quanan Han for the contribution.

Replication: When a replication source server shuts down and restarts, its \ 
MEMORY tables become empty. To replicate this effect to replicas, the first time \ 
that the source uses a given MEMORY table after startup, it notifies replicas \ 
that the table must be emptied by writing a DELETE statement for that table to \ 
the binary log. Previously, the generated DELETE statement was written to the \ 
binary log statement cache for the current session, which could result in it \ 
being logged together with other statements under the same GTID, or logged \ 
without BEGIN and COMMIT statements. Also, in some situations, the generated \ 
DELETE statement could consume the GTID intended for the transaction that \ 
triggered it. The generated DELETE statement is now logged with accompanying \ 
BEGIN and COMMIT statements, and the resulting transaction is flushed to the \ 
binary log immediately after it is written to the statement cache, so that it \ 
always receives its own GTID and is kept separate from other tra
nsactions.

mysql_store_result() could fail to detect invalid data packets.

The server sometimes mistakenly removed a subquery with a GROUP BY when \ 
optimizing a query, even in some cases when this subquery was used by an outer \ 
select. This could occur when the subquery also used an aggregate function.

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:
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:
*: Recursive revision bump for openssl 1.1.1.