| non port: databases/mysql56-server/distinfo |
|
SVNWeb
|
Number of commits found: 39 |
|
Wed, 3 Feb 2021
|
[ 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
|
|
Mon, 19 Oct 2020
|
[ 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
|
|
Tue, 14 Jul 2020
|
[ 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
|
|
Tue, 28 Apr 2020
|
[ 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
|
|
Fri, 17 Jan 2020
|
[ 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
|
|
Thu, 2 Jan 2020
|
[ 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
|
|
Mon, 5 Aug 2019
|
[ 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
|
|
Sun, 28 Apr 2019
|
[ 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
|
|
Mon, 21 Jan 2019
|
[ 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
|
|
Sun, 28 Oct 2018
|
[ 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
|
|
Fri, 10 Aug 2018
|
[ 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
|
|
Fri, 20 Apr 2018
|
[ 10:41 mmokhi ]
databases/mysql56-server: Add missed distinfo for r467817
|
|
Wed, 17 Jan 2018
|
[ 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
|
|
Thu, 19 Oct 2017
|
[ 14:08 ale ]
Update to 5.6.38 release.
|
|
Tue, 18 Jul 2017
|
[ 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
|
|
Mon, 17 Apr 2017
|
[ 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
|
|
Thu, 19 Jan 2017
|
[ 22:29 feld ] (Only the first 10 of 15 ports in this commit are shown above.  )
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
|
|
Fri, 21 Oct 2016
|
[ 09:03 ale ]
Update to 5.6.34 release.
|
|
Fri, 16 Sep 2016
|
[ 07:38 ale ]
Update to 5.6.33 release.
|
|
Wed, 31 Aug 2016
|
[ 10:56 ale ]
Update to 5.6.32 release.
|
|
Tue, 19 Apr 2016
|
[ 15:45 ale ]
Update to 5.6.30 release.
|
|
Wed, 18 Nov 2015
|
[ 17:00 ale ]
Update to 5.6.27 release.
|
|
Sat, 15 Aug 2015
|
[ 08:17 ale ]
Update to 5.6.26 release.
|
|
Wed, 15 Jul 2015
|
[ 13:49 ale ]
Update to 5.6.25 release.
|
|
Sun, 26 Apr 2015
|
[ 13:36 ale ]
Update to 5.6.24 release.
|
|
Wed, 4 Feb 2015
|
[ 13:42 ale ]
Update to 5.6.23 release.
|
|
Wed, 3 Dec 2014
|
[ 09:40 ale ]
Update to 5.6.22 release.
|
|
Wed, 24 Sep 2014
|
[ 10:48 ale ]
Update to 5.6.21 release.
|
|
Mon, 4 Aug 2014
|
[ 14:21 ale ]
Update to 5.6.20 release.
|
|
Tue, 3 Jun 2014
|
[ 12:53 ale ]
Update to 5.6.19 release.
|
|
Mon, 31 Mar 2014
|
[ 12:29 ale ]
Update to 5.6.17 release.
|
|
Sat, 1 Feb 2014
|
[ 10:29 ale ]
Update to 5.6.16 release.
|
|
Tue, 17 Dec 2013
|
[ 11:25 ale ]
Update to 5.6.15 release and stagify.
|
|
Fri, 27 Sep 2013
|
[ 14:20 ale ]
Update to 5.6.14 release.
|
|
Mon, 12 Aug 2013
|
[ 11:47 ale ]
Update to 5.6.13 release.
|
|
Sun, 30 Jun 2013
|
[ 09:05 ale ]
Distfile rerolled to make it clearer the license of this
community edition (GPLv2).
Restore readline patch.
|
|
Mon, 10 Jun 2013
|
[ 15:12 ale ]
Update to 5.6.12 release.
|
|
Mon, 22 Apr 2013
|
[ 18:45 ale ]
Update to 5.6.11 release.
|
|
Thu, 14 Feb 2013
|
[ 15:04 ale ] (Only the first 10 of 27 ports in this commit are shown above. )
Add MySQL 5.6.
|
Number of commits found: 39 |
As an Amazon Associate I earn from qualifying purchases.