head 1.8; access; symbols pkgsrc-2024Q2:1.7.0.32 pkgsrc-2024Q2-base:1.7 pkgsrc-2024Q1:1.7.0.30 pkgsrc-2024Q1-base:1.7 pkgsrc-2023Q4:1.7.0.28 pkgsrc-2023Q4-base:1.7 pkgsrc-2023Q3:1.7.0.26 pkgsrc-2023Q3-base:1.7 pkgsrc-2023Q2:1.7.0.24 pkgsrc-2023Q2-base:1.7 pkgsrc-2023Q1:1.7.0.22 pkgsrc-2023Q1-base:1.7 pkgsrc-2022Q4:1.7.0.20 pkgsrc-2022Q4-base:1.7 pkgsrc-2022Q3:1.7.0.18 pkgsrc-2022Q3-base:1.7 pkgsrc-2022Q2:1.7.0.16 pkgsrc-2022Q2-base:1.7 pkgsrc-2022Q1:1.7.0.14 pkgsrc-2022Q1-base:1.7 pkgsrc-2021Q4:1.7.0.12 pkgsrc-2021Q4-base:1.7 pkgsrc-2021Q3:1.7.0.10 pkgsrc-2021Q3-base:1.7 pkgsrc-2021Q2:1.7.0.8 pkgsrc-2021Q2-base:1.7 pkgsrc-2021Q1:1.7.0.6 pkgsrc-2021Q1-base:1.7 pkgsrc-2020Q4:1.7.0.4 pkgsrc-2020Q4-base:1.7 pkgsrc-2020Q3:1.7.0.2 pkgsrc-2020Q3-base:1.7 pkgsrc-2020Q2:1.6.0.12 pkgsrc-2020Q2-base:1.6 pkgsrc-2020Q1:1.6.0.8 pkgsrc-2020Q1-base:1.6 pkgsrc-2019Q4:1.6.0.10 pkgsrc-2019Q4-base:1.6 pkgsrc-2019Q3:1.6.0.6 pkgsrc-2019Q3-base:1.6 pkgsrc-2019Q2:1.6.0.4 pkgsrc-2019Q2-base:1.6 pkgsrc-2019Q1:1.6.0.2 pkgsrc-2019Q1-base:1.6 pkgsrc-2018Q4:1.5.0.22 pkgsrc-2018Q4-base:1.5 pkgsrc-2018Q3:1.5.0.20 pkgsrc-2018Q3-base:1.5 pkgsrc-2018Q2:1.5.0.18 pkgsrc-2018Q2-base:1.5 pkgsrc-2018Q1:1.5.0.16 pkgsrc-2018Q1-base:1.5 pkgsrc-2017Q4:1.5.0.14 pkgsrc-2017Q4-base:1.5 pkgsrc-2017Q3:1.5.0.12 pkgsrc-2017Q3-base:1.5 pkgsrc-2017Q2:1.5.0.8 pkgsrc-2017Q2-base:1.5 pkgsrc-2017Q1:1.5.0.6 pkgsrc-2017Q1-base:1.5 pkgsrc-2016Q4:1.5.0.4 pkgsrc-2016Q4-base:1.5 pkgsrc-2016Q3:1.5.0.2 pkgsrc-2016Q3-base:1.5 pkgsrc-2016Q2:1.4.0.16 pkgsrc-2016Q2-base:1.4 pkgsrc-2016Q1:1.4.0.14 pkgsrc-2016Q1-base:1.4 pkgsrc-2015Q4:1.4.0.12 pkgsrc-2015Q4-base:1.4 pkgsrc-2015Q3:1.4.0.10 pkgsrc-2015Q3-base:1.4 pkgsrc-2015Q2:1.4.0.8 pkgsrc-2015Q2-base:1.4 pkgsrc-2015Q1:1.4.0.6 pkgsrc-2015Q1-base:1.4 pkgsrc-2014Q4:1.4.0.4 pkgsrc-2014Q4-base:1.4 pkgsrc-2014Q3:1.4.0.2 pkgsrc-2014Q3-base:1.4 pkgsrc-2014Q2:1.3.0.4 pkgsrc-2014Q2-base:1.3 pkgsrc-2014Q1:1.3.0.2 pkgsrc-2014Q1-base:1.3 pkgsrc-2013Q4:1.2.0.2 pkgsrc-2013Q4-base:1.2 pkgsrc-2013Q3:1.1.0.6 pkgsrc-2013Q3-base:1.1 pkgsrc-2013Q2:1.1.0.4 pkgsrc-2013Q2-base:1.1 pkgsrc-2013Q1:1.1.0.2 pkgsrc-2013Q1-base:1.1; locks; strict; comment @# @; 1.8 date 2024.08.05.06.30.26; author wiz; state dead; branches; next 1.7; commitid bBHFyVW9uHUXcBkF; 1.7 date 2020.07.07.20.18.20; author adam; state Exp; branches; next 1.6; commitid zx23Gtn2e1XIGbfC; 1.6 date 2019.01.20.18.04.49; author maya; state Exp; branches; next 1.5; commitid g40tTX6HGB047y8B; 1.5 date 2016.08.04.10.09.08; author adam; state Exp; branches 1.5.22.1; next 1.4; commitid Jxxd0AwgqntknYgz; 1.4 date 2014.08.10.15.11.57; author adam; state Exp; branches 1.4.16.1; next 1.3; commitid bIheneSZaTIhmPLx; 1.3 date 2014.02.13.14.38.08; author jperkin; state Exp; branches; next 1.2; commitid pYD0nWgOozKOSWox; 1.2 date 2013.12.03.20.02.42; author adam; state Exp; branches; next 1.1; commitid W0d5936M5AQa0Jfx; 1.1 date 2013.02.13.21.00.03; author adam; state Exp; branches; next ; 1.5.22.1 date 2019.01.29.13.01.46; author bsiegert; state Exp; branches; next ; commitid Oc05OrnAapzs9G9B; 1.4.16.1 date 2016.09.13.19.23.04; author bsiegert; state Exp; branches; next ; commitid upw2QBb1Wd66aamz; desc @@ 1.8 log @mysql* 5.6, 5.7: remove As proposed on pkgsrc-users on July 26. These versions are unsupported by upstream since 2018 and 2020 respectively. @ text @$NetBSD: patch-CMakeLists.txt,v 1.7 2020/07/07 20:18:20 adam Exp $ Split configuration between mysql-client and mysql-server. Build with newer DTrace. --- CMakeLists.txt.orig 2016-07-11 09:19:51.000000000 +0000 +++ CMakeLists.txt @@@@ -202,6 +202,7 @@@@ IF(DISABLE_SHARED) SET(WITHOUT_DYNAMIC_PLUGINS 1) ENDIF() OPTION(ENABLED_PROFILING "Enable profiling" ON) +OPTION(ENABLE_DTRACE "Include support for DTrace probes" OFF) OPTION(CYBOZU "" OFF) OPTION(BACKUP_TEST "" OFF) OPTION(WITHOUT_SERVER OFF) @@@@ -495,7 +496,6 @@@@ ADD_SUBDIRECTORY(vio) ADD_SUBDIRECTORY(regex) ADD_SUBDIRECTORY(mysys) ADD_SUBDIRECTORY(mysys_ssl) -ADD_SUBDIRECTORY(libmysql) IF(WITH_UNIT_TESTS) # Visual Studio 11 needs this extra flag in order to compile gmock. @@@@ -513,16 +513,16 @@@@ IF(WITH_UNIT_TESTS) ENDIF() ADD_SUBDIRECTORY(extra) -ADD_SUBDIRECTORY(client) ADD_SUBDIRECTORY(sql/share) ADD_SUBDIRECTORY(libservices) -IF(UNIX) +IF(WITHOUT_SERVER) + ADD_SUBDIRECTORY(libmysql) + ADD_SUBDIRECTORY(client) + ADD_SUBDIRECTORY(scripts) ADD_SUBDIRECTORY(man) -ENDIF() - -IF(NOT WITHOUT_SERVER) ADD_SUBDIRECTORY(tests) +ELSE() ADD_SUBDIRECTORY(sql) OPTION (WITH_EMBEDDED_SERVER "Compile MySQL with embedded server" OFF) IF(WITH_EMBEDDED_SERVER) @@@@ -533,7 +533,6 @@@@ ENDIF() # scripts/mysql_config depends on client and server targets loaded above. # It is referenced by some of the directories below, so we insert it here. -ADD_SUBDIRECTORY(scripts) IF(NOT WITHOUT_SERVER) ADD_SUBDIRECTORY(mysql-test) @ 1.7 log @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. @ text @d1 1 a1 1 $NetBSD: patch-CMakeLists.txt,v 1.6 2019/01/20 18:04:49 maya Exp $ @ 1.6 log @mysql56-client: change the default configuration to avoid information disclosure to a malicious server. Backport of upstream commit: https://github.com/mysql/mysql-server/commit/98ed3d8bc8ad724686d26c7bf98dced3bd1777be Exploit method described here: https://gwillem.gitlab.io/2019/01/17/adminer-4.6.2-file-disclosure-vulnerability/ @ text @d1 1 a1 1 $NetBSD: patch-CMakeLists.txt,v 1.5 2016/08/04 10:09:08 adam Exp $ a5 4 Backport of https://github.com/mysql/mysql-server/commit/98ed3d8bc8ad724686d26c7bf98dced3bd1777be Avoid disclosure of files from a client to a malicious server, described here: https://gwillem.gitlab.io/2019/01/17/adminer-4.6.2-file-disclosure-vulnerability/ a15 9 @@@@ -345,7 +346,7 @@@@ IF(REPRODUCIBLE_BUILD) ENDIF() OPTION(ENABLED_LOCAL_INFILE - "If we should should enable LOAD DATA LOCAL by default" ${IF_WIN}) +"If we should should enable LOAD DATA LOCAL by default" OFF) MARK_AS_ADVANCED(ENABLED_LOCAL_INFILE) OPTION(WITH_FAST_MUTEXES "Compile with fast mutexes" OFF) @ 1.5 log @Changes 5.6.32: Bugs Fixed InnoDB: Full-text search auxiliary tables could be dropped by one session while being access by another. InnoDB: Selecting full-text index information schema tables for a deleted table caused a segmentation fault. InnoDB: Rollback of a full-text index synchronization operation raised an assertion. The rollback operation attempted to acquire a mutex still held by the background synchronization thread. InnoDB: Setting innodb_monitor_enable to all did not enable all counters. Replication: After issuing a PURGE BINARY LOGS statement, if the binary log index file was not available, for example because it had been opened by another application such as MEB, the server could stop unexpectedly. Although this situation was rare, the handling has been made more robust to avoid unexpected halts and more informative errors are provided. Replication: When using row-based replication and InnoDB, replication slaves reverted to using an older locking scheme when a transaction had already acquired an AUTOINC lock related to a LOAD FILE or INSERT ... SELECT type of statement, reducing replication slave performance. The fix ensures that sql_command is set correctly for any of the DML events such as WRITE_ROWS_EVENT, UPDATE_EVENT, and DELETE_EVENT. Replication: A MySQL version 5.5 slave does not have a server_uuid and replication identified servers by their server_id. Starting from MySQL version 5.6, replication masters detected a zombie dump thread based only on a slave's server_uuid value, under the assumption that each slave has a unique UUID. Connecting a MySQL 5.5 slave to a MySQL 5.6 and later master meant that the master was unable to detect zombie dump threads that were created to serve slaves running versions older than MySQL 5.6. The fix ensures that a master now first checks if a slave has a server_uuid set. If it is set, zombie dump thread detection happens based on the slave's UUID. If a slave's server_uuid is not set, zombie dump thread detection happens based on server_id. Replication: With slave_skip_errors enabled there were still special cases when slave errors were not being correctly ignored. For example: When opening and locking a table failed. When field conversions failed on a server running row-based replication. In these cases the error was considered critical and it was not respecting the state of slave_skip_errors. The fix ensures that with slave_skip_errors enabled, all errors reported during applying a transaction are correctly handled. This means that in such a set up, upon receiving an error with the log_warnings option set to greater than 1, if the error can be ignored then the warning is printed into the error log and the server continues as it does in the case of other ignored errors. Replication: When using statement-based or mixed binary logging format with --read-only=ON, it was not possible to modify temporary tables. MySQL Server upgrades performed using RPM packages failed when upgrading from MySQL 5.5 Community to MySQL 5.6 Community or MySQL 5.5 Commercial to MySQL 5.6 Commercial. The code for reading character set information from Performance Schema statement events tables (for example, events_statements_current) did not prevent simultaneous writing to that information. As a result, the SQL query text character set could be invalid, which could result in a server exit. Now an invalid character set causes SQL_TEXT column truncation. A buffer overflow in the regex library was fixed. Certain arguments to NAME_CONST() could cause a server exit. For unit-testing with the MySQL test suite, the make unit-test command is no longer available. The ctest program should be used instead. See Unit Tests Added to Main Test Runs. ST_Distance() could raise an assertion for NULL return values. With the query cache enabled, executing a prepared statement with CURSOR_TYPE_READ_ONLY and then again with CURSOR_TYPE_NO_CURSOR caused the server to return an error. mysql_real_connect() was not thread-safe when invoked with the MYSQL_READ_DEFAULT_FILE or MYSQL_READ_DEFAULT_GROUP option enabled. Installing MySQL from a yum or zypper repository resulted in /var/log/mysqld.log being created with incorrect user and group permissions. If a stored function updated a view for which the view table had a trigger defined that updated another table, it could fail and report an error that an existing table did not exist. 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). For multibyte character sets, LOAD DATA could fail to allocate space correctly and ignore input rows as a result. @ text @d1 1 a1 1 $NetBSD: patch-CMakeLists.txt,v 1.4 2014/08/10 15:11:57 adam Exp $ d6 4 d20 10 a29 1 @@@@ -462,7 +463,6 @@@@ ADD_SUBDIRECTORY(vio) d37 1 a37 1 @@@@ -480,16 +480,16 @@@@ IF(WITH_UNIT_TESTS) d59 1 a59 1 @@@@ -500,7 +500,6 @@@@ ENDIF() @ 1.5.22.1 log @Pullup ticket #5900 - requested by maya databases/mysql55-client: security fix databases/mysql56-client: security fix databases/mysql57-client: security fix Revisions pulled up: - databases/mysql55-client/Makefile 1.32 - databases/mysql55-client/distinfo 1.63 - databases/mysql55-client/patches/patch-CMakeLists.txt 1.7 - databases/mysql55-client/patches/patch-cmake_build__configurations_mysql__release.cmake 1.1 - databases/mysql55-client/patches/patch-sql_sys__vars.cc 1.1 - databases/mysql56-client/Makefile 1.28 - databases/mysql56-client/distinfo 1.49 - databases/mysql56-client/patches/patch-CMakeLists.txt 1.6 - databases/mysql56-client/patches/patch-cmake_build__configurations_mysql__release.cmake 1.1 - databases/mysql56-client/patches/patch-sql_sys__vars.cc 1.3 - databases/mysql57-client/Makefile 1.19 - databases/mysql57-client/distinfo 1.27 - databases/mysql57-client/patches/patch-CMakeLists.txt 1.2 - databases/mysql57-client/patches/patch-cmake_build__configurations_mysql__release.cmake 1.1 - databases/mysql57-client/patches/patch-sql_sys__vars.cc 1.1 --- Module Name: pkgsrc Committed By: maya Date: Sun Jan 20 18:03:25 UTC 2019 Modified Files: pkgsrc/databases/mysql55-client: Makefile distinfo pkgsrc/databases/mysql55-client/patches: patch-CMakeLists.txt Added Files: pkgsrc/databases/mysql55-client/patches: patch-cmake_build__configurations_mysql__release.cmake patch-sql_sys__vars.cc Log Message: mysql55-client: change the default configuration to avoid information disclosure to a malicious server. Backport of upstream commit: https://github.com/mysql/mysql-server/commit/98ed3d8bc8ad724686d26c7bf98dced3bd1777be Exploit method described here: https://gwillem.gitlab.io/2019/01/17/adminer-4.6.2-file-disclosure-vulnerability/ --- Module Name: pkgsrc Committed By: maya Date: Sun Jan 20 18:04:49 UTC 2019 Modified Files: pkgsrc/databases/mysql56-client: Makefile distinfo pkgsrc/databases/mysql56-client/patches: patch-CMakeLists.txt Added Files: pkgsrc/databases/mysql56-client/patches: patch-cmake_build__configurations_mysql__release.cmake patch-sql_sys__vars.cc Log Message: mysql56-client: change the default configuration to avoid information disclosure to a malicious server. Backport of upstream commit: https://github.com/mysql/mysql-server/commit/98ed3d8bc8ad724686d26c7bf98dced3bd1777be Exploit method described here: https://gwillem.gitlab.io/2019/01/17/adminer-4.6.2-file-disclosure-vulnerability/ --- Module Name: pkgsrc Committed By: maya Date: Sun Jan 20 18:22:10 UTC 2019 Modified Files: pkgsrc/databases/mysql57-client: Makefile distinfo pkgsrc/databases/mysql57-client/patches: patch-CMakeLists.txt Added Files: pkgsrc/databases/mysql57-client/patches: patch-cmake_build__configurations_mysql__release.cmake patch-sql_sys__vars.cc Log Message: mysql57-client: change the default configuration to avoid information disclosure to a malicious server. Backport of upstream commit: https://github.com/mysql/mysql-server/commit/98ed3d8bc8ad724686d26c7bf98dced3bd1777be Exploit method described here: https://gwillem.gitlab.io/2019/01/17/adminer-4.6.2-file-disclosure-vulnerability/ @ text @d1 1 a1 1 $NetBSD$ a5 4 Backport of https://github.com/mysql/mysql-server/commit/98ed3d8bc8ad724686d26c7bf98dced3bd1777be Avoid disclosure of files from a client to a malicious server, described here: https://gwillem.gitlab.io/2019/01/17/adminer-4.6.2-file-disclosure-vulnerability/ d16 1 a16 10 @@@@ -345,7 +346,7 @@@@ IF(REPRODUCIBLE_BUILD) ENDIF() OPTION(ENABLED_LOCAL_INFILE - "If we should should enable LOAD DATA LOCAL by default" ${IF_WIN}) +"If we should should enable LOAD DATA LOCAL by default" OFF) MARK_AS_ADVANCED(ENABLED_LOCAL_INFILE) OPTION(WITH_FAST_MUTEXES "Compile with fast mutexes" OFF) @@@@ -495,7 +496,6 @@@@ ADD_SUBDIRECTORY(vio) d24 1 a24 1 @@@@ -513,16 +513,16 @@@@ IF(WITH_UNIT_TESTS) d46 1 a46 1 @@@@ -533,7 +533,6 @@@@ ENDIF() @ 1.4 log @Changes 5.6.20: Security Fix: The linked OpenSSL library for the MySQL 5.6 Commercial Server has been updated from version 1.0.1g to version 1.0.1h. Versions of OpenSSL prior to and including 1.0.1g are reported to be vulnerable to CVE-2014-0224. This change does not affect the Oracle-produced MySQL Community build of MySQL Server 5.6, which uses the yaSSL library instead. DTrace Support MySQL now includes DTrace support on Oracle Linux 6 or higher with UEK kernel. If DTrace is present, server builds will detect it with no special CMake options required. For information about using DTrace on MySQL, see Tracing mysqld Using DTrace. InnoDB Notes Important Change: Redo log writes for large, externally stored BLOB fields could overwrite the most recent checkpoint. The 5.6.20 patch limits the size of redo log BLOB writes to 10% of the redo log file size. The 5.7.5 patch addresses the bug without imposing a limitation. For MySQL 5.5, the bug remains a known limitation. As a result of the redo log BLOB write limit introduced for MySQL 5.6, innodb_log_file_size should be set to a value greater than 10 times the largest BLOB data size found in the rows of your tables plus the length of other variable length fields (VARCHAR, VARBINARY, and TEXT type fields). Failing to do so could result in “Row size too large” errors. No action is required if your innodb_log_file_size setting is already sufficiently large or your tables contain no BLOB data. Functionality Added or Changed Replication: The new system variable binlog_impossible_mode controls what happens if the server cannot write to the binary log, for example, due to a file error. For backward compatibility, the default for binlog_impossible_mode is IGNORE_ERROR, meaning the server logs the error, halts logging, and continues updates to the database. Setting this variable to ABORT_SERVER makes the server halt logging and shut down if it cannot write to the binary log. CMake support was updated to handle CMake version 3. New Debian7, Ubuntu12.04, and Ubuntu14.04 distribution support that was introduced with 5.6.17 now comes with the platform-specific packaging source placed under the packaging directory, in the deb-precise, deb-wheezy, and deb-trusty directories. Support for LinuxThreads has been removed from the source code. LinuxThreads was superseded by NPTL in Linux 2.6. By default, mysql_install_db creates a my.cnf file in the installation base directory using a template. This may be undesireable for some deployments. To enable this behavior to be suppressed, mysql_install_db now supports a --keep-my-cnf option to preserve any existing my.cnf file and not create a new my.cnf file. The mysqlhotcopy utility is now deprecated and will be removed in a future version of MySQL. Among the reasons for this: It works only for the MyISAM and ARCHIVE storage engines; it works on Unix but not Windows. Alternatives include mysqldump and MySQL Enterprise Backup. The timed_mutexes system variable has no effect and is deprecated. Bugs Fixed @ text @d1 1 a1 1 $NetBSD: patch-CMakeLists.txt,v 1.3 2014/02/13 14:38:08 jperkin Exp $ d6 1 a6 1 --- CMakeLists.txt.orig 2014-07-18 15:48:39.000000000 +0000 d8 1 a8 1 @@@@ -215,6 +215,7 @@@@ IF(DISABLE_SHARED) d16 1 a16 1 @@@@ -472,7 +473,6 @@@@ ADD_SUBDIRECTORY(vio) d23 2 a24 2 ADD_SUBDIRECTORY(unittest) @@@@ -491,16 +491,16 @@@@ IF(WITH_UNIT_TESTS) d46 1 a46 1 @@@@ -511,7 +511,6 @@@@ ENDIF() @ 1.4.16.1 log @Pullup ticket #5101 - requested by maya databases/mysql55-client: security fix databases/mysql56-client: security fix Revisions pulled up: - databases/mysql55-client/Makefile.common 1.54 - databases/mysql55-client/distinfo 1.52 - databases/mysql55-server/PLIST 1.44 - databases/mysql56-client/Makefile.common 1.35 - databases/mysql56-client/distinfo 1.37 - databases/mysql56-client/patches/patch-CMakeLists.txt 1.5 - databases/mysql56-server/PLIST 1.26 --- Module Name: pkgsrc Committed By: adam Date: Wed Sep 7 13:13:36 UTC 2016 Modified Files: pkgsrc/databases/mysql55-client: Makefile.common distinfo pkgsrc/databases/mysql55-server: PLIST Log Message: Changes in MySQL 5.5.52 (2016-09-06) Bugs Fixed ---------- Replication: mysqlbinlog --read-from-remote-server log1 log2 was opening a new \ connection for log2 without freeing the connection used for log1. Thanks to Laurynas \ Biveinis for the contribution. (Bug 81675, Bug 23540182) For mysqld_safe, the argument to --malloc-lib now must be one of the directories \ /usr/lib, /usr/lib64, /usr/lib/i386-linux-gnu, or /usr/lib/x86_64-linux-gnu. In \ addition, the --mysqld and --mysqld-version options can be used only on the command \ line and not in an option file. (Bug 24464380) It was possible to write log files ending with .ini or .cnf that later could be \ parsed as option files. The general query log and slow query log can no longer be \ written to a file ending with .ini or .cnf. (Bug 24388753) Privilege escalation was possible by exploiting the way REPAIR TABLE used temporary \ files. (Bug 24388746) Certain internal character-handling functions could fail to handle a too-large \ character and cause a server exit. (Bug 23296299) A blank server name in CREATE SERVER statements produced a server exit rather than an \ error. (Bug 23295288) The optimizer failed to check a function return value for an area calculation, \ leading to a server exit. (Bug 23280059) A prepared statement that used a parameter in the select list of a derived table that \ was part of a join could cause a server exit. (Bug 22392374, Bug 24380263) MEDIUMINT columns used in operations with long integer values could result in buffer \ overflow. (Bug 19984392) EINTR handling in the client library has been fixed so that interrupted read and \ write calls are retried. Previously, EINTR was ignored. (Bug 82019, Bug 23703570) --- Module Name: pkgsrc Committed By: adam Date: Wed Sep 7 12:58:25 UTC 2016 Modified Files: pkgsrc/databases/mysql56-client: Makefile.common distinfo pkgsrc/databases/mysql56-server: PLIST Log Message: Changes in MySQL 5.6.33 (2016-09-06) Test Suite Notes ---------------- In mysql-test-run.pl, a limit of 50 was imposed on the number of workers for parallel \ testing, which on systems with more than 50 CPUs resulted in exhaustion of unique \ thread IDs. The ID-exhaustion problem has been corrected, and the limit of 50 on \ number of workers has been lifted. Thanks to Daniel Black for the patch on which this \ change was based. Additionally, these changes were made: To avoid idle workers, the number of parallel workers now is limited to the number of \ tests. Previously, if --parallel=auto was given and the MTR_MAX_PARALLEL environment \ variable was not set, a limit of 8 was imposed on the number of parallel workers. \ This limit has been lifted. (Bug 22342399, Bug 79585) Functionality Added or Changed ------------------------------ CMake support for compiling with Solaris Studio 12.5 was added. (Bug 82249, Bug \ 24303829, Bug 81274, Bug 23212938) Bugs Fixed ---------- InnoDB: An operation that dropped and created a full-text search table raised an \ assertion. (Bug 24315031) InnoDB: Accessing full-text search auxiliary tables while dropping the indexed table \ raised an assertion. (Bug 24009272) InnoDB: An online DDL operation on a table with indexed BLOB columns raised an \ assertion during logging of table modifications. (Bug 23760086) Replication: mysqlbinlog --read-from-remote-server log1 log2 was opening a new \ connection for log2 without freeing the connection used for log1. Thanks to Laurynas \ Biveinis for the contribution. (Bug 81675, Bug 23540182) Replication: With binlog_row_image=FULL, when updating single tables temporary tables \ were unnecessarily being used. The fix ensures single table update follows the same \ pattern as multi-table update. (Bug 79867, Bug 22510353) For mysqld_safe, the argument to --malloc-lib now must be one of the directories \ /usr/lib, /usr/lib64, /usr/lib/i386-linux-gnu, or /usr/lib/x86_64-linux-gnu. In \ addition, the --mysqld and --mysqld-version options can be used only on the command \ line and not in an option file. (Bug 24464380) It was possible to write log files ending with .ini or .cnf that later could be \ parsed as option files. The general query log and slow query log can no longer be \ written to a file ending with .ini or .cnf. (Bug 24388753) Privilege escalation was possible by exploiting the way REPAIR TABLE used temporary \ files. (Bug 24388746) If the basedir system variable was set at server startup from the command line or \ option file, the value was not normalized (on Windows, / was not replaced with /). \ (Bug 23747899, Bug 82125) In-place ALTER TABLE operations which when executed separately caused no table \ rebuild could when combined into a single statement result in a table rebuild. (Bug \ 23475211, Bug 81587) A blank server name in CREATE SERVER statements produced a server exit rather than an \ error. (Bug 23295288) A prepared statement that used a parameter in the select list of a derived table that \ was part of a join could cause a server exit. (Bug 22392374, Bug 24380263) MEDIUMINT columns used in operations with long integer values could result in buffer \ overflow. (Bug 19984392) A spurious ER_NO_SUCH_TABLE error could occur when attempting to execute a prepared \ CREATE TABLE ... SELECT statement that used a temporary table in the FROM clause and \ called a stored function. The same error could occur for a nonprepared version of the \ statement if used in a stored procedure when the procedure was re-executed. (Bug \ 16672723, Bug 68972) EINTR handling in the client library has been fixed so that interrupted read and \ write calls are retried. Previously, EINTR was ignored. (Bug 82019, Bug 23703570) @ text @d1 1 a1 1 $NetBSD$ d6 1 a6 1 --- CMakeLists.txt.orig 2016-07-11 09:19:51.000000000 +0000 d8 1 a8 1 @@@@ -202,6 +202,7 @@@@ IF(DISABLE_SHARED) d16 1 a16 1 @@@@ -462,7 +463,6 @@@@ ADD_SUBDIRECTORY(vio) d23 2 a24 2 # Visual Studio 11 needs this extra flag in order to compile gmock. @@@@ -480,16 +480,16 @@@@ IF(WITH_UNIT_TESTS) d46 1 a46 1 @@@@ -500,7 +500,6 @@@@ ENDIF() @ 1.3 log @Support building with recent DTrace (v1.11 or newer). Patch from https://bugs.launchpad.net/percona-server/+bug/1196460 @ text @d1 1 a1 1 $NetBSD: patch-CMakeLists.txt,v 1.2 2013/12/03 20:02:42 adam Exp $ d6 1 a6 1 --- CMakeLists.txt.orig 2013-11-17 18:02:53.000000000 +0000 d8 1 a8 1 @@@@ -205,6 +205,7 @@@@ IF(DISABLE_SHARED) d16 1 a16 1 @@@@ -443,7 +443,6 @@@@ ADD_SUBDIRECTORY(vio) d24 1 a24 1 @@@@ -458,9 +457,13 @@@@ IF(WITH_UNIT_TESTS) d28 5 a32 2 -IF(NOT WITHOUT_SERVER) - ADD_SUBDIRECTORY(tests) d35 1 a35 1 ADD_SUBDIRECTORY(client) d37 5 a41 2 + ADD_SUBDIRECTORY(man) + ADD_SUBDIRECTORY(tests) d44 9 a52 3 ADD_SUBDIRECTORY(sql/share) ADD_SUBDIRECTORY(libservices) @@@@ -473,11 +476,7 @@@@ IF(NOT WITHOUT_SERVER) a53 10 ADD_SUBDIRECTORY(mysql-test/lib/My/SafeProcess) ADD_SUBDIRECTORY(support-files) - ADD_SUBDIRECTORY(scripts) ADD_SUBDIRECTORY(sql-bench) - IF(UNIX) - ADD_SUBDIRECTORY(man) - ENDIF() IF(EXISTS ${CMAKE_SOURCE_DIR}/internal/CMakeLists.txt) ADD_SUBDIRECTORY(internal) ENDIF() @ 1.2 log @Changes 5.6.15: * Previously, MySQL Server distributions included the MySQL Reference Manual in Info format (the Docs/mysql.info file). Because the license for the manual restricts redistribution, its inclusion in Community packages caused problems for downstream redistributors, such as those who create Linux distributions. Community distributions of MySQL Server no longer include the mysql.info file, to make the repackaging and redistribution process easier (for example, the source tarball and its checksum can be used directly). This change applies to all source and binary Community packaging formats. Commercial (Enterprise) distributions are unchanged. * Incompatible Change: Several statement instruments in the setup_instruments table are used by the Performance Schema during the early stages of statement classification before the exact statement type is known. * The Performance Schema now instruments the read/write lock Delegate::lock * A new CMake option, WITH_ASAN, permits enabling address sanitization for compilers that support it. * The hash function used for metadata locking was modified to reduce overhead. * Bugs Fixed @ text @d1 1 a1 1 $NetBSD: patch-CMakeLists.txt,v 1.1 2013/02/13 21:00:03 adam Exp $ d4 1 d8 8 @ 1.1 log @Changes 5.6.10: http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-10.html @ text @d1 1 a1 1 $NetBSD: patch-CMakeLists.txt,v 1.3 2012/10/01 15:54:40 adam Exp $ d5 1 a5 1 --- CMakeLists.txt.orig 2013-01-22 16:54:49.000000000 +0000 d7 1 a7 1 @@@@ -367,7 +367,6 @@@@ ADD_SUBDIRECTORY(vio) d15 1 a15 1 @@@@ -378,9 +377,13 @@@@ IF(WITH_UNIT_TESTS) d31 1 a31 1 @@@@ -393,11 +396,7 @@@@ IF(NOT WITHOUT_SERVER) @