summaryrefslogtreecommitdiff
path: root/databases/mysql57-client (follow)
Commit message (Collapse)AuthorAgeFilesLines
* devel/protobuf: Update to 3.19.4Po-Chuan Hsieh2022-02-281-1/+1
| | | | | | - Bump PORTREVISION of dependent ports for shlib change Changes: https://github.com/protocolbuffers/protobuf/releases
* */*: Remove redundant '-*' from CONFLICTS definitionsStefan Eßer2021-11-251-4/+4
| | | | | | | | | 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-*: update to 5.7.36Jochen Neumeister2021-11-011-1/+1
| | | | | | Full Changelog: https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-36.html Sponsored by: Netzkommune GmbH
* databases/mysql57-*: fix build with libresslJochen Neumeister2021-08-101-0/+3
| | | | Sponsored by: Netzkommune GmbH
* net/openldap24-server: Make SASL permanent for OpenLDAP port.Xin LI2021-08-011-2/+2
| | | | | | | PR: ports/257374 Reviewed by: obrien Approved by: portmgr (exp-run by antoine) Differential Revision: https://reviews.freebsd.org/D31301
* databases/mysql57-*: update to 5.7.35Jochen Neumeister2021-07-271-1/+1
| | | | | | Full Changelog: https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-35.html Sponsored by: Netzkommune GmbH
* devel/protobuf: Update to 3.17.3Po-Chuan Hsieh2021-07-221-1/+1
| | | | | | | | - Bump PORTREVISION of dependent ports for shlib change Changes: https://github.com/protocolbuffers/protobuf/releases PR: 257026 Exp-run by: antoine
* databases/mysql57-*: update to 5.7.32 GA releaseDima Panov2021-05-301-8/+8
| | | | | | | | 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)
* Remove # $FreeBSD$ from Makefiles.Mathieu Arnold2021-04-061-1/+0
|
* databases/mysql56*: update to 5.7.33 releaseDima Panov2021-02-033-16/+49
| | | | | | | Disable detect of TLSv1.3 functions - it's broken with LibreSSL Release Notes: https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-33.html Requested by: joneum
* Bump PORTREVISION for devel/protobuf shlib changeSunpoet Po-Chuan Hsieh2021-01-261-1/+1
|
* databases/mysq57-{client, server}: Update to latest release 5.7.32Jochen Neumeister2020-10-201-1/+1
| | | | | | Full Changelog: https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-32.html Sponsored by: Netzkommune GmbH
* Bump PORTREVISION for devel/protobuf shlib changeSunpoet Po-Chuan Hsieh2020-08-301-0/+1
|
* databases/mysq57-{client, server}: Update to latest release 5.7.31Jochen Neumeister2020-07-131-1/+0
| | | | | | | | | 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
* databases/mysql57-client: fix SIGSEGV due to static OpenSSL linkingJochen Neumeister2020-07-091-15/+36
| | | | | | | | | | | | | | | | As opposed to MySQL 8.0.x branch that switched to dynamic linking for OpenSSL libraries, MySQL 5.7.30 still statically links client applications with OpenSSL. Meantime, OpenSSL supports dynamic loading of external engines like security/gost-engine. If such engine is configured to load in the openssl.cnf, mysql CLI application crashes at start with SIGSEGV early trying to initialize OpenSSL. This loads dynamic engine library libgost.so that calls OpenSSL function using second (uninitialized) instance of OpenSSL leading to crash. The problem is fixed with small backport from MySQL 8.0.x for cmake/ssl.cmake distribution file we already patching anyway. https://github.com/openssl/openssl/issues/12368 PR: 247803 Reported by: eugen Sponsored by: Netzkommune GmbH
* Bump PORTREVISION for devel/protobuf shlib changeSunpoet Po-Chuan Hsieh2020-06-031-1/+1
|
* In file included from ↵Jochen Neumeister2020-05-043-0/+58
| | | | | | | | | | | | | /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.30Jochen Neumeister2020-04-303-37/+6
| | | | | | | | | | | | | | | | | | | | | | 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
* Bump PORTREVISION for devel/protobuf shlib changeSunpoet Po-Chuan Hsieh2020-01-221-1/+1
|
* databases/mysq56-{client, server}: Update to latest release 5.7.29Jochen Neumeister2020-01-161-1/+1
| | | | | | | | | | | | | | | | 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
* /ram/usr/ports/databases/mysql57-client/work/mysql-5.7.28/vio/viosslfactorie ↵Jochen Neumeister2019-12-072-10/+22
| | | | | | | | | | | | s.c:505:27: error: use of undeclared identifier 'SSL_OP_NO_TLSv1_3' | SSL_OP_NO_TLSv1_3 This patch fix this error PR: 242474 Approved by: mmokhi (maintainer, implicit) Sponsored by: Netzkommune GmbH
* Make the build dependency more accurateAntoine Brodin2019-09-281-1/+1
|
* Revert r513041, it breaks the portsAntoine Brodin2019-09-281-0/+1
| | | | | Reported by: pkg-fallout Pointy hat: bapt
* sasl.h header does not belong at all to openldap packageBaptiste Daroussin2019-09-271-1/+0
| | | | | but to the cyrus-sasl2 package already listed in the dependency in the above line. Just remove the wrong dependency line
* Convert to UCL & cleanup pkg-message (categories d)Mathieu Arnold2019-08-131-4/+6
|
* databases/mysq56-{client, server}: Update to latest release 5.7.27Mahdi Mokhtari2019-08-052-12/+12
| | | | | | | | | | | | 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 devel/protobuf shlib changeSunpoet Po-Chuan Hsieh2019-07-311-1/+1
|
* databases/mysql57-{client, server}: Update to latest release 5.7.26Mahdi Mokhtari2019-04-281-22/+22
| | | | | | | | | | | | | | | | | | | | 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
* databases/mysql57-{client, server}: Update to latest release 5.7.25Mahdi Mokhtari2019-01-211-1/+1
| | | | | | | | | | | | | | | | | | | | 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
* Fix build on GCC-based architectures by removing default assumption thatMark Linimon2019-01-031-4/+5
| | | | | | FreeBSD == clang. Approved by: portmgr (tier-2 blanket)
* databases/mysql57-client: Fix build for i386Mahdi Mokhtari2018-12-262-4/+12
| | | | | | | | | | | | | 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. This fixes the build of mysql57-client on the i386 again. PR: 229605 Submitted by: PitDron <pitdron@gmail.com> Reported by: gbromov@gmail.com Sponsored by: The FreeBSD Foundation
* databases/mysql57-client: Fix the build with GCC-based architecturesMahdi Mokhtari2018-12-221-5/+17
| | | | | | | | | | | This patch adds a condition to FreeBSD part of MySQL CMake-scripts to recognize gcc as well as Clang, while taking care of Unsupported compilers too. This is an enhancement on the initial patch by Piotr Kubaj <pkubaj@anongoth.pl> that committed by linimon on r488087. PR: 234172 Sponsored by: The FreeBSD Foundation
* Actually add the fix.Mark Linimon2018-12-221-0/+11
| | | | Reported by: maintainer
* Fix port not compiling on GCC-based architectures, because MySQL believedMark Linimon2018-12-221-3/+0
| | | | | | | | only that Clang was used on FreeBSD. PR: 234172 Submitted by: Piotr Kubaj Approved by: portmgr (tier-2 blanket)
* databases/mysql57-{client, server}: Fix inconsistencies on texinfo and man filesMahdi Mokhtari2018-11-251-1/+1
| | | | | | This is port of r485867 from mysql56-{client, server} Differential Revision: The FreeBSD Foundation
* databases/mysql57-{client, server}: Update to 5.7.24Mahdi Mokhtari2018-10-282-11/+10
| | | | | | | | | | | | | | 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-{client, server}: Update ports to 5.7.23Mahdi Mokhtari2018-08-101-1/+1
| | | | | | | | | | | | 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
* databases/mysql57-client: Fix build with 10.x default compiler/linkerMahdi Mokhtari2018-04-222-1/+12
| | | | | | | | | | The upstream seems merged our local-patches but added a -R flag to its `c++` [actually ld] command. The -R $DIR is like -rpath on 11.x and CURRENT bases but not on 10.x We then use -rpath to make sure it works on all supported bases. Reported by: John W. O'Brien <john@saltant.com> Sponsored by: Netzkommune GmbH
* mysql57-{client, server}: Update port to 5.7.22Mahdi Mokhtari2018-04-201-0/+1
| | | | | | | | | | | | 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/mysql56-{client, server}: Update to 5.7.21Mahdi Mokhtari2018-01-175-39/+17
| | | | | | | | | | 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 ↵Mahdi Mokhtari2017-10-211-1/+0
| | | | | | | | | | | | | | | | | 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
* databases/mysql57-{server client}: Fix broken SASL/LDAP integration on ↵Mahdi Mokhtari2017-07-234-0/+72
| | | | | | | | | | | | | | | | | | | 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
* databases/mysql57-{client/server}: Update to 5.7.19Mahdi Mokhtari2017-07-193-5/+26
| | | | | | | | | | 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
* Mark some ports failing on power64. In cases where the error messageMark Linimon2017-05-201-2/+2
| | | | | | | | | was a stub, provide a real one. While here, pet portlint. Reported by: swills Approved by: portmgr (tier-2 blanket)
* databases/mysql57-{server client}: Update to latest 5.7.18 releaseMahdi Mokhtari2017-04-172-18/+7
| | | | | | | | Fix some no-longer-valid (but needed) patches. Reviewed by: feld, mat (mentors) Approved by: feld (mentor) Differential Revision: https://reviews.freebsd.org/D10392
* devel/libevent2: drop historical suffix after r362796Jan Beich2017-02-201-1/+1
| | | | | PR: 216777 Approved by: mm (maintainer)
* devel/libevent2: update to 2.1.8 and cleanupJan Beich2017-02-041-1/+1
| | | | | | | | | | | - DEFAULT_VERSIONS += ssl=openssl-devel is now supported - devel/py-event and devel/p5-Event-Lib are marked BROKEN Changes: https://github.com/libevent/libevent/raw/release-2.1.8-stable/whatsnew-2.1.txt Changes: https://github.com/libevent/libevent/raw/release-2.1.8-stable/ChangeLog PR: 216527 Exp-run by: antoine Approved by: mm (maintainer)
* Fix cut-and-paste typo.Mark Linimon2016-09-191-1/+1
| | | | Reported by: maintainer
* Mark broken on sparc64.Mark Linimon2016-09-181-0/+1
| | | | Approved by: portmgr (tier-2 blanket)
* Update to upstream version 5.7.15; fixes zero-day remote vuln CVE-2016-6662Thomas Zander2016-09-163-14/+14
| | | | | | | PR: 212690 Submitted by: mokhi64@gmail.com (maintainer) MFH: 2016Q3 Security: CVE 2016-6662
generated by cgit v1.2.3 (git 2.25.1) at 2025-10-30 17:22:00 +0000