summaryrefslogtreecommitdiff
path: root/databases/mysql57-client/files (follow)
Commit message (Collapse)AuthorAgeFilesLines
* 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)
* databases/mysql56*: update to 5.7.33 releaseDima Panov2021-02-032-15/+48
| | | | | | | 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
* 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
* 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
* /ram/usr/ports/databases/mysql57-client/work/mysql-5.7.28/vio/viosslfactorie ↵Jochen Neumeister2019-12-071-9/+21
| | | | | | | | | | | | 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
* databases/mysq56-{client, server}: Update to latest release 5.7.27Mahdi Mokhtari2019-08-051-11/+11
| | | | | | | | | | | | 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
* 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
* 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-261-3/+11
| | | | | | | | | | | | | 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
* 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
* databases/mysql57-client: Fix build with 10.x default compiler/linkerMahdi Mokhtari2018-04-221-0/+11
| | | | | | | | | | 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
* databases/mysql56-{client, server}: Update to 5.7.21Mahdi Mokhtari2018-01-174-38/+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-{server client}: Fix broken SASL/LDAP integration on ↵Mahdi Mokhtari2017-07-232-0/+61
| | | | | | | | | | | | | | | | | | | 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-192-4/+24
| | | | | | | | | | 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
* databases/mysql57-{server client}: Update to latest 5.7.18 releaseMahdi Mokhtari2017-04-171-17/+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
* Update to upstream version 5.7.15; fixes zero-day remote vuln CVE-2016-6662Thomas Zander2016-09-162-13/+13
| | | | | | | PR: 212690 Submitted by: mokhi64@gmail.com (maintainer) MFH: 2016Q3 Security: CVE 2016-6662
* databases/mysql57-server: Fix build with LibreSSLBernard Spil2016-08-241-0/+15
| | | | | | | | | | | - Fix building when OPENSSL_VERSION_NUMBER == 2 - Switch USE_OPENSSL to USES= ssl PR: 211770 Submitted by: Markus Kohlmeyer <rootservice@gmail.com> Reported by: Markus Kohlmeyer <rootservice@gmail.com> Approved by: Mahdi Mokhtari <mokhi64@gmail.com> MFH: 2016Q3
* Make my.cnf path correct according to hier(7), bump PORTREVISIONThomas Zander2016-07-041-7/+37
| | | | | | PR: 209579 Submitted by: mokhi64@gmail.com Reviewed by: rootservice@gmail.com
* Update to 5.7.12, fixing 31 partially critical vulnerabilitiesThomas Zander2016-05-0615-29/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Cosmetic change of handling manual pages; preparation for upcoming updateThomas Zander2016-04-231-4/+2
| | | | | | PR: 208634 Submitted by: rootservice@gmail.com Approved by: mokhi64@gmail.com (maintainer)
* - Fix plistThomas Zander2016-02-031-8/+1
| | | | | | | | | | | | | | | | | | | - binary_log_types.h is now installed only by client, not server - lib/mysql/plugin/ha_example.so is only installed if EXAMPLES OPTION is turned off - Bump PORTREVISION - Allow slave port to override PORTREVISION if necessary - Deactivate performance_schema feature to conserve memory - Add notes to pkg-message: - root password - performance_schema feature is deactivated by default to reduce memory footprint PR: 205956 206065 Submitted by: smh Reviewed by: mokhi64@gmail.com (maintainer) Approved by: mokhi64@gmail.com (maintainer) MFH: 2016Q1
* databases/mysql57-client, databases/mysql57-server:Kurt Jaeger2016-01-107-124/+113
| | | | | | change all files that were missed in the last commit PR: 204607
* databases/mysql57-client, databases/mysql57-server:Kurt Jaeger2016-01-1016-0/+432
| | | | | | re-add for proper repo-copy PR: 204607
* databases/mysql57-client, databases/mysql57-server:Kurt Jaeger2016-01-1016-421/+0
| | | | | | remove to prepare for proper repo-copy PR: 204607
* - Restore backwards compatibilityMartin Wilke2015-12-271-45/+21
| | | | PR: 205433
* databases/mysql57-*: Support DragonFlyJohn Marino2015-12-174-0/+69
| | | | PR: 204607
* New ports: databases/mysql57-client, databases/mysql57-serverKurt Jaeger2015-12-1512-0/+376
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
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-15 22:04:41 +0000