Log message:
Unbreak build on DragonFly BSD.
Add OpenBSD to the exclusion list in chartype.h as with upstream version.

Log message:
Recursive bump for perl5-5.28.0

Log message:
mysql56-client: Backport comparison fix from upstream.

Log message:
mysql56-client: Disable compiler detection on SunOS.

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.

Log message:
mysql56: update to 5.6.38

Changes in MySQL 5.6.38:

Packaging Notes
---------------
mysqlcheck was missing in the MySQL Server Docker image, which prevented \ 
mysql_upgrade from running.

Bugs Fixed
----------
InnoDB: Replication lag occurred on slave instances during large update \ 
operations on tables with many partitions.
InnoDB: A failure occurred during an end range comparison.
InnoDB: Enabling the innodb_buffer_pool_load_now setting failed in readonly \ 
mode. The event that signals the buffer pool load thread was not initialized.
InnoDB: A long wait for a dictionary operation lock held by a full-text search \ 
synchronization operation caused a server exit.
Partitioning: Queries involving NULL were not always handled correctly on tables \ 
that were partitioned by LIST.
Replication: When replicating a partitioned table with an index, on a \ 
replication slave where HASH_SCAN was specified as part of the \ 
slave_rows_search_algorithms setting, the slave I/O thread sometimes stopped \ 
with an error HA_ERR_KEY_NOT_FOUND.
Replication: Replication clients no longer enable LOCAL capability for LOAD DATA \ 
statements, because they do not use LOAD DATA LOCAL statements.
Replication: In case of a failure while creating multiple slave applier worker \ 
threads, some threads would be left orphaned and their resources would not be \ 
collected. Thanks to Laurynas Biveinis for his contribution to fixing this bug.
MSI packages for Windows failed to detect when Microsoft Visual C++ 2010 \ 
Redistributable Package was installed.
yaSSL could incorrectly perform TLS cipher negotiation.
The server failed to check the maximum path length for partition names.
Identifiers containing a mixture of backslashes and backticks could be parsed \ 
incorrectly.
Source packages for Debian platforms contained prebuilt debug binaries, causing \ 
build failures on any architectures other than the one on which those binaries \ 
were built.
Uninstalling the daemon_memcached plugin caused a serious error.
Selecting from a view could yield different results with materialization enabled \ 
versus materialization disabled.
The Performance Schema failed to check the maximum host length for client \ 
connections.
A server error occurred when a full text search result exceeded the \ 
innodb_ft_result_cache_limit setting. The patch for this bug also backports a \ 
related patch.
If a stored function was considered a constant by the optimizer, calling it from \ 
a subquery in a NOT IN condition in the WHERE clause could cause a server exit.
A mysqldump memory leak was fixed.
If a session rolled back to a savepoint and then was killed, the statements up \ 
to the point of the savepoint could be committed.
For clients that used Connector/Python and authenticated using the \ 
sha256_password plugin, the server could handle connections incorrectly.
NAME_CONST() can return null if incorrect arguments are given. In some cases, \ 
this was not handled and could cause a server exit.

Log message:
Follow some redirects.

Log message:
Security Notes
* Security Fix: The linked OpenSSL library for the MySQL Commercial Server has \ 
been updated to version 1.0.2l. 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.

Platform-Specific Notes
* Linux: The generic Linux build for MySQL 5.6 is now built on Oracle Linux 6 \ 
using glibc 2.12. Systems that use the build need to have glibc 2.12 or later \ 
installed on them.

Functionality Added or Changed
* For Windows, MSI installer packages now include a check for the required \ 
Visual Studio redistributable package, and produce a message asking the user to \ 
install it if it is missing.
* The mysql client now supports a --binary-as-hex option that causes display of \ 
binary data using hexadecimal notation (0xvalue). Thanks to Daniël van Eeden \ 
for the patch.
* mysqlaccess now looks for its configuration file only in the SYSCONFDIR \ 
directory and /etc.

Bugs Fixed
* InnoDB: The server allocated memory unnecessarily for an operation that \ 
rebuilt the table.
* InnoDB: When using an index merge optimizer switch, a SELECT COUNT(*) \ 
operation sometimes returned 0. Partitioning code incorrectly performed a memcpy \ 
instead of a column copy of columns read by the index, causing the wrong records \ 
to be copied.
* Replication: A USE statement that followed a SET GTID_NEXT statement sometimes \ 
had no effect.
* Replication: If the binary log on a master server was rotated and a full disk \ 
condition occurred on the partition where the binary log file was being stored, \ 
the server could stop unexpectedly. The fix adds a check for the existence of \ 
the binary log when the dump thread switches to next binary log file. If the \ 
binary log is disabled, all binary logs up to the current active log are \ 
transmitted to slave and an error is returned to the receiver thread.
* Replication: If a relay log index file named relay log files that did not \ 
exist, RESET SLAVE ALL sometimes did not fully clean up properly.
* Replication: mysqlbinlog, if invoked with the --raw option, does not flush the \ 
output file until the process terminates. But if also invoked with the \ 
--stop-never option, the process never terminates, thus nothing is ever written \ 
to the output file. Now the output is flushed after each event.
* Replication: A memory leak in mysqlbinlog was fixed. The leak happened when \ 
processing fake rotate events, or when using --raw and the destination log file \ 
could not be created. The leak only occurred when processing events from a \ 
remote server. Thanks to Laurynas Biveinis for his contribution to fixing this \ 
bug.
* Replication: Multi-threaded slaves could not be configured with small queue \ 
sizes using slave_pending_jobs_size_max if they ever needed to process \ 
transactions larger than that size. Any packet larger than \ 
slave_pending_jobs_size_max was rejected with the error \ 
ER_MTS_EVENT_BIGGER_PENDING_JOBS_SIZE_MAX, even if the packet was smaller than \ 
the limit set by slave_max_allowed_packet.
* With this fix, slave_pending_jobs_size_max becomes a soft limit rather than a \ 
hard limit. If the size of a packet exceeds slave_pending_jobs_size_max but is \ 
less than slave_max_allowed_packet, the transaction is held until all the slave \ 
workers have empty queues, and then processed. All subsequent transactions are \ 
held until the large transaction has been completed. The queue size for slave \ 
workers can therefore be limited while still allowing occasional larger \ 
transactions.
* mysqldump could write database names in USE statements incorrectly.
* If the mysql_stmt_close() C API function was called, it freed memory that \ 
later could be accessed if mysql_stmt_error(), mysql_stmt_errno(), or \ 
mysql_stmt_sqlstate() was called. To obtain error information after a call to \ 
mysql_stmt_close(), call mysql_error(), mysql_errno(), or mysql_sqlstate() \ 
instead.
* Queries could be cached incorrectly, leading to incorrect query results, under \ 
these circumstances: InnoDB table; rows are being inserted but have not yet been \ 
committed; a query uses the table as a base table in a derived table; the \ 
optimizer chooses to materialize the derived table.
* Man pages for a few utilities were missing from Debian/Ubuntu packages.
* The field-t unit test failed to run with AddressSanitizer enabled. Thanks to \ 
Laurynas Biveinis for the patch.
* Debian client packages were missing information about conflicts with native \ 
packages.
* The Perl path in #! lines at the beginning of Perl scripts has been adjusted \ 
to /usr/local/bin/perl for FreeBSD 11.
* The server exited abnormally attempting to access invalid memory.
* A race condition could occur for CREATE TABLE statements with DATA DIRECTORY \ 
or INDEX DIRECTORY clauses.
* MySQL compilation in different directories produced different builds to \ 
leakage of absolute paths into debug information and __FILE__.
* mysqld_failed to start the server if the --datadir option was specified with a \ 
relative path name.
* With read_only enabled, creation of non-TEMPORARY tables by non-SUPER users \ 
was permitted under certain conditions.
*Certain stored functions, if used in a query WHERE clause, could be handled \ 
using Index Condition Pushdown (which should not happen), resulting in a server \ 
exit.
* On x86 machines, the uint3korr() macro read 4 bytes of data instead of the \ 
intended 3 bytes.
* An assertion was raised during a fetch operation by the memcached plugin.
* Queries that contained UNION in a subquery and GROUP BY could return incorrect \ 
results.
* LOAD XML INFILE performance became noticeably slower when the XML file being \ 
read contained a great many spaces, such as those introduced by indenting or \ 
pretty-printing. Now all leading whitespace is trimmed from each such value \ 
before reading it into memory.

Log message:
The mysql client links against libcurses, ensure we pull in the bl3 so
that user preferences are respected.

Log message:
Changes 5.6.36:
* Windows builds now use the default runtime libraries (builds use the /MD flag).
* CMake support was added for compiling with Developer Studio 12.6.
MySQL failed to compile if -DENABLE_DEBUG_SYNC=OFF AND -DWITH_DEBUG=ON were both \ 
given. The ENABLE_DEBUG_SYNC option has been removed and enabling WITH_DEBUG \ 
enables Debug Sync.
* Changes in RPM package structure require a larger set of packages to be \ 
removed to install MySQL Server cleanly.
* To avoid potential race conditions, Debian packages now use the GNU install \ 
utility rather than a combination of mkdir, touch, and chown.
* CMake-generated packaging for Debian/Ubuntu packages was refactored for \ 
improved maintainability. The change includes updated logic for correctly \ 
replacing native distribution packaging in Debian and Ubuntu.
* Reminder: MySQL 5.6 requires the Microsoft Visual C++ 2010 Redistributable \ 
Package to run on Windows platforms. Users should make sure the package has been \ 
installed on the system before starting the server. The package is available at \ 
the Microsoft Download Center.
* The linked OpenSSL library for the MySQL Commercial Server has been updated to \ 
version 1.0.2k. For a description of issues fixed in this version, see \ 
http://www.openssl.org/news/vulnerabilities.html.
* The mysql_options() C API function now supports a MYSQL_OPT_SSL_MODE option.