notbugAs an Amazon Associate I earn from qualifying purchases.
Want a good read? Try FreeBSD Mastery: Jails (IT Mastery Book 15)
All times are UTC
Ukraine
non port: databases/mysql80-server/pkg-plist
SVNWeb

Number of commits found: 26

Sun, 30 Apr 2023
[ 18:18 Jochen Neumeister (joneum) search for other commits by this committer Author: Toshimichi Masubuchi ]    commit hash:567557abbfc0a4deec492983ffc01da78c62bae4  commit hash:567557abbfc0a4deec492983ffc01da78c62bae4  commit hash:567557abbfc0a4deec492983ffc01da78c62bae4  567557a 
databases/mysql80-server: fix a issue with protobuf

PR:	270289
Reported by: Ting-Wei Lan <lantw44@gmail.com>
Sponsored by:	Netzkommune GmbH
Tue, 14 Feb 2023
[ 06:18 Jochen Neumeister (joneum) search for other commits by this committer ]    commit hash:fea9d2e9a495fb6938d2f420bbc2d655c4a7e596  commit hash:fea9d2e9a495fb6938d2f420bbc2d655c4a7e596  commit hash:fea9d2e9a495fb6938d2f420bbc2d655c4a7e596  fea9d2e 
databases/mysql80-*: Update to latest release 8.0.32

Bugs Fixed

    Important Change: The implementation of the max_join_size system variable,
although documented as a maximum number of rows or disk seeks, did not check the
number of rows or disk seeks directly, but instead treated max_join_size as the
maximum estimated cost to permit. While cost and row count are correlated, they
are not the same, and this could lead to unexpected results when some large
queries were allowed to proceed.

    In this release, we change how max_join_size is used, so that it now
actually limits the maximum number of row accesses in base tables. If the
estimate indicates that a greater number of rows must be read from the base
tables, an error is raised. This makes the actual behavior better reflect what
is documented. (Bug #83885, Bug #25118903)

    InnoDB: Undetectable problems after upgrade from 8.0.28, crash and
corruption.

    Any new row inserted after upgrade will have all columns added with
ALGORITHM=INSTANT materialized and have version=0.

    In the new implementation, a column added with ALGORITHM=INSTANT will fail
if the maximum possible size of a row exceeds the row size limit. So new rows
with materialized ALGORITHM=INSTANT columns will always be within row size
limit. (Bug #34558510)

    InnoDB: No more garbled UTF characters in SHOW ENGINE INNODB STATUS
(Only the first 15 lines of the commit message are shown above View all of this commit message)
Mon, 6 Feb 2023
[ 17:51 Jochen Neumeister (joneum) search for other commits by this committer ]    commit hash:6498bc6381cc493b38ff7d1ab6087a66f0ec238f  commit hash:6498bc6381cc493b38ff7d1ab6087a66f0ec238f  commit hash:6498bc6381cc493b38ff7d1ab6087a66f0ec238f  6498bc6 
databases/mysql80-*: Unbreak on i386

Fix a issue with i386:
--yplg_out: protoc-gen-yplg: Plugin killed by signal 11.
*** Error code 1

PR: 269203
Sponsored by: Netzkommmune GmbH
Sat, 29 Oct 2022
[ 07:45 Jochen Neumeister (joneum) search for other commits by this committer ]    commit hash:a2d4c050c0728f20e859bcdc4766878b2d911be7  commit hash:a2d4c050c0728f20e859bcdc4766878b2d911be7  commit hash:a2d4c050c0728f20e859bcdc4766878b2d911be7  a2d4c05 
databases/mysql80-*: Update to latest release 8.0.31

Bugs Fixed

    Incompatible Change: The service pfs_plugin_table, deprecated since MySQL
8.0.14, is removed in this release.

    Plugins or components using this service must be updated to use
pfs_plugin_table_v1 and pfs_plugin_column_* instead. (Bug #34361827)

    Important Change; Replication: Query log events filtered by the default
database whenever --replicate-do-db or --replicate-ignore-db was used included
XA START, XA END, XA COMMIT, and XA ROLLBACK (but not XA PREPARE or XA COMMIT
ONE_PHASE), regardless of the binary log format.

    This can lead to one of the issues listed here:

        When XA START or XA END was filtered out, the sequence of XA statements
within the first part of the transaction were rendered invalid, which made the
replica stop with an error.

        When XA START and XA END were preserved while XA COMMIT or XA ROLLBACK
was filtered out, then a transaction could remain in the prepared state
indefinitely on the replica.
(Only the first 15 lines of the commit message are shown above View all of this commit message)
Thu, 15 Sep 2022
[ 14:34 Jochen Neumeister (joneum) search for other commits by this committer ]    commit hash:b5daf80a266a031ac1299ec2107f53dac3f2c722  commit hash:b5daf80a266a031ac1299ec2107f53dac3f2c722  commit hash:b5daf80a266a031ac1299ec2107f53dac3f2c722  b5daf80  (Only the first 10 of 17 ports in this commit are shown above. View all ports for this commit)
databases/mysql80-*: Update to latest release 8.0.30

PR:	265468

Bugs Fixed:
- InnoDB: A TRUNCATE TABLE operation failed to remove data dictionary entries
for columns that were dropped using ALGORITHM=INSTANT.
- InnoDB: An incorrect nullable column calculation on tables with instantly
added columns caused data to be interpreted incorrectly
- InnoDB: The read_2_bytes() function in the InnoDB sources, which reads bytes
from the log buffer, returned a null pointer.
- Replication: The COUNT_TRANSACTIONS_REMOTE_IN_APPLIER_QUEUE column in the
Performance Schema table replication_group_member_stats could persistently show
transactions related to view change events (View_change_log_event) that had
already been applied. These events are queued in the Group Replication applier
channel but applied in the Group Replication recovery channel, causing a race
condition that could result in the counter decrement being lost. The increment
of the count now takes place at a more suitable point, and the counter for
COUNT_TRANSACTIONS_REMOTE_IN_APPLIER_QUEUE is also now set to zero when the
applier is not busy.
- Debug MySQL binaries can now be built using -0g and -fno-inline.

See full Changelog here:
https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-30.html

Sponsored by:	Netzkommune GmbH
Mon, 16 May 2022
[ 06:49 Loïc Bartoletti (lbartoletti) search for other commits by this committer ]    commit hash:9f0ff92f6deaa2187cdb33a27f5aebbdd2c0d71d  commit hash:9f0ff92f6deaa2187cdb33a27f5aebbdd2c0d71d  commit hash:9f0ff92f6deaa2187cdb33a27f5aebbdd2c0d71d  9f0ff92  (Only the first 10 of 16 ports in this commit are shown above. View all ports for this commit)
databases/mysql*: fix pkg-plist use share/man

Approved by:	portmgr (blanket)
Tue, 3 May 2022
[ 16:58 Jochen Neumeister (joneum) search for other commits by this committer ]    commit hash:0517374e455af49ec25820891cb387e125d2cfde  commit hash:0517374e455af49ec25820891cb387e125d2cfde  commit hash:0517374e455af49ec25820891cb387e125d2cfde  0517374 
databases/mysql80-{client, server}: Update to latest release 8.0.29

Bugs Fixed

    InnoDB: A failure occurred when attempting to purge undo records for a table
with an instantly added column. (Bug #33924532)

    InnoDB: High-priority transactions were not permitted to stop waiting when
interrupted or to timeout while waiting for a lock, preventing deadlocks from
being resolved. In cases where the blocking transaction is also high-priority,
high-priority transactions are now permitted to stop waiting when interrupted or
timeout when exceeding the lock wait timeout period. If a blocking transaction
is not high-priority, high-priority transactions wait for the blocking
transaction to release its locks. (Bug #33856332)

    InnoDB: The AIO synchronization queue used on Windows was removed. The
synchronous file I/O read-write function (SyncFileIO::execute) was revised to
handle files opened for both normal and overlapped I/O, as it does on Linux.
(Bug #33840645)

    InnoDB: Table version metadata was not reset after truncating all partitions
of a table with an instantly added column. (Bug #33822729)

    InnoDB: The srv_error_monitor_thread() function, which prints warnings about
semaphore waits, failed to handle a long semaphore wait as expected. To address
this issue, a blocking call was moved to a more appropriate location. Related
monitor thread code was simplified and improved, and missing shutdown signals
were added for several server threads.

    Enabling and disabling of the standard monitor by InnoDB is now performed
independently of the user-settable innodb_status_output variable. This change
addresses an issue in which the monitor was enabled by InnoDB in a particular
scenario but not set back to its previous value. Thanks to Yuhui Wang for the
contribution. (Bug #33789526, Bug #93878)
(Only the first 15 lines of the commit message are shown above View all of this commit message)
Tue, 22 Feb 2022
[ 19:36 Dima Panov (fluffy) search for other commits by this committer ]    commit hash:c4ac829e974e1c9b1de8348588d73a3c1a166a22  commit hash:c4ac829e974e1c9b1de8348588d73a3c1a166a22  commit hash:c4ac829e974e1c9b1de8348588d73a3c1a166a22  c4ac829 
databases/mysql80-server: bring back mysql_secure_installation (+)

Typo in patchfile leads to skip mysql_secure_installation.
Bring it back.

PR:		262123
Submitted by:	amdmi3
Approved by:	joneum (implicit)
Thu, 25 Nov 2021
[ 07:17 Jochen Neumeister (joneum) search for other commits by this committer ]    commit hash:ea739e8990792020fa9fcdc83adcd5854095ea7d  commit hash:ea739e8990792020fa9fcdc83adcd5854095ea7d  commit hash:ea739e8990792020fa9fcdc83adcd5854095ea7d  ea739e8  (Only the first 10 of 14 ports in this commit are shown above. View all ports for this commit)
databases/mysql80-*: Update to 8.0.27

Release Notes: https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-27.html

Sponsored by:	Netzkommune GmbH
Thu, 26 Aug 2021
[ 17:52 Jochen Neumeister (joneum) search for other commits by this committer ]    commit hash:84cc7ae5a0d131c991067d32bd0fae872a039cb9  commit hash:84cc7ae5a0d131c991067d32bd0fae872a039cb9  commit hash:84cc7ae5a0d131c991067d32bd0fae872a039cb9  84cc7ae 
databases/mysql80-*: update to 8.0.26

Release notes: https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-26.html

Sponsored by:	Netzkommune GmbH
Thu, 20 May 2021
[ 12:07 Dima Panov (fluffy) search for other commits by this committer ]    commit hash:c7fbbf15f3b8471c85f4c404c61fb2c9fbe1b923  commit hash:c7fbbf15f3b8471c85f4c404c61fb2c9fbe1b923  commit hash:c7fbbf15f3b8471c85f4c404c61fb2c9fbe1b923  c7fbbf1 
databases/mysql80-*: update to 8.0.25 GA release

Release notes:	https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-25.html
		https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-24.html

PR:		255937
Submitted by:	delphij@
Approved by	joneum@ (implicit)
MFH:		2021Q2
Wed, 3 Feb 2021
[ 02:09 fluffy search for other commits by this committer ] Original commit   Revision:563859 (Only the first 10 of 16 ports in this commit are shown above. View all ports for this commit)
databases/mysql80*: update to 8.0.23

Disable detect of TLSv1.3 functions - it's broken with LibreSSL

Release Notes:	https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-23.html
Requested by:	joneum
Thu, 29 Oct 2020
[ 10:20 joneum search for other commits by this committer ] Original commit   Revision:553599 (Only the first 10 of 12 ports in this commit are shown above. View all ports for this commit)
databases/mysql80-{client, server}: Update to latest release 8.0.22

Full Changelog: https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-22.html

MFH:		2020Q4
Security:	4fba07ca-13aa-11eb-b31e-d4c9ef517024
Sponsored by:	Netzkommune GmbH
Tue, 14 Jul 2020
[ 18:00 joneum search for other commits by this committer ] Original commit   Revision:542227
databases/mysql80-{client, server}: Update to latest release 8.0.21

Full Changelog: https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-21.html

Submitted by:	fluffy
MFH:		2020Q3
Security:	0ed71663-c369-11ea-b53c-d4c9ef517024
Sponsored by:	Netzkommune GmbH
Thu, 7 May 2020
[ 11:51 joneum search for other commits by this committer ] Original commit   Revision:534263 (Only the first 10 of 16 ports in this commit are shown above. View all ports for this commit)
databases/mysql80-{client, server}: Update to latest release 8.0.20

- Performance: Certain queries against tables with spatial indexes were not
performed as efficiently following an upgrade from MySQL 5.7 to MySQL 8.0.
- NDB Cluster: NDB defines one SPJ worker per node owning a primary partition of
the root table. If this table used read from any replica, DBTC put all SPJ
workers in the same DBSPJ instance, which effe
- NDB Cluster: Executing the SHOW command using an ndb_mgm client binary from
NDB 8.0.16 or earlier to access a management node running NDB 8.0.17 or later
produced the error message Unknown field: is_s
- On EL7 and EL8, CMake configuration was adjusted to look for GCC 9 before GCC
8. Because libmysqlclient ships with MySQL distributions, client applications
built against libmysqlclient on those platfo
- The max_length_for_sort_data system variable is now deprecated due to
optimizer changes that make it obsolete and of no effect.

More Infos: https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-20.html

Special thanks to: fluffy

MFH:		2020Q2
Security:	21d59ea3-8559-11ea-a5e2-d4c9ef517024 (MySQL - Server)
Security:       622b5c47-855b-11ea-a5e2-d4c9ef517024 (MySQL - Client)
Sponsored by:	Netzkommune GmbH
Wed, 15 Jan 2020
[ 20:06 joneum search for other commits by this committer ] Original commit   Revision:523155 (Only the first 10 of 19 ports in this commit are shown above. View all ports for this commit)
databases/mysql80-{client, server}: Update to latest release 8.0.19

- New FPROFILE_GENERATE and FPROFILE_USE CMake options are available for
experimenting with profile guided optimization (PGO) with GCC. See the
cmake/fprofile.cmake in a MySQL source distribution for information about using
them. These options have been tested with GCC 8 and 9, and with Clang.
- Enabling FPROFILE_USE also enables WITH_LTO (link time optimization).
- Innodb_system_rows_read, Innodb_system_rows_inserted,
Innodb_system_rows_deleted status variables were added for counting row
operations on InnoDB tables that belong to system-created schemas. The new
status variables are similar to the existing Innodb_rows_read,
Innodb_rows_inserted, Innodb_rows_deleted status variables, which count
operations on InnoDB tables that belong to both user-created and system-created
schemas.
- The new status variables are useful in replication environments where
relay_log_info_repository and master_info_repository variables are set to TABLE,
resulting in higher row operation counts on slaves due to operations performed
on the slave_master_info, slave_replay_log_info, and slave_worker_info tables,
which belong to the system-created mysql schema. For a valid comparison of
master and slave row operation counts, operations on tables in system-created
schemas can now be excluded using the count data provided by the new status
variables.

More infos: https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-19.html

Submitted by:	fluffy
Approved by:	mmokhi (maintainer, implicit)
Sponsored by:	Netzkommune GmbH
Wed, 8 Jan 2020
[ 16:47 joneum search for other commits by this committer ] Original commit   Revision:522436 (Only the first 10 of 51 ports in this commit are shown above. View all ports for this commit)
databases/mysql80-{client, server}: Update to latest release 8.0.18

switch patch-files to mysql80-server to make it easy for maintain.

Bugfix:
- CMake now enables use of fastcov if it is available. fastcov is faster than
lcov or gcov. This requires GCC and gcov versions of 9 or higher.
- The DISABLE_SHARED CMake option was unused and has been removed.
- The CMake code to find Protobuf executables now works on platforms that split
these into multiple packages.
- The new ADD_GDB_INDEX CMake option determines whether to enable generation of
a .gdb_index section in binaries, which makes loading them in a debugger faster.
The option is disabled by default. It has no effect if a linker other than lld
or GNU gold is used.
- For the INSTALL_LAYOUT CMake option, the SLES and WIN option values were not
used and have been removed.
- The max_prepared_stmt_count system variable maximum value has been increased
from 1 million (1,048,576) to 4 million (4,194,304). The default value remains
unchanged at 16,382.
- MySQL 8.0 no longer supports building using wolfSSL. All MySQL builds now use
OpenSSL.
- The RE2 library is no longer used by MySQL. The library is no longer bundled
with source distributions and the WITH_RE2 CMake option is obsolete.

More Infos: https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-18.html

A big thanks to @fluffy for his help with this update

MFH:		2020Q1
Security:	fc91f2ef-fd7b-11e9-a1c7-b499baebfeaf
Sponsored by:	Netzkommune GmbH
Tue, 10 Dec 2019
[ 10:26 joneum search for other commits by this committer ] Original commit   Revision:519655
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
Thu, 19 Sep 2019
[ 12:33 mmokhi search for other commits by this committer ] Original commit   Revision:512334 (Only the first 10 of 20 ports in this commit are shown above. View all ports for this commit)
databases/mysql80-{client, server}: Update to latest release 8.0.17
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

Delete upstream-merged patches
Change other local-patches according upstream changes

PR:		239272
Reported by:	Markus Kohlmeyer <rootservice@gmail.com>
Sponsored by:	EuroBSDCon 2019 DevSummit
Sat, 11 May 2019
[ 14:15 mmokhi search for other commits by this committer ] Original commit   Revision:501261 (Only the first 10 of 13 ports in this commit are shown above. View all ports for this commit)
databases/mysql80-{client, server}: Update to latest release 8.0.16

This update includes:
Bugfixes:
- InnoDB: Undo tablespaces remained unencrypted after enabling
    undo tablespace encryption at startup. (Bug #29477795)
- InnoDB: Problematic macros introduced with undo tablespace DDL support
    (Bug #29324132, Bug #94243).
- InnoDB: Static thread local variables defined at the wrong scope
    were not released at thread exit. (Bug #29305186)
-  Memory leaks discovered in the innochecksum  (Bug #28917614, Bug #93164).

New features:
- MySQL C API now supports asynchronous functions for
    nonblocking communication with the MySQL server.
(Only the first 15 lines of the commit message are shown above View all of this commit message)
Sat, 26 Jan 2019
[ 18:36 mmokhi search for other commits by this committer ] Original commit   Revision:491308 (Only the first 10 of 12 ports in this commit are shown above. View all ports for this commit)
databases/mysql80-{client, server}: Update to latest release 8.0.14
This update (released on Jan 21st) includes:
Bugs Fixed:
  Important Change: Fix importing a dump from a MySQL 5.7 server 8.0 failure.
    (ER_WRONG_VALUE_FOR_VAR, when an unsupported [by 8.0] SQL mode was used).
    The behavior of the server in such circumstances now depends on the setting
of the
    `pseudo_slave_mode` system variable.
    If this is false, the server rejects the mode setting with
ER_UNSUPPORTED_SQL_MODE.
    Otherwise, server just gives a warning. (Bug #90337, Bug #27828236).

  InnoDB: Properly initialize the static thread-local 'tables' variable in
    the TempTable storage engine (on Solaris X86) was not properly initialized.
    (Bug #28987365)

  InnoDB: Fix incorrect lock order caused a deadlock when one thread attempted
to
    drop a table while another created an encrypted tablespace. (Bug #28774259)

More info from upstream:
  https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-14.html

While here, Adapt some local patches with new upstream changes.

PR:		234984
Sponsored by:	The FreeBSD Foundation
Sun, 13 Jan 2019
[ 23:24 mmokhi search for other commits by this committer ] Original commit   Revision:490218 (Only the first 10 of 13 ports in this commit are shown above. View all ports for this commit)
databases/mysql80-{client, server}: Update ports to latest version 8.0.13
This update fixes several issues including CVEs.
Bug-fixes:
	- Return better error messages for OpenSSL errors
	- Incorrect copying of an integer value by X Plugin caused an
	    error relating to misaligned memory access
Improvement:
	- Important Change: X Protocol now provides a connection pooling option

Upstream notes: https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-13

While here, fix the build with GCC-based architectures too (ported from fix on
MySQL57)

Sponsored by:	The FreeBSD Foundation
Sat, 11 Aug 2018
[ 20:22 mmokhi search for other commits by this committer ] Original commit   Revision:476944 (Only the first 10 of 12 ports in this commit are shown above. View all ports for this commit)
databases/mysql80-{client, server}: Update ports to 8.0.12
This update includes Oracle Critical Patch Advisory published on July 2018
More info:
http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html#AppendixMSQL
Also:
Delete upstreamed hunks of patches.
Change local patches regarding upstream changes.

PR:		229861
Reported by:	Markus Kohlmeyer <rootservice@gmail.com>
Sponsored by:	The FreeBSD Foundation
Sat, 12 May 2018
[ 15:35 mmokhi search for other commits by this committer ] Original commit   Revision:469734 (Only the first 10 of 50 ports in this commit are shown above. View all ports for this commit)
databases/mysql80-{client,server}: Upgrade the ports to GA version 8.0.11
Fix build with LibreSSL and OpenSSL-devel ports as well

MySQL 8.0.11 is the General Availability (GA) version of MySQL 8.
MySQL since this version supports FIPS-mode, if compiled using OpenSSL, AND
    an OpenSSL library and FIPS Object Module are available at runtime.
    FIPS mode imposes conditions on cryptographic operations such as
    restrictions on acceptable encryption algorithms or requirements for longer
key lengths.
    The --ssl-fips-mode client option enables control of FIPS mode on the client
side for:
    mysql, mysqladmin, mysqlbinlog, mysqlcheck, mysqldump, mysqlimport,
mysqlpump, ...
This update includes bugfixes including (not limited to):
-InnoDB: The server was stopped before a fatal error message
    was written to the error log.
-InnoDB: An incorrect GROUP BY result was returned when using the
    TempTable storage engine and a NO PAD collation.
-InnoDB: The data retrieved from INFORMATION_SCHEMA.INNODB_COLUMNS was
    incorrect for tables containing a virtual column.

Full Release-Notes are available at:
https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-11.html
Fri, 6 Oct 2017
[ 15:44 mmokhi search for other commits by this committer ] Original commit   Revision:451389 (Only the first 10 of 32 ports in this commit are shown above. View all ports for this commit)
databases/mysql80-{server, client}: Update port to the latest release 8.0.2
Changes happened into format of --version which caused r450384

Reviewed by:	mat (mentor)
Approved by:	mat (mentor)
Sponsored by:	Netzkommune GmbH
Differential Revision:	https://reviews.freebsd.org/D12579
Sat, 7 Jan 2017
[ 20:34 lifanov search for other commits by this committer ] Original commit   Revision:430827 (Only the first 10 of 26 ports in this commit are shown above. View all ports for this commit)
add databases/mysql80-server and databases/mysql80-client

This is a development snapshot of upcoming MySQL 8.0.

PR:		215738
Submitted by:	Mahdi Mokhtari <mokhi64@gmail.com>
Reviewed by:	matthew, feld
Approved by:	matthew (mentor), feld
Differential Revision:	https://reviews.freebsd.org/D9031

Number of commits found: 26