non port: databases/mysql57-server/distinfo |
Number of commits found: 34 |
Sunday, 31 Dec 2023
|
00:06 Muhammad Moinur Rahman (bofh)
databases/mysql57-*: Remove expired port
e716c4e |
Friday, 17 Nov 2023
|
18:04 Jochen Neumeister (joneum)
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
was only showing 1024 characters for the combined thread and query
information. Fixing by removing the printed query string limit. (Bug
Some complex queries using multiple common table expressions were
not always handled correctly. (Bug #34900334)
References: This issue is a regression of: Bug #34377854.
Full Changelog: https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-44.html
Sponsored by: Netzkommune GmbH
dca82fc |
Thursday, 16 Nov 2023
|
19:08 Jochen Neumeister (joneum) Author: User Joneum
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
Executing a query with an implicit aggregation should return exactly
one row, unless the query has a HAVING clause that filters out the row,
but a query with a HAVING clause which evaluated to FALSE sometimes
ignored this, and returned a row regardless. (Bug #14272020)
During optimization, range-select tree creation uses logic which
differs based on the left-hand side of the IN() predicate. For a field
item, each value on the right-hand side is added to an OR tree to create
the necessary expression. In the case of a row item comparison (example:
WHERE (a,b) IN ((n1,m1), (n2, m2), ...)), an expression in disjunctive
normal form (DNF) is needed. A DNF expression is created by adding an
AND tree with column values to an OR tree for each set of RHS values,
but instead the OR tree was added to the AND tree causing the tree merge
to require exponential time due to O(n2) runtime complexity. (Bug
Changelog: https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-43.html
Sponsored by: Netzkommune GmbH
cc257a5 |
Tuesday, 6 Jun 2023
|
10:35 Jochen Neumeister (joneum)
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)
A client setting the character set to an impermissible client
character set (ucs2, utf16, utf16le, or utf32) could cause unexpected
behavior when the client used an authentication plugin. (Bug #35054579)
The scope of the connect_timeout limit was extended to full-packet
reads. (Bug #33723597)
References: See also: Bug #34574013.
Using --single-transaction with mysqldump version 5.7.41 required
either the RELOAD or FLUSH_TABLES privilege. This requirement now
applies only when both gtid_mode=ON (default OFF) and with
--set-gtid-purged = ON|AUTO (default AUTO). (Bug #109685, Bug #109701,
Bug #34993824, Bug #34998910, Bug #35020512)
Full Changelog: https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-42.html
Sponsored by: Netzkommune GmbH
e6db1ed |
Tuesday, 11 Apr 2023
|
16:52 Jochen Neumeister (joneum)
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.
The linked OpenLDAP library for MySQL Server (Enterprise edition) was
updated to version 2.5.13. (Bug #34815046)
The bundled zlib library has been upgraded to zlib 1.2.13; zlib 1.2.13 is
now the minimum zlib version supported. (Bug #34711762, Bug #34711758)
Stack overruns could be erroneously reported when using the thread pool
under heavy load. The race condition causing this in the thread pool has been
avoided with an additional thread group ID check. (Bug #34414959)
Data and GTIDs backed up by mysqldump were inconsistent when the options
--single-transaction and --set-gtid-purged=ON were both used. This was because
GTID_EXECUTED was fetched at the end of the dump, at which point the GTIDs on
the server could have increased already. With this fix, a FLUSH TABLES WITH READ
LOCK is performed at the beginning of the dump, and GTID_EXECUTED fetched
immediately after, to ensure that its value is consistent with the snapshot
taken by mysqldump.
Full Changelog: https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-41.html
Sponsored by: Netzkommune GmbH
e6137ea |
Friday, 28 Oct 2022
|
16:19 Jochen Neumeister (joneum)
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)
InnoDB: A TRUNCATE TABLE operation failed to free an acquired mutex in specific
cases. (Bug #107858, Bug #34380370)
The server did not always process nested views as expected. (Bug #33876690)
mysqlpump might not be given the correct permissions to use derived tables
(tables that are generated by a query FROM clause), causing the dump process to
stop if these were present. Derived tables are now handled separately and
privileges are set for them. (Bug #33866103)
When using --log-timestamps=SYSTEM, ISO 8601 timestamps in log messages did not
take account of daylight saving time. (Bug #28632725, Bug #32893161)
The GRANT OPTION privilege was treated as related to database operations. (Bug
#25203933, Bug #34159579)
Sponsored by: Netzkommune GmbH
7e60621 |
Saturday, 17 Sep 2022
|
23:16 Jochen Neumeister (joneum)
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
#34144531)
- Replication: When the --replicate-same-server-id option was used to
make the replica not skip events that have its own server ID, if the
log file was rotated, replication stopped with an error. The log
rotation event now checks and applies the current value of the option.
(Bug #89375, Bug #27492990)
- Under certain circumstances TRUNCATE performance_schema.accounts
caused duplicated counts in global_status.
Full Changelog: https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-39.html
Sponsored by: Netzkommune GmbH
000b25c |
Saturday, 30 Apr 2022
|
10:17 Jochen Neumeister (joneum)
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
7339d36 |
Tuesday, 15 Feb 2022
|
15:50 Jochen Neumeister (joneum)
databases/mysql57-*: Update ti 5.7.37
Changelog: https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-37.html
Sponsored by: Netzkommune GmbH
881f863 |
Monday, 1 Nov 2021
|
17:09 Jochen Neumeister (joneum)
databases/mysql57-*: update to 5.7.36
Full Changelog: https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-36.html
Sponsored by: Netzkommune GmbH
25cc11b |
Tuesday, 27 Jul 2021
|
16:20 Jochen Neumeister (joneum)
databases/mysql57-*: update to 5.7.35
Full Changelog: https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-35.html
Sponsored by: Netzkommune GmbH
853341f |
Sunday, 30 May 2021
|
09:39 Dima Panov (fluffy)
databases/mysql57-*: update to 5.7.32 GA release
Release Notes: https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-34.html
PR: 255748 (based on)
MFH: 2021Q2
Approved by: joneum@ (implicit)
ebbb2d5 |
Wednesday, 3 Feb 2021
|
06:20 joneum
fix distinfo
Sponsored by: Netzkommune GmbH
|
Tuesday, 20 Oct 2020
|
08:53 joneum
databases/mysq57-{client, server}: Update to latest release 5.7.32
Full Changelog: https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-32.html
Sponsored by: Netzkommune GmbH
|
Monday, 13 Jul 2020
|
19:09 joneum
databases/mysq57-{client, server}: Update to latest release 5.7.31
Full Changelog: https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-31.html
Submitted by: fluffy
MFH: 2020Q3
Security: 0ed71663-c369-11ea-b53c-d4c9ef517024
Sponsored by: Netzkommune GmbH
|
Thursday, 30 Apr 2020
|
08:15 joneum
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
|
Thursday, 16 Jan 2020
|
15:14 joneum
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
|
Thursday, 5 Dec 2019
|
18:12 joneum
Update to 5.7.28
Changelog: https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-28.html
PR: 241920
Approved by: mmokhi (maintainer, implicit)
Sponsored by: Netzkommune GmbH
|
Monday, 5 Aug 2019
|
23:37 mmokhi
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
|
Sunday, 28 Apr 2019
|
21:34 mmokhi
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
|
Monday, 21 Jan 2019
|
20:40 mmokhi
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
|
Sunday, 28 Oct 2018
|
22:31 mmokhi
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
|
Friday, 10 Aug 2018
|
21:45 mmokhi
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
|
Friday, 20 Apr 2018
|
10:47 mmokhi
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
|
Wednesday, 17 Jan 2018
|
22:43 mmokhi
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
|
Thursday, 19 Oct 2017
|
17:50 feld
databases/mysql57: Update to 5.7.20
Approved by: ports-secteam (with hat)
MFH: 2017Q4
Security: c41bedfd-b3f9-11e7-ac58-b499baebfeaf
|
Wednesday, 19 Jul 2017
|
15:15 mmokhi
databases/mysql57-{client/server}: Update to 5.7.19
ChangeLog for this update:
https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-19.html
PR: 220849
Reviewed by: mat (mentor)
Approved by: mat (mentor)
Sponsored by: Netzkommune GmbH
Differential Revision: https://reviews.freebsd.org/D11656
|
Monday, 17 Apr 2017
|
14:58 mmokhi
databases/mysql57-{server client}: Update to latest 5.7.18 release
Fix some no-longer-valid (but needed) patches.
Reviewed by: feld, mat (mentors)
Approved by: feld (mentor)
Differential Revision: https://reviews.freebsd.org/D10392
|
Tuesday, 3 Jan 2017
|
14:40 lifanov
update mysql57 ports to 5.7.17
Changelog: https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-17.html
PR: 215711
Submitted by: Mahdi Mokhtari <mokhi64@gmail.com> (maintainer)
Reviewed by: matthew
Approved by: matthew (mentor)
Differential Revision: https://reviews.freebsd.org/D9027
|
Friday, 16 Sep 2016
|
15:55 riggs
Update to upstream version 5.7.15; fixes zero-day remote vuln CVE-2016-6662
PR: 212690
Submitted by: mokhi64@gmail.com (maintainer)
MFH: 2016Q3
Security: CVE 2016-6662
|
Wednesday, 15 Jun 2016
|
05:40 pi
databases/mysql57-{server|client}: 5.7.12 -> 5.7.13
Changes:
http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-13.html
PR: 210042
Approved by: Mahdi Mokhtari <mokhi64@gmail.com> (maintainer)
|
Friday, 6 May 2016
|
14:40 riggs
Update to 5.7.12, fixing 31 partially critical vulnerabilities
List of vulnerabilities is documented on:
http://vuxml.freebsd.org/freebsd/8c2b2f11-0ebe-11e6-b55e-b499baebfeaf.html
CVE IDs see below.
PR: 206998
Submitted by: mokhi64@gmail.com (maintainer)
Reviewed by: rootservice@gmail.com
Approved by: mokhi64@gmail.com (maintainer)
MFH: 2016Q2
Security: CVE-2016-0705
CVE-2016-0639
CVE-2015-3194
CVE-2016-0640
CVE-2016-0641
CVE-2016-3461
CVE-2016-2047
CVE-2016-0642
CVE-2016-0643
CVE-2016-0644
CVE-2016-0646
CVE-2016-0647
CVE-2016-0648
CVE-2016-0649
CVE-2016-0650
CVE-2016-0652
CVE-2016-0653
CVE-2016-0654
CVE-2016-0655
CVE-2016-0656
CVE-2016-0657
CVE-2016-0658
CVE-2016-0651
CVE-2016-0659
CVE-2016-0661
CVE-2016-0662
CVE-2016-0663
CVE-2016-0665
CVE-2016-0666
CVE-2016-0667
CVE-2016-0668
|
Sunday, 10 Jan 2016
|
20:07 pi
databases/mysql57-client, databases/mysql57-server:
change all files that were missed in the last commit
PR: 204607
|
Tuesday, 15 Dec 2015
|
19:40 pi
New ports: databases/mysql57-client, databases/mysql57-server
The next major release of mysql.
MySQL is a very fast, multi-threaded, multi-user and robust SQL
(Structured Query Language) database server.
WWW: http://www.mysql.com/
PR: 204607
Submitted by: mokhi64@gmail.com
Reviewed by: koobs, brnrd
Approved by: mat
|
Number of commits found: 34 |