===> The following configuration options are available for mysql57-server-5.7.44_2:
====> Permissible Storage Engines (to compile statically into the server)
ARCHIVE=off: Compile "Archive Storage" statically in server
BLACKHOLE=off: Compile "Blackhole Storage" statically in server
EXAMPLE=off: Compile "Example Storage" statically in server
FEDERATED=off: Compile "Federated Storage" statically in server
INNOBASE=off: Compile "InnoDB Storage" statically in server
PARTITION=off: Compile "Partitioning support Storage" statically in server
PERFSCHEMA=off: Compile "Performance Schema Storage" statically in server
====> Default features knobs
PERFSCHM=on: Enable "Performance Schema" by default (High RAM usage)
===> Use 'make config' to modify these settings
Initial password for first time use of MySQL is saved in $HOME/.mysql_secret
ie. when you want to use "mysql -u root -p" first you should see password
in /root/.mysql_secret
MySQL57 has a default /usr/local/etc/mysql/my.cnf,
remember to replace it with your own
or set `mysql_optfile="$YOUR_CNF_FILE` in rc.conf.
If upgrading
Remember to run mysql_upgrade the first time you start the MySQL server
after an upgrade from an earlier version.
databases/mysql57-{client,server}: Use bundled protobuf
- Bump PORTREVISION for dependency and package change
mysql57 failed to build with protobuf 22+. Since the maintainer already
committed
a fix [1] on mysql80 to use bundled protobuf, we take the same approach to avoid
build error with protobuf 22+ from ports tree and potential issue.
PR: 270289
Reference: https://cgit.freebsd.org/ports/commit/?id=567557abbfc0a4deec492983ffc01da78c62bae4
[1]
databases/mysql57-*: update to 5.7.44
Important:
MySQL 5.7.44 is the final release of the MySQL 5.7 series.
MySQL 5.7 users are encouraged to upgrade to the latest MySQL 8.0 or
MySQL Innovation release.
Bugs Fixed
InnoDB: Fixed processing of single character tokens by a FTS parser plugin.
Our thanks to Shaohua Wang for the contribution. (Bug #35432973)
InnoDB: The last detected deadlock section of the engine status log
(Only the first 15 lines of the commit message are shown above )
databases/mysq57-{client, server}: Update to latest release 5.7.43
Bugs Fixed
Group Replication: After one machine halted and restarted in a
three-node MySQL InnoDB Cluster, one node failed to start; after
restarting all nodes, the cluster shut down unexpectedly.
Our thanks to Zetang Zeng for the contribution. (Bug #34976442)
Fortified parsing of the network packet data sent by the server to
the client. (Bug #35374491)
Some floating-point literals were not always handled correctly. (Bug
(Only the first 15 lines of the commit message are shown above )
databases/mysql57-{client|server}: Mark IGNORE with OpenSSL 3
OpenSSL 3 has been merged into OSVERSION 1400092 so also mark IGNORE
for 14 and OSVERSION 1400092 onwards.
Approved by: portmgr (blanket)
Sponsored by: The FreeBSD Foundation
databases/mysql57-*: Update to 5.7.42
Bugs Fixed
InnoDB: Prevent online DDL operations from accessing out-of-bounds
memory. (Bug #34750489, Bug #108925)
Replication: Some binary log events were not always handled
correctly. (Bug #34617506)
Replication: Setting binlog_order_commits to OFF could lead to a
missed GTID in the next binary log file's Previous_gtids event.
Our thanks to Yewei Xu and the Tencent team for the contribution.
(Bug #109485, Bug #34930969)
(Only the first 15 lines of the commit message are shown above )
databases/mysql57-*: Update to 5.7.41
Bugs Fixed
Replication: Issuing STOP SLAVE SQL_THREAD while the SQL thread was handling
a transaction caused replication to stop immediately, instead of waiting 60
seconds for the event group to complete before shutting down the SQL thread as
expected.
The root cause of this issue was due to the internal variable storing the
last event start time not being reset after the SQL thread was restarted.
We fix this by resetting the variable holding the last event start time
whenever the SQL thread is started. (Bug #33646899)
Replication: The relay_log_space_limit system variable is a 64-bit value,
but its valid maximum was specified internally as that of a 32-bit value. (Bug
#106323, Bug #33799840)
Some remote connections to the server were not handled correctly. This issue
arose as the result of a previous fix for an issue with
require_secure_transport. (Bug #34857411)
References: This issue is a regression of: Bug #34094706.
(Only the first 15 lines of the commit message are shown above )
databases/mysql57-server: Mark deprecated
* Chasing security fixes no longer provided by Oracle after 5.7.41
* 2019-10-14: Support EOL for MySQL 5.7 on FreeBSD
Due to very low demand, MySQL has stopped development and support for
MySQL 5.7 on FreeBSD. Users of FreeBSD are requested to upgrade to recent
versions of MySQL. Source and binaries for previously released versions
will continue to be available from the archives.
Obtained from: https://www.mysql.com/support/eol-notice.html
databases/mysql57-server: fix build with clang 15 on i386
During an exp-run for llvm 15 (see bug 265425), it turned out that
databases/mysql57-server failed to build with clang 15, on i386:
In file included from
/wrkdirs/usr/ports/databases/mysql57-server/work/mysql-5.7.40/rapid/plugin/x/src/xpl_plugin.cc:30:
In file included from
/wrkdirs/usr/ports/databases/mysql57-server/work/mysql-5.7.40/rapid/plugin/x/src/xpl_session.h:31:
In file included from
/wrkdirs/usr/ports/databases/mysql57-server/work/mysql-5.7.40/rapid/plugin/x/ngs/include/ngs/client_session.h:30:
In file included from
/wrkdirs/usr/ports/databases/mysql57-server/work/mysql-5.7.40/rapid/plugin/x/ngs/include/ngs/protocol_encoder.h:31:
In file included from
/wrkdirs/usr/ports/databases/mysql57-server/work/mysql-5.7.40/rapid/plugin/x/ngs/include/ngs/protocol/page_pool.h:34:
In file included from
/wrkdirs/usr/ports/databases/mysql57-server/work/mysql-5.7.40/rapid/plugin/x/ngs/include/ngs_common/atomic.h:29:
In file included from
/wrkdirs/usr/ports/databases/mysql57-server/work/mysql-5.7.40/boost/boost_1_59_0/boost/atomic.hpp:12:
In file included from
/wrkdirs/usr/ports/databases/mysql57-server/work/mysql-5.7.40/boost/boost_1_59_0/boost/atomic/atomic.hpp:20:
In file included from
/wrkdirs/usr/ports/databases/mysql57-server/work/mysql-5.7.40/boost/boost_1_59_0/boost/atomic/fences.hpp:21:
In file included from
/wrkdirs/usr/ports/databases/mysql57-server/work/mysql-5.7.40/boost/boost_1_59_0/boost/atomic/detail/operations.hpp:17:
(Only the first 15 lines of the commit message are shown above )
databases/mysql*-{client, server}: Remove NDEBUG
As of 3c5189a0fd4c82addfb659024bf28c5006bf88f7 there shouldn't be a need
to define NDEBUG by hand when using CMake.
Reported by: dizzy
Sponsored by: Netzkommune GmbH
databases/mysql57-*: Update to 5.7.40
Changelog:
Important Change: The linked OpenSSL library for MySQL Server has been updated
to version 1.1.1q. Issues fixed in OpenSSL version 1.1.1q are described at
https://www.openssl.org/news/cl111.txt and
https://www.openssl.org/news/vulnerabilities.html. (Bug #34414695)
The linked curl library for MySQL Server (Enterprise Edition) has been updated
to version 7.84.0. (Bug #34138733, Bug #34614578)
MySQL Server’s AES_ENCRYPT() and AES_DECRYPT() functions now support the use
of a key derivation function (KDF) to create a cryptographically strong secret
key from information such as a password or a passphrase that you pass to the
function. The derived key is used to encrypt and decrypt the data, and it
remains in the MySQL Server instance and is not accessible to users. Using a KDF
is highly recommended, as it provides better security than specifying your own
premade key or deriving it by a simpler method when you use the function. The
functions support HKDF (available from OpenSSL 1.1.0), for which you can specify
an optional salt and context-specific information to include in the keying
material, and PBKDF2 (available from OpenSSL 1.0.2), for which you can specify
an optional salt and set the number of iterations used to produce the key.
Bugs Fixed
InnoDB: In debug builds, a descending b-tree scan raised a debug assertion
failure. (Bug #34144951)
InnoDB: An index latch order violation in dict_table_x_lock_indexes() caused an
assertion failure. (Bug #32912868)
(Only the first 15 lines of the commit message are shown above )
databases/and_others: Fix rc.d script comment
I found this typo while researching something else. It seems to have
propgated around the tree.
Approved by: blanket
bases/mysql57-*: Update ti 5.7.39
Bugs Fixed:
- InnoDB: A 4GB tablespace file size limit on Windows 32-bit systems has
been removed. The limit was due to an incorrect calculation performed
while extending the tablespace. (Bug #28934351)
- Replication: The write sets extracted by MySQL Replication from
transactions when the transaction_write_set_extraction system variable
is enabled (which is the default) are extracted from primary keys,
unique keys, and foreign keys. They are used to detect dependencies
and conflicts between transactions. Previously, write sets involving
multi-column foreign keys were incorrectly identifying each column as
a separate foreign key. The issue has now been fixed and foreign key
write sets include all referenced key columns. (Bug #34095747, Bug
(Only the first 15 lines of the commit message are shown above )
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
databases/mysql57-*: Update ti 5.7.38
Bugs Fixed
InnoDB: A missing null pointer check for an index instance caused a failure.
(Bug #33600109)
InnoDB: Purge threads processed undo records of an encrypted table for which
the tablespace was not loaded, causing a failure. (Bug #32586721)
InnoDB: Incorrect AUTO_INCREMENT values were generated when the maximum
integer column value was exceeded. The error was due to the maximum column value
not being considered. The previous valid AUTO_INCREMENT value should have been
returned in this case, causing a duplicate key error. (Bug #87926, Bug
#26906787)
Partitioning: In some cases, establishing a connection to MySQL server could
fail if the .ibd file for a partition was missing. (Bug #33459653)
Statements that cannot be parsed (due, for example, to syntax errors) are no
longer written to the slow query log. (Bug #33732907)
It was not possible to revoke the DROP privilege on the Performance Schema.
(Bug #33578113)
A page cleaner thread timed out as it waited for an exclusive lock on an
index page held by a full-text index creation operation on a large table. (Bug
#33101844)
A memory leak occurred if mysqldump was used on more than one table with the
--order-by-primary option. The memory allocated for sorting each table’s rows
is now freed after every table, rather than only once. (Bug #30042589, Bug
#96178)
mysqld_safe log message textual errors were corrected. Thanks to Bin Wang at
China Mobile for the contribution. (Bug #106590, Bug #33903639)
Full Changelog: https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-38.html
Sponsored by: Netzkommune GmbH
Fix CONFLICTS entries of multiple ports
There have been lots of missing CONFLICTS_INSTALL entries, either
because conflicting ports were added without updating existing ports,
due to name changes of generated packages, due to mis-understanding
the format and semantics of the conflicts entries, or just due to
typoes in package names.
This patch is the result of a comparison of all files contained in
the official packages with each other. This comparison was based on
packages built with default options and may therefore have missed
further conflicts with optionally installed files.
Where possible, version numbers in conflicts entries have been
generalized, some times taking advantage of the fact that a port
(Only the first 15 lines of the commit message are shown above )
*/*: Remove redundant '-*' from CONFLICTS definitions
The conflict checks compare the patterns first against the package
names without version (as reported by "pkg query "%n"), then - if
there was no match - agsinst the full package names including the
version (as reported by "pkg query "%n-%v").
Approved by: portmgr (blanket)
databases/mysql57-server: don't use LLD for linking on powerpc
LLD currently fails:
ld: error: relocation refers to a discarded section:
.rodata._ZN5boost6detail8function15functor_managerINS_9algorithm6detail13token_finderFINS4_10is_any_ofFIcEEEEE7managerERKNS1_15function_bufferERSA_NS1_30functor_manager_operation_typeEN4mpl_5bool_ILb0EEE
>>> defined in
../../archive_output_directory/libmysqlpump_lib.a(object_filter.cc.o)
>>> referenced by object_filter.cc
>>> object_filter.cc.o:(.got2+0x108) in archive
../../archive_output_directory/libmysqlpump_lib.a
ld: error: relocation refers to a discarded section:
.rodata._ZN5boost6detail8function15functor_managerINS_9algorithm6detail13token_finderFINS4_10is_any_ofFIcEEEEE7managerERKNS1_15function_bufferERSA_NS1_30functor_manager_operation_typeEN4mpl_5bool_ILb0EEE
>>> defined in
../../archive_output_directory/libmysqlpump_lib.a(sql_formatter.cc.o)
>>> referenced by sql_formatter.cc
>>> sql_formatter.cc.o:(.got2+0x130) in archive
../../archive_output_directory/libmysqlpump_lib.a
ld: error: relocation refers to a discarded section:
.rodata._ZN5boost6detail8function15functor_managerINS_9algorithm6detail13token_finderFINS4_10is_any_ofFIcEEEEE7managerERKNS1_15function_bufferERSA_NS1_30functor_manager_operation_typeEN4mpl_5bool_ILb0EEE
>>> defined in ../../archive_output_directory/libmysqlpump_lib.a(table.cc.o)
>>> referenced by table.cc
>>> table.cc.o:(.got2+0x50) in archive
../../archive_output_directory/libmysqlpump_lib.a
clang++: error: linker command failed with exit code 1 (use -v to see
invocation)
In file included from
/usr/obj/usr/ports/databases/mysql57-client/work/mysql-5.7.30/vio/viosslfactories.c:29:
/usr/obj/usr/ports/databases/mysql57-client/work/mysql-5.7.30/include/my_openssl.h:55:30:
error: use of undeclared identifier 'OPENSSL_INIT_NO_ATEXIT'
return OPENSSL_init_crypto(OPENSSL_INIT_NO_ATEXIT, NULL);
This fix a problem with libressl
PR: 246070
MFH: 2020Q2
Sponsored by: Netzkommune GmbH
databases/mysq56-{client, server}: Update to latest release 5.7.30
Bugs Fixed:
- InnoDB: The row_upd_clust_rec_by_insert function, which marks a clustered
index record as deleted and inserts an updated version of the record into the
clustered index, passed an incorrect n_ext value (the total number of external
fields) to lower level functions, causing an assertion failure.
- InnoDB: An operation performed with the innodb_buffer_pool_evict debug
variable set to uncompressed caused an assertion failure.
- InnoDB: An add column operation caused an assertion failure. The failure was
due to a dangling pointer.
- nnoDB: Updating certain InnoDB system variables that take string values raised
invalid read errors during Valgrind testing.
- InnoDB: An insert statement on a table with a spatial index raised a record
type mismatch assertion due to a tuple corruption.
- InnoDB: A function that calculates undo log record size could calculate an
incorrect length value in the case of a corrupted undo log record, resulting in
a malloc failure. Assertion code was added to detect incorrect calculations.
- Replication: While an SQL statement was in the process of being rewritten for
the binary log so that sensitive information did not appear in plain text, if a
SHOW PROCESSLIST statement was used to inspect the query, the query could become
corrupted when it was written to the binary log, causing replication to stop.
The process of rewriting the query is now kept private, and the query thread is
updated only when rewriting is complete.
- Replication: When a GRANT or REVOKE statement is only partially executed, an
incident event is logged in the binary log, which makes the replication slave's
applier thread stop so that the slave can be reconciled manually with the
master. Previously, if a failed GRANT or REVOKE statement was the first
statement executed in the session, no GTID was applied to the incident event
(because the cache manager did not yet exist for the session), causing an error
on the replication slave. Also, no incident event was logged in the situation
where a GRANT statement created a user but then failed because the privileges
had been specified incorrectly, again causing an error on the replication slave.
Both these issues have now been fixed.
- Replication: When a replication slave has a generated column that the master
does not have in that table, with a secondary index on the generated column, the
generated expression should be evaluated and the value stored by the storage
engine in the secondary index. When row-based binary logging is in use, the
replication slave assigns default values to any fields that are not in the
master's definition of the table. In the case of a generated column, which does
not have a default value, the slave was previously assigning a null or a zero
value to the column. This value was then stored by the storage engine in the
secondary index, causing both the table and the index to become corrupted. To
fix this issue, generated columns in a table on a replication slave are now
re-evaluated before the values are sent to the storage engine.
- 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.
Full Changelog: https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-30.html
MFH: 2020Q2
Security: 21d59ea3-8559-11ea-a5e2-d4c9ef517024 (MySQL - Server)
Security: 622b5c47-855b-11ea-a5e2-d4c9ef517024 (MySQL - Client)
Sponsored by: Netzkommune GmbH
databases/mysq56-{client, server}: Update to latest release 5.7.29
Bugs Fixed:
- InnoDB: os_file_get_parent_dir warnings were encountered when compiling MySQL
with GCC 9.2.0.
- InnoDB: An internal function (btr_push_update_extern_fields()) used to fetch
newly added externally stored fields and update them during a pessimistic update
or when going back to a previous version of a record was no longer required.
Newly added externally stored fields are updated by a different function. Also,
the method used to determine the number of externally stored fields was
corrected.
- InnoDB: A comparison function found two records to be equal when attempting to
merge non-leaf pages of a spatial index. The function was unable to handle this
unexpected condition, which resulted in a long semaphore wait and an eventual
assertion failure.
- Replication: A memory leak could occur when a failed replication group member
tried to rejoin a minority group and was disallowed from doing so.
- Docker packages were missing the LDAP authentication plugins.
More Infos: https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-29.html
Approved by: mmokhi (maintainer, implicit)
MFH: 2020Q1
Security: a6cf65ad-37d2-11ea-a1c7-b499baebfeaf
Sponsored by: Netzkommune GmbH
Get rid of useless and unfilled
libdata/pkgconfig/LIBMYSQL_OS_OUTPUT_NAME-NOTFOUND.pc
for server bundle, right .pc file is already installed by client package
PR: 242488
Reported by: fluffy
Approved by: mmokhi (maintainer, implicit)
Sponsored by: Netzkommune GmbH
/ram/usr/ports/databases/mysql57-client/work/mysql-5.7.28/vio/viosslfactories.c
/ram/usr/ports/databases/mysql57-client/work/mysql-5.7.28/vio/viosslfactories.c:505:27:
error: use of undeclared identifier 'SSL_OP_NO_TLSv1_3'
| SSL_OP_NO_TLSv1_3
This fix a problem with libressl
PR: 242474
Approved by: mmokhi (maintainer, implicit)
Sponsored by: Netzkommune GmbH
databases/mysq56-{client, server}: Update to latest release 5.7.27
This update includes security fixes on issues that are
mentioned on upstream critical patch report.
Further info:
https://www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.html#AppendixMSQL
PR: 239271
Submitted by: Greg Veldman <freebsd@gregv.net>
Reported by: Markus Kohlmeyer <rootservice@gmail.com>
Sponsored by: Platform.sh
Bump PORTREVISION for ports depending on the canonical version of GCC
as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.
PR: 238330
databases/mysql57-{client, server}: Update to latest release 5.7.26
This update includes:
Bugfix:
- InnoDB: Optimized internal temporary tables did not support
in-place UPDATE operations
- InnoDB: A function called by a CREATE TABLE thread attempted access after
free()
- InnoDB: The INDEX_LENGTH value in INFORMATION_SCHEMA.TABLES
was not updated when adding an index
- The authentication_ldap_simple plugin could enforce authentication incorrectly
More info: https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-26.html
Security Fix:
CVE-2019-2632, CVE-2019-1559, CVE-2018-3123, and other fixes.
More info:
https://www.oracle.com/technetwork/security-advisory/cpuapr2019-5072813.html#AppendixMSQL
PR: 237399
Reported by: Brent Busby <brent@jfi.uchicago.edu>
Sponsored by: The FreeBSD Foundation
Similar to other SQL ports, add -fpermissive when compiling using GCC
to fix compilation.
PR: 235690
Submitted by: Piotr Kubaj
Approved by: portmgr (tier-2 blanket)
databases/mysql57-{client, server}: Update to latest release 5.7.25
This update (released on Jan 21st) includes:
Deprecation:
-Tools resolveip and resolve_stack_dump utilities are now deprecated.
(Will be removed on MySQL8.0).
Bugfix:
-Fix a memory leak caused by a dangling pointer. (Bug #28693568)
-Fix mishandling of SIGHUP by server could result in a server exit.
(Bug #27966483, Bug #90742).
-Correct potential incorrect out-of-memory checks performed by parser.
(Bug #25633994).
More info from upstream:
https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-25.html
PR: 234983
Reported by: Markus Kohlmeyer < rootservice@gmail.com >
Sponsored by: The FreeBSD Foundation
databases/mysql57-server: Fix build for i386
Make MySQL build-script assume that FreeBSD's Clang (on i386)
doesn't have "atomic_*" functions builtin implemented.
This is added to cmake/os/FreeBSD.cmake to make the merge for upstream easier.
PR: 229605
Reported by: gbromov@gmail.com
Sponsored by: The FreeBSD Foundation
Change cmake default behaviour to outsource.
Ports that build out of source now simply can use "USES=cmake"
instead of "USES=cmake:outsource". Ports that fail to build
out of source now need to specify "USES=cmake:insource".
I tried to only set insource where explictely needed.
PR: 232038
Exp-run by: antoine
Bump PORTREVISION for ports depending on the canonical version of GCC
defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t
GCC 8.2 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, as a double check, everything INDEX-11 showed depending on lang/gcc7.
PR: 231590
databases/mysql57-{client, server}: Fix inconsistencies on texinfo and man files
This is port of r485867 from mysql56-{client, server}
Differential Revision: The FreeBSD Foundation
databases/mysql57-{client, server}: Update to 5.7.24
Delete merged-to-upstream FreeBSD patches, edit half-merged ones.
Upstream bugfixes:
Regression of Bug #27753193 (segfault on ALTER TABLE adding primary key,
InnoDB)
Query interruption during a lock wait caused an error: Bug #28068293
Raised assertion during an OPTIMIZE TABLE operation for InnoDB: Bug
#27753193
More info on update:
https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-24.html
PR: 232685
Reported by: Markus Kohlmeyer <rootservice@gmail.com>
Sponsored by: The FreeBSD Foundation
mysql57-server: Fix build with LibreSSL 2.7
PR: 230527
Submitted by: Markus Kohlmeyer <rootservice@gmail.com>
Reported by: Markus Kohlmeyer <rootservice@gmail.com>
Sponsored by: The FreeBSD Foundation
mysql57-{client, server}: Update ports to 5.7.23
This update includes Oracle Critical Patch Advisory published on July 2018
More info:
http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html#AppendixMSQL
PR: 229860
Submitted by: Dani <i.dani@outlook.com<
Reported by: Markus Kohlmeyer <rootservice@gmail.com>
Reviewed by: brnrd , koobs
Sponsored by: The FreeBSD Foundation
Bump PORTREVISION for ports depending on the canonical version of GCC
in the ports tree (via Mk/bsd.default-versions.mk and lang/gcc) which
has now moved from GCC 6 to GCC 7 by default.
This includes ports
- featuring USE_GCC=yes or USE_GCC=any,
- featuring USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and those
- with USES=compiler specifying one of openmp, nestedfct, c11, c++0x,
c++11-lib, c++11-lang, c++14-lang, c++17-lang, or gcc-c++11-lib.
PR: 222542
mysql57-{client, server}: Update port to 5.7.22
This update includes fixes for multiple CVEs including:
CVE-2018-2755 in replication component, MySQL protocol
CVE-2018-2805 in GIS extention
CVE-2018-2782 in InnoDB
and more info on
http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html#AppendixMSQL
PR: 227621
Reported by: Markus Kohlmeyer <rootservice@gmail.com>
Sponsored by: Netzkommune GmbH
databases/mysql57-server: Fix ${name}_limits regression on 11-STABLE
This is port of r467049 (that was done on mysql56-server)
PR: 227435
Reported by: 0mp
databases/mysql57-server: Adapt ${name}_limits to the new mechanism
Regarding to the changes to rc.subr(8) it is no longer necessary to
define a resource limiting logic in service scripts.
limits(1) is now run by default and its configuration is handled
via the "${name}_limits" variable.
This however causes collision of variable names and also is not
compatible with the old mechanism.
This fixes the rc-script of mysql57 for the bases with both
old and new mechanism.
(This is port of the r466505 [and r466506])
PR: 227230
Submitted by: 0mp
Reported by: 0mp
Differential Revision: Netzkommune GmbH
databases/mysql57-server: Delete no-longer-needed patch.
The patch was casting variables to right size on previous versions
Issue seems fixed by upstream it's not needed anymore.
It also fixes a warning/error for from Clang6 on the port build.
databases/mysql56-{client, server}: Update to 5.7.21
This update fixes bugs like CVE-2018-2696, CVE-2018-2562, CVE-2018-2640,
CVE-2018-2668, CVE-2017-3737 (and more) in MySQL protocol by upstream.
Delete local patches (CMake plugin macros) that are merged by upstream.
PR: 225195
Sponsored by: Netzkommune GmbH
databases/mysql57-{client, server}: Complete Upgrade of to 5.7.20 (as done by
port-secteam in r452458)
Using FreeBSD-ports libcurl and protobuf instead of bundled ones
This upgrade includes:
-Deprecation of these syntax constructs for table and column:
.col_name
.tbl_name
.tbl_name.col_name
-Bugfix of memory-leak in mysqldump
Reviewed by: mat (mentor)
Approved by: mat (mentor)
Sponsored by: Netzkommune GmbH
Differential Revision: https://reviews.freebsd.org/D12712
Bump PORTREVISION for ports depending on the canonical version of GCC
(via Mk/bsd.default-versions.mk and lang/gcc) which has moved from
GCC 5.4 to GCC 6.4 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c++11-lib, c++11-lang,
c++14-lang, c++0x, c11, or gcc-c++11-lib.
PR: 219275
MySQL ports: Extend CONFLICTS_INSTALL in conflicting ports.
databases/mysqlwsrep56-server has been present for some time and
databases/mysqlwsrep57-server has been added recently. Both ports
conflict with other MySQL server ports and this has been reflected
in databases/mysqlwsrep5[67]-server/Makefile but must also be
reflected in all conflicting ports' Makefiles as well.
The conflicting ports are:
databases/mariadb100-server
databases/mariadb101-server
databases/mariadb102-server
databases/mariadb55-server
databases/mysql55-server
databases/mysql56-server
(Only the first 15 lines of the commit message are shown above )
databases/mysql57-{server client}: Fix broken SASL/LDAP integration on newest
5.7.19 upgrade
-Add a SASL/LDAP option for mysql57-client
-Fix plugin.cmake for "FreeBSD != Linux" case
For new plugin, MySQL build assumes everything is MacOS or Windows or Linux.
This breaks upgrades when you have SASL/LDAP client-library installed.
Because it "Decides" that you "Want" SASL/LDAP support and tries to build it.
PR: 220865
Submitted by: mmokhi
Reported by: Vladimir Omelchuk <admin@vladiom.com.ua>
Reviewed by: mat, feld (mentors)
Approved by: feld (mentor)
MFH: 2017Q3
Differential Revision: https://reviews.freebsd.org/D11667
Make ninja opt-out in cmake.mk
Using ninja instead of make (1) can lead to significant speed ups while
building.
Therefore switch from having the ninja generator opt-in to having it opt-out.
Previously cmake-ports that wanted to use ninja could set
CMAKE_NINJA=yes
now, ports that do not work with ninja can set
cmake:<existing args>,noninja
Note, that needing this should be an exception and most often points to a broken
cmake of the port.
The ports using cmake were modified
* removed USES=gmake, if ninja is used
* removed MAKE_ARGS, if ninja is used
* added the cmake-argument noninja if necessary
PR: 219629
PR: 213331
Exp-run by: antoine
Reviewed by: rakuco
Differential Revision: https://reviews.freebsd.org/D10748
