01:40 Muhammad Moinur Rahman (bofh) 

databases/mysql56-*: Sunset

2023-06-30 databases/mysql56-*: Upstream support ended in February 2021

Approved by:	portmgr (blanket)

    1fb68a4

01:58 fluffy 

databases/mysql56*: update to 5.6.51

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

Release Notes:	https://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-51.html
Requested by:	joneum

 

18:44 joneum 

databases/mysq56-{client, server}: Update to latest release 5.6.50

Full Changelog: https://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-50.html

Sponsored by:	Netzkommune GmbH

 

09:23 joneum 

databases/mysq56-{client, server}: Update to latest release 5.6.49

Full changelog: https://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-49.html

MFH:		2020Q3
Security:	0ed71663-c369-11ea-b53c-d4c9ef517024
Sponsored by:	Netzkommune GmbH

 

21:08 joneum 

databases/mysql56-{client, server}: Update to latest release 5.6.48

Bugfix:
- 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.

More Infos: https://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-48.html

MFH:		2020Q2
Security:	21d59ea3-8559-11ea-a5e2-d4c9ef517024 (MySQL - Server)
Security:	622b5c47-855b-11ea-a5e2-d4c9ef517024 (MySQL - Client)
Sponsored by:	Netzkommune GmbH

 

14:26 joneum 

databases/mysql56-{client, server}: Update to latest release 5.6.47

Bugs Fixed:
- Replication: When GTIDs are enabled on a replication master and slave, and the
slave connects to the master with the MASTER_AUTO_POSITION=1 option set, the
master must send the slave all the transactions that the slave has not already
received, committed, or both. If any of the transactions that should be sent by
the master have been already purged from the master's binary log, the master
sends the error ER_MASTER_HAS_PURGED_REQUIRED_GTIDS (1789) to the slave, and
replication does not start.
  The message provided for the error ER_MASTER_HAS_PURGED_REQUIRED_GTIDS has
been changed to provide advice on the correct action in this situation, which is
for the slave to replicate the missing transactions from another source, or for
the slave to be replaced by a new slave created from a more recent backup. The
message advises that the master's binary log expiration period can be revised to
avoid the situation in future. In addition, the master now identifies the GTIDs
of the purged transactions and supplies them in its error log in the warning
message ER_FOUND_MISSING_GTIDS (11809), so that you do not need to calculate the
missing GTIDs manually.
- With multiple sessions executing concurrent INSERT ... ON DUPLICATE KEY UPDATE
statements into a table with an AUTO_INCREMENT column but not specifying the
AUTO_INCREMENT value, inserts could fail with a unique index violation.
- A SELECT using a WHERE condition of the form A AND (B OR C [OR ...]) resulting
in an impossible range led to an unplanned exit of the server.
- An incomplete connection packet could cause clients not to properly initialize
the authentication plugin name.

Approved by:	mmokhi (maintainer, implicit)
MFH:		2020Q1
Security:	a6cf65ad-37d2-11ea-a1c7-b499baebfeaf
Sponsored by:	Netzkommune GmbH

 

20:00 joneum 

databases/mysql56-{client, server}: Update to latest release 5.6.46

Bugfix:
 -  Improper locking during storage engine initialization could cause a server
exit.
 - A query with a WHERE clause whose predicate contained a numeric value in
scientific notation was not handled correctly.
 - VS2019 produced compilation errors with debug compilation selected due to use
of the /ZI flag. Now /Z7 is used instead.
 - For MySQL Community Edition, the cipher order specified by the client was
used in preference to the order on the server side, unless the server was confi
 - Password masking was incomplete for SHOW PROCESSLIST and some
INFORMATION_SCHEMA and Performance Schema tables.
 - The -DWITH_EXAMPLE_STORAGE_ENGINE=1 CMake option was ignored but should not
have been. If -DWITH_EXAMPLE_STORAGE_ENGINE=0 is given, the EXAMPLE storage e

More Info: https://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-46.html

Approved by:	mmokhi (maintainer, implicit)
MFH:		2020Q1
Security:	fc91f2ef-fd7b-11e9-a1c7-b499baebfeaf
Sponsored by:	Netzkommune GmbH

 

23:21 mmokhi 

databases/mysq56-{client, server}: Update to 5.6.45

This update includes security fixes which are
mentioned on upstream critical patch report.
Further info:
https://www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.html#AppendixMSQL

PR:		239571
Reported by:	serg@tmn.ru
Sponsored by:	Platform.sh

 

21:24 mmokhi 

databases/mysql56-{client, server}: Update to latest release 5.6.44
This update includes
Bugfix:
- InnoDB: The INDEX_LENGTH value in INFORMATION_SCHEMA.TABLES
    was not updated when adding an index
- MySQL 5.6 did not build with maintainer mode enabled with GCC 7
- A damaged mysql.user table could cause a server exit
- mysqladmin shutdown did not wait for mysqld to shut down
More info: https://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-44.html

