Log message:
Change the service_bundle name to "export" to reduce diffs between the
original manifest.xml file and the output from "svccfg export".

Log message:
Add or fix manpath entries to use the correct path.

Log message:
Changes 5.6.30:

Security Notes
--------------
The linked OpenSSL library for the MySQL Commercial Server has been updated to \ 
version 1.0.1s. Issues fixed in the new 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.

MySQL client programs now support an --ssl-mode option that enables you to \ 
specify the security state of the connection to the server. The default value is \ 
DISABLED (establish an unencrypted connection). --ssl-mode=REQUIRED) can be \ 
specified to require a secure connection, or fail if a secure connection cannot \ 
be obtained.

These clients support --ssl-mode: mysql, mysqladmin, mysqlcheck, mysqldump, \ 
mysqlimport, mysqlshow, mysqlpump, mysqlslap, mysqltest, mysql_upgrade.

For more information, see Command Options for Secure Connections.

Bugs Fixed

Log message:
Bump PKGREVISION for security/openssl ABI bump.

Log message:
Changes 5.6.29:
* InnoDB: A new InnoDB configuration option, innodb_tmpdir, allows you to \ 
configure a separate temporary file directory for online ALTER TABLE operations. \ 
This option was introduced to help avoid tmpdir overflows that could occur as a \ 
result of large temporary files created during online ALTER TABLE operations. \ 
innodb_tmpdir is a SESSION variable and can be configured dynamically using a \ 
SET statement.
* yaSSL was upgraded to version 2.3.9. This upgrade corrects an issue in which \ 
yaSSL handled only cases of zero or one leading zeros for the key agreement \ 
instead of potentially any number, which in rare cases could cause connections \ 
to fail when using DHE cipher suites.
* The Valgrind function signature in mysql-test/valgrind.supp was upgraded for \ 
Valgrind 3.11.
* Bugs Fixed

Log message:
Changes 5.6.28:
MySQL Server RPM packages now contain a conflict indicator for MySQL Connector \ 
C, such that an error occurs when installing MySQL Server if MySQL Connector C \ 
is also installed. To install MySQL Server, remove any MySQL Connector C \ 
packages first.

mysql_upgrade now attempts to print more informative errors than FATAL ERROR: \ 
Upgrade failed.

These client programs now support the --enable-cleartext-plugin option: \ 
mysqlcheck, mysqldump, mysqlimport, mysqlshow. This option enables the \ 
mysql_clear_password cleartext authentication plugin. (See The Cleartext \ 
Client-Side Authentication Plugin.)

Support for building with Solaris Studio 5.13 was added.

Performance Schema digests in DIGEST_TEXT columns have ... appended to the end \ 
to indicate when statements exceed the maximum statement size and were \ 
truncated. This is also now done for statement text values in SQL_TEXT columns.

Bugs Fixed

Log message:
Changes 5.6.27:
* InnoDB: The new innodb_numa_interleave read-only configuration option allows \ 
you to enable the NUMA interleave memory policy for allocation of the InnoDB \ 
buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is \ 
set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is \ 
allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is \ 
only available on NUMA-enabled systems.
* yaSSL was upgraded to version 2.3.8.
* RPM .spec files were updated so that MySQL Server builds from source RPM \ 
packages will include the proper files to take advantage of operating system \ 
NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and \ 
yum detect this and refuse to install if that library is not installed.
* InnoDB: Reloading a table that was evicted while empty caused an \ 
AUTO_INCREMENT value to be reset.
* InnoDB: Memory allocation sanity checks were added to the memcached code.
* InnoDB: A memcached flush_all command raised an assertion. A function that \ 
starts a transaction was called from within assertion code.
* InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the \ 
correct fences when setting or unsetting the lock word.
* InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To \ 
avoid this problem, the number of calls to trx_purge() was reduced, and the \ 
trx_purge() batch size was reduced to 20.
* InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary \ 
index resulted in a constraint violation.
* InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in \ 
the leaf page than was actually available.
* InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system \ 
could result in a hang condition when running an INSERT INTO ... SELECT ... FROM \ 
tbl_name operation with the wrong tbl_name letter case. An error message is now \ 
printed and the server exits when attempting to start the server with \ 
--lower_case_table_names=0 on a case-insensitive file system.
* InnoDB: The server failed to start with an innodb_force_recovery setting \ 
greater than 3. InnoDB was set to read-only mode before redo logs were applied.
* InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong \ 
file format.
* Partitioning: CREATE TABLE statements that used an invalid function in a \ 
subpartitioning expression did not always fail gracefully as expected.
* Partitioning: Error handling for failed partitioning-related ALTER TABLE \ 
operations against non-partitioned tables was not performed correctly
* Partitioning: ALTER TABLE when executed from a stored procedure did not always \ 
work correctly with tables partitioned by RANGE.
* Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for \ 
example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock \ 
on a table led to an assert.
* Replication: If statement based logging was in use, when updating multiple \ 
tables in a single statement, a single transaction could be logged as two \ 
different transactions. This was due to the binary logging process not properly \ 
identifying statements which were operating over transactional tables. The fix \ 
ensures that they are correctly identified, even if such statements do not \ 
change the contents of the tables.

Log message:
Add memcached option (disabled by default).

Log message:
Changes 5.6.26:
* Security Fix: Due to the LogJam issue (https://weakdh.org/), OpenSSL has \ 
changed the Diffie-Hellman key length parameters for openssl-1.0.1n and up.
* Replication: When using a multi-threaded slave, each worker thread has its own \ 
queue of transactions to process. In previous MySQL versions, STOP SLAVE waited \ 
for all workers to process their entire queue. This logic has been changed so \ 
that STOP SLAVE first finds the newest transaction that was committed by any \ 
worker thread. Then, it waits for all workers to complete transactions older \ 
than that. Newer transactions are not processed. The new logic allows STOP SLAVE \ 
to complete faster in case some worker queues contain multiple transactions.
* Previously, the max_digest_length system variable controlled the maximum \ 
digest length for all server functions that computed statement digests. However, \ 
whereas the Performance Schema may need to maintain many digest values, other \ 
server functions such as MySQL Enterprise Firewall need only one digest per \ 
session. Increasing the max_digest_length value has little impact on total \ 
memory requirements for those functions, but can increase Performance Schema \ 
memory requirements significantly. To enable configuring digest length \ 
separately for the Performance Schema, its digest length is now controlled by \ 
the new performance_schema_max_digest_length system variable.
* Previously, changes to the validate_password plugin dictionary file (named by \ 
the validate_password_dictionary_file system variable) while the server was \ 
running required a restart for the server to recognize the changes. Now \ 
validate_password_dictionary_file can be set at runtime and assigning a value \ 
causes the named file to be read without a restart.

In addition, two new status variables are available. \ 
validate_password_dictionary_file_last_parsed indicates when the dictionary file \ 
was last read, and validate_password_dictionary_file_words_count indicates how \ 
many words it contains.
* Bugs fixed

Log message:
Restore SSL functionnality with OpenSSL 1.0.1p (revision bump)

This changes just bumps PKGREVISION after patches were added
in mysql56-client/patches which impact mysql56-server.

For the record, the commit log or that patches:
> With OpenSSL 1.0.1p upgrade, DH parameters below 1024 bits are now
> refused. MySQL hardcodes 512 bits DH parameters and will therefore
> fail to run SSL connexions with OpenSSL 1.0.1p
>
> Apply fix from upstream:
> \ 
https://github.com/mysql/mysql-server/commit/866b988a76e8e7e217017a7883a52a12ec5024b9