Security Fix:
CVE-2019-1559, CVE-2018-3123 and other fixes.
More info:
https://www.oracle.com/technetwork/security-advisory/cpuapr2019-5072813.html#AppendixMSQL<Paste>

PR:		237399
Reported by:	Brent Busby <brent@jfi.uchicago.edu>
Sponsored by:	The FreeBSD Foundation

 

20:28 mmokhi 

databases/mysql56-{client, server}: Update to latest release 5.6.43
This update (released on Jan 21st) includes:
Bugfix:
  -Correct the handling of quotes for identifiers in
    ROLLBACK TO SAVEPOINT statements.
  -Don't permit creation of dbs with same name as redo log file
    (Bug #28867993).
  -Use strncmp() instead of memcmp() for comparing logfile names
    (prevent the uninitialized memory as result).

More info from upstream:
    https://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-43.html

Sponsored by:	The FreeBSD Foundation

 

21:26 mmokhi 

databases/mysql56-{client, server}: Upgrade to new release 5.6.42
    Upstream Bug #27788907, Bug #90264 fixed
Bug Fixes:
     Raised assertion during an OPTIMIZE TABLE operation for InnoDB: Bug
#27753193
     For MEMORY tables, memory overflow errors could occur: Bug #27799513
     Incorrectly handled very long table keys on replication slaves: Bug
#27930505

More info on update:
https://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-42.html

Sponsored by:	The FreeBSD Foundation

 

22:05 mmokhi 

mysql56-{client, server}: Update ports to 5.6.41
This update includes Oracle Critical Patch Advisory published on July 2018
More info:
http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html#AppendixMSQL

Sponsored by:	The FreeBSD Foundation

 

10:41 mmokhi 

databases/mysql56-server: Add missed distinfo for r467817

 

22:35 mmokhi 

databases/mysql56-{client, server}: Update to 5.6.39
This update fixes bugs like CVE-2018-2696, CVE-2018-2562,
and CVE-2018-2583 in MySQL protocol by upstream

PR:		225240
Sponsored by:	Netzkommune GmbH

 

14:08 ale 

Update to 5.6.38 release.

 

16:59 mmokhi 

databases/mysql56-{server client}: Update to latest 5.6.37
This release contains
features:
* The mysql client now supports a --binary-as-hex option for
    binary data (Bug #25340722, Bug #84391)
* mysqlaccess now looks for its configuration file only in the
    SYSCONFDIR directory and /etc. (Bug #25043674)

And bugfixes:
* mysqld: failed to start the server if the --datadir option was specified
    with a relative path name. (Bug #25364806)
* InnoDB: The server allocated memory unnecessarily for an operation that
    rebuilt the table. (Bug #25573565, Bug #85043)
* mysqldump: could write database names in USE statements
    incorrectly. (Bug #25998635)

Reviewed by:	mat (mentor)
Approved by:	mat (mentor)
Sponsored by:	Netzkommune GmbH
Differential Revision:	https://reviews.freebsd.org/D11638

 

14:54 mmokhi 

databases/mysql56-{server client}: Update to latest 5.6.36
Also Delete patches that merged/fixed by upstream.
And fix some no-longer-valid (but needed) patches.

Reviewed by:	feld, mat (mentors)
Approved by:	feld (mentor)
Differential Revision:	https://reviews.freebsd.org/D10392

 

22:29 feld 

databases/mysql56: Update to 5.6.35

- Port improvements from MySQL 5.7 port
- Use system libs instead of bundled
- Fix many open PRs
- Change MAINTAINER

PR:		216244 192657 198812 199751 205093
PR:		209618 211248 205983 209338

 

09:03 ale 

Update to 5.6.34 release.

 

07:38 ale 

Update to 5.6.33 release.

 

10:56 ale 

Update to 5.6.32 release.

 

15:45 ale 

Update to 5.6.30 release.

 

17:00 ale 

Update to 5.6.27 release.

 

08:17 ale 

Update to 5.6.26 release.

 

13:49 ale 

Update to 5.6.25 release.

 

13:36 ale 

Update to 5.6.24 release.

 

13:42 ale 

Update to 5.6.23 release.

 

09:40 ale 

Update to 5.6.22 release.

 

10:48 ale 

Update to 5.6.21 release.

 

14:21 ale 

Update to 5.6.20 release.

 

12:53 ale 

Update to 5.6.19 release.

 

12:29 ale 

Update to 5.6.17 release.

 

10:29 ale 

Update to 5.6.16 release.

 

11:25 ale 

Update to 5.6.15 release and stagify.

 

14:20 ale 

Update to 5.6.14 release.

 

11:47 ale 

Update to 5.6.13 release.

 

09:05 ale 

Distfile rerolled to make it clearer the license of this
community edition (GPLv2).
Restore readline patch.

 

15:12 ale 

Update to 5.6.12 release.

 

18:45 ale 

Update to 5.6.11 release.

 

15:04 ale 

Add MySQL 5.6.