![[BACK]](/icons/back.gif){kind=icon}
Up to [cvs.NetBSD.org] / pkgsrc / databases / mysql55-client
Request diff between arbitrary revisions
Default branch: MAIN
Revision 1.36, Sat May 23 07:25:10 2020 UTC (3 years, 6 months ago) by adam
Branch: MAIN
CVS Tags: HEAD
Changes since 1.35: +1 -1
lines
FILE REMOVED
Retired mysql55 and postgresql94 packages
Revision 1.35 / (download) - annotate - [select for diffs], Sat Jan 18 21:48:00 2020 UTC (3 years, 10 months ago) by jperkin
Branch: MAIN
CVS Tags: pkgsrc-2020Q1-base,
pkgsrc-2020Q1
Changes since 1.34: +2 -2
lines
Diff to previous 1.34 (colored)
*: Recursive revision bump for openssl 1.1.1.
Revision 1.34 / (download) - annotate - [select for diffs], Sun Aug 11 13:18:20 2019 UTC (4 years, 3 months ago) by wiz
Branch: MAIN
CVS Tags: pkgsrc-2019Q4-base,
pkgsrc-2019Q4,
pkgsrc-2019Q3-base,
pkgsrc-2019Q3
Changes since 1.33: +2 -2
lines
Diff to previous 1.33 (colored)
Bump PKGREVISIONs for perl 5.30.0
Revision 1.33 / (download) - annotate - [select for diffs], Tue Apr 30 17:20:23 2019 UTC (4 years, 7 months ago) by abs
Branch: MAIN
CVS Tags: pkgsrc-2019Q2-base,
pkgsrc-2019Q2
Changes since 1.32: +2 -2
lines
Diff to previous 1.32 (colored)
Bump PKGREVISION for addition of USE_GCC_RUNTIME
Revision 1.31.2.1 / (download) - annotate - [select for diffs], Tue Jan 29 13:01:45 2019 UTC (4 years, 10 months ago) by bsiegert
Branch: pkgsrc-2018Q4
Changes since 1.31: +2 -1
lines
Diff to previous 1.31 (colored) next main 1.32 (colored)
Pullup ticket #5900 - requested by maya
databases/mysql55-client: security fix
databases/mysql56-client: security fix
databases/mysql57-client: security fix
Revisions pulled up:
- databases/mysql55-client/Makefile 1.32
- databases/mysql55-client/distinfo 1.63
- databases/mysql55-client/patches/patch-CMakeLists.txt 1.7
- databases/mysql55-client/patches/patch-cmake_build__configurations_mysql__release.cmake 1.1
- databases/mysql55-client/patches/patch-sql_sys__vars.cc 1.1
- databases/mysql56-client/Makefile 1.28
- databases/mysql56-client/distinfo 1.49
- databases/mysql56-client/patches/patch-CMakeLists.txt 1.6
- databases/mysql56-client/patches/patch-cmake_build__configurations_mysql__release.cmake 1.1
- databases/mysql56-client/patches/patch-sql_sys__vars.cc 1.3
- databases/mysql57-client/Makefile 1.19
- databases/mysql57-client/distinfo 1.27
- databases/mysql57-client/patches/patch-CMakeLists.txt 1.2
- databases/mysql57-client/patches/patch-cmake_build__configurations_mysql__release.cmake 1.1
- databases/mysql57-client/patches/patch-sql_sys__vars.cc 1.1
---
Module Name: pkgsrc
Committed By: maya
Date: Sun Jan 20 18:03:25 UTC 2019
Modified Files:
pkgsrc/databases/mysql55-client: Makefile distinfo
pkgsrc/databases/mysql55-client/patches: patch-CMakeLists.txt
Added Files:
pkgsrc/databases/mysql55-client/patches:
patch-cmake_build__configurations_mysql__release.cmake
patch-sql_sys__vars.cc
Log Message:
mysql55-client: change the default configuration to avoid information
disclosure to a malicious server.
Backport of upstream commit:
https://github.com/mysql/mysql-server/commit/98ed3d8bc8ad724686d26c7bf98dced3bd1777be
Exploit method described here:
https://gwillem.gitlab.io/2019/01/17/adminer-4.6.2-file-disclosure-vulnerability/
---
Module Name: pkgsrc
Committed By: maya
Date: Sun Jan 20 18:04:49 UTC 2019
Modified Files:
pkgsrc/databases/mysql56-client: Makefile distinfo
pkgsrc/databases/mysql56-client/patches: patch-CMakeLists.txt
Added Files:
pkgsrc/databases/mysql56-client/patches:
patch-cmake_build__configurations_mysql__release.cmake
patch-sql_sys__vars.cc
Log Message:
mysql56-client: change the default configuration to avoid information
disclosure to a malicious server.
Backport of upstream commit:
https://github.com/mysql/mysql-server/commit/98ed3d8bc8ad724686d26c7bf98dced3bd1777be
Exploit method described here:
https://gwillem.gitlab.io/2019/01/17/adminer-4.6.2-file-disclosure-vulnerability/
---
Module Name: pkgsrc
Committed By: maya
Date: Sun Jan 20 18:22:10 UTC 2019
Modified Files:
pkgsrc/databases/mysql57-client: Makefile distinfo
pkgsrc/databases/mysql57-client/patches: patch-CMakeLists.txt
Added Files:
pkgsrc/databases/mysql57-client/patches:
patch-cmake_build__configurations_mysql__release.cmake
patch-sql_sys__vars.cc
Log Message:
mysql57-client: change the default configuration to avoid information
disclosure to a malicious server.
Backport of upstream commit:
https://github.com/mysql/mysql-server/commit/98ed3d8bc8ad724686d26c7bf98dced3bd1777be
Exploit method described here:
https://gwillem.gitlab.io/2019/01/17/adminer-4.6.2-file-disclosure-vulnerability/
Revision 1.32 / (download) - annotate - [select for diffs], Sun Jan 20 18:03:25 2019 UTC (4 years, 10 months ago) by maya
Branch: MAIN
CVS Tags: pkgsrc-2019Q1-base,
pkgsrc-2019Q1
Changes since 1.31: +2 -1
lines
Diff to previous 1.31 (colored)
mysql55-client: change the default configuration to avoid information disclosure to a malicious server. Backport of upstream commit: https://github.com/mysql/mysql-server/commit/98ed3d8bc8ad724686d26c7bf98dced3bd1777be Exploit method described here: https://gwillem.gitlab.io/2019/01/17/adminer-4.6.2-file-disclosure-vulnerability/
Revision 1.31 / (download) - annotate - [select for diffs], Thu Nov 22 11:27:11 2018 UTC (5 years ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2018Q4-base
Branch point for: pkgsrc-2018Q4
Changes since 1.30: +1 -2
lines
Diff to previous 1.30 (colored)
mysql55: updated to 5.5.62 Changes in MySQL 5.5.62 Functionality Added or Changed * Previously, file I/O performed in the I/O cache in the mysys library was not instrumented, affecting in particular file I/O statistics reported by the Performance Schema about the binary log index file. Now, this I/O is instrumented and Performance Schema statistics are accurate. Thanks to Yura Sorokin for the contribution. * The zlib library version bundled with MySQL was raised from version 1.2.3 to version 1.2.11. MySQL implements compression with the help of the zlib library. * The zlib compressBound() function in zlib 1.2.11 returns a slightly higher estimate of the buffer size required to compress a given length of bytes than it did in zlib version 1.2.3. The compressBound() function is called by InnoDB functions that determine the maximum row size permitted when creating compressed InnoDB tables or inserting rows into compressed InnoDB tables. As a result, CREATE TABLE ... ROW_FORMAT=COMPRESSED or INSERT operations with row sizes very close to the maximum row size that were successful in earlier releases could now fail. Bugs Fixed * MySQL Server and test RPM packages were missing perl-Data-Dumper as a dependency. * For the mysql client, the -b short option was associated with two long options, --no-beep and --binary-as-hex. The -b option now is associated only with --no-beep. * During server startup/shutdown, PID files could be mishandled. * For MEMORY tables, memory overflow errors could occur. * When converting from a BLOB (or TEXT) type to a smaller BLOB (or TEXT) type, no warning or error was reported informing about the truncation or data loss. Now an appropriate error is issued in strict SQL mode and a warning in nonstrict SQL mode. * ALTER TABLE ... REORGANIZE PARTITION ... could result in incorrect behavior if any partition other than the last was missing the VALUES LESS THAN part of the syntax.
Revision 1.30 / (download) - annotate - [select for diffs], Wed Aug 22 09:43:12 2018 UTC (5 years, 3 months ago) by wiz
Branch: MAIN
CVS Tags: pkgsrc-2018Q3-base,
pkgsrc-2018Q3
Changes since 1.29: +2 -1
lines
Diff to previous 1.29 (colored)
Recursive bump for perl5-5.28.0
Revision 1.28.2.1 / (download) - annotate - [select for diffs], Sat Jul 29 13:56:01 2017 UTC (6 years, 4 months ago) by spz
Branch: pkgsrc-2017Q2
Changes since 1.28: +14 -11
lines
Diff to previous 1.28 (colored) next main 1.29 (colored)
Pullup ticket #5524 - requested by taca
databases/mysql55-client: security update
databases/mysql55-server: security update
Revisions pulled up:
- databases/mysql55-client/Makefile 1.29
- databases/mysql55-client/Makefile.common 1.60
- databases/mysql55-client/distinfo 1.59
- databases/mysql55-server/Makefile 1.33
- databases/mysql55-server/PLIST 1.47
-------------------------------------------------------------------
Module Name: pkgsrc
Committed By: adam
Date: Wed Jul 19 18:48:22 UTC 2017
Modified Files:
pkgsrc/databases/mysql55-client: Makefile Makefile.common distinfo
pkgsrc/databases/mysql55-server: Makefile PLIST
pkgsrc/databases/mysql56-client: Makefile Makefile.common distinfo
pkgsrc/databases/mysql56-server: Makefile PLIST
Log Message:
Security Notes
* Security Fix: The linked OpenSSL library for the MySQL Commercial Server has been updated to version 1.0.2l. Issues fixed in the new OpenSSL version are described at http://www.openssl.org/news/vulnerabilities.html.
This change does not affect the Oracle-produced MySQL Community build of MySQL Server, which uses the yaSSL library instead.
Platform-Specific Notes
* Linux: The generic Linux build for MySQL 5.6 is now built on Oracle Linux 6 using glibc 2.12. Systems that use the build need to have glibc 2.12 or later installed on them.
Functionality Added or Changed
* For Windows, MSI installer packages now include a check for the required Visual Studio redistributable package, and produce a message asking the user to install it if it is missing.
* The mysql client now supports a --binary-as-hex option that causes display of binary data using hexadecimal notation (0xvalue). Thanks to DaniõÍ van Eeden for the patch.
* mysqlaccess now looks for its configuration file only in the SYSCONFDIR directory and /etc.
Bugs Fixed
* InnoDB: The server allocated memory unnecessarily for an operation that rebuilt the table.
* InnoDB: When using an index merge optimizer switch, a SELECT COUNT(*) operation sometimes returned 0. Partitioning code incorrectly performed a memcpy instead of a column copy of columns read by the index, causing the wrong records to be copied.
* Replication: A USE statement that followed a SET GTID_NEXT statement sometimes had no effect.
* Replication: If the binary log on a master server was rotated and a full disk condition occurred on the partition where the binary log file was being stored, the server could stop unexpectedly. The fix adds a check for the existence of the binary log when the dump thread switches to next binary log file. If the binary log is disabled, all binary logs up to the current active log are transmitted to slave and an error is returned to the receiver thread.
* Replication: If a relay log index file named relay log files that did not exist, RESET SLAVE ALL sometimes did not fully clean up properly.
* Replication: mysqlbinlog, if invoked with the --raw option, does not flush the output file until the process terminates. But if also invoked with the --stop-never option, the process never terminates, thus nothing is ever written to the output file. Now the output is flushed after each event.
* Replication: A memory leak in mysqlbinlog was fixed. The leak happened when processing fake rotate events, or when using --raw and the destination log file could not be created. The leak only occurred when processing events from a remote server. Thanks to Laurynas Biveinis for his contribution to fixing this bug.
* Replication: Multi-threaded slaves could not be configured with small queue sizes using slave_pending_jobs_size_max if they ever needed to process transactions larger than that size. Any packet larger than slave_pending_jobs_size_max was rejected with the error ER_MTS_EVENT_BIGGER_PENDING_JOBS_SIZE_MAX, even if the packet was smaller than the limit set by slave_max_allowed_packet.
* With this fix, slave_pending_jobs_size_max becomes a soft limit rather than a hard limit. If the size of a packet exceeds slave_pending_jobs_size_max but is less than slave_max_allowed_packet, the transaction is held until all the slave workers have empty queues, and then processed. All subsequent transactions are held until the large transaction has been completed. The queue size for slave workers can therefore be limited while still allowing occasional larger transactions.
* mysqldump could write database names in USE statements incorrectly.
* If the mysql_stmt_close() C API function was called, it freed memory that later could be accessed if mysql_stmt_error(), mysql_stmt_errno(), or mysql_stmt_sqlstate() was called. To obtain error information after a call to mysql_stmt_close(), call mysql_error(), mysql_errno(), or mysql_sqlstate() instead.
* Queries could be cached incorrectly, leading to incorrect query results, under these circumstances: InnoDB table; rows are being inserted but have not yet been committed; a query uses the table as a base table in a derived table; the optimizer chooses to materialize the derived table.
* Man pages for a few utilities were missing from Debian/Ubuntu packages.
* The field-t unit test failed to run with AddressSanitizer enabled. Thanks to Laurynas Biveinis for the patch.
* Debian client packages were missing information about conflicts with native packages.
* The Perl path in #! lines at the beginning of Perl scripts has been adjusted to /usr/local/bin/perl for FreeBSD 11.
* The server exited abnormally attempting to access invalid memory.
* A race condition could occur for CREATE TABLE statements with DATA DIRECTORY or INDEX DIRECTORY clauses.
* MySQL compilation in different directories produced different builds to leakage of absolute paths into debug information and __FILE__.
* mysqld_failed to start the server if the --datadir option was specified with a relative path name.
* With read_only enabled, creation of non-TEMPORARY tables by non-SUPER users was permitted under certain conditions.
*Certain stored functions, if used in a query WHERE clause, could be handled using Index Condition Pushdown (which should not happen), resulting in a server exit.
* On x86 machines, the uint3korr() macro read 4 bytes of data instead of the intended 3 bytes.
* An assertion was raised during a fetch operation by the memcached plugin.
* Queries that contained UNION in a subquery and GROUP BY could return incorrect results.
* LOAD XML INFILE performance became noticeably slower when the XML file being read contained a great many spaces, such as those introduced by indenting or pretty-printing. Now all leading whitespace is trimmed from each such value before reading it into memory.
To generate a diff of this commit:
cvs rdiff -u -r1.28 -r1.29 pkgsrc/databases/mysql55-client/Makefile
cvs rdiff -u -r1.59 -r1.60 pkgsrc/databases/mysql55-client/Makefile.common
cvs rdiff -u -r1.58 -r1.59 pkgsrc/databases/mysql55-client/distinfo
cvs rdiff -u -r1.32 -r1.33 pkgsrc/databases/mysql55-server/Makefile
cvs rdiff -u -r1.46 -r1.47 pkgsrc/databases/mysql55-server/PLIST
Revision 1.29 / (download) - annotate - [select for diffs], Wed Jul 19 18:48:21 2017 UTC (6 years, 4 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2018Q2-base,
pkgsrc-2018Q2,
pkgsrc-2018Q1-base,
pkgsrc-2018Q1,
pkgsrc-2017Q4-base,
pkgsrc-2017Q4,
pkgsrc-2017Q3-base,
pkgsrc-2017Q3
Changes since 1.28: +14 -11
lines
Diff to previous 1.28 (colored)
Security Notes * Security Fix: The linked OpenSSL library for the MySQL Commercial Server has been updated to version 1.0.2l. Issues fixed in the new OpenSSL version are described at http://www.openssl.org/news/vulnerabilities.html. This change does not affect the Oracle-produced MySQL Community build of MySQL Server, which uses the yaSSL library instead. Platform-Specific Notes * Linux: The generic Linux build for MySQL 5.6 is now built on Oracle Linux 6 using glibc 2.12. Systems that use the build need to have glibc 2.12 or later installed on them. Functionality Added or Changed * For Windows, MSI installer packages now include a check for the required Visual Studio redistributable package, and produce a message asking the user to install it if it is missing. * The mysql client now supports a --binary-as-hex option that causes display of binary data using hexadecimal notation (0xvalue). Thanks to Daniël van Eeden for the patch. * mysqlaccess now looks for its configuration file only in the SYSCONFDIR directory and /etc. Bugs Fixed * InnoDB: The server allocated memory unnecessarily for an operation that rebuilt the table. * InnoDB: When using an index merge optimizer switch, a SELECT COUNT(*) operation sometimes returned 0. Partitioning code incorrectly performed a memcpy instead of a column copy of columns read by the index, causing the wrong records to be copied. * Replication: A USE statement that followed a SET GTID_NEXT statement sometimes had no effect. * Replication: If the binary log on a master server was rotated and a full disk condition occurred on the partition where the binary log file was being stored, the server could stop unexpectedly. The fix adds a check for the existence of the binary log when the dump thread switches to next binary log file. If the binary log is disabled, all binary logs up to the current active log are transmitted to slave and an error is returned to the receiver thread. * Replication: If a relay log index file named relay log files that did not exist, RESET SLAVE ALL sometimes did not fully clean up properly. * Replication: mysqlbinlog, if invoked with the --raw option, does not flush the output file until the process terminates. But if also invoked with the --stop-never option, the process never terminates, thus nothing is ever written to the output file. Now the output is flushed after each event. * Replication: A memory leak in mysqlbinlog was fixed. The leak happened when processing fake rotate events, or when using --raw and the destination log file could not be created. The leak only occurred when processing events from a remote server. Thanks to Laurynas Biveinis for his contribution to fixing this bug. * Replication: Multi-threaded slaves could not be configured with small queue sizes using slave_pending_jobs_size_max if they ever needed to process transactions larger than that size. Any packet larger than slave_pending_jobs_size_max was rejected with the error ER_MTS_EVENT_BIGGER_PENDING_JOBS_SIZE_MAX, even if the packet was smaller than the limit set by slave_max_allowed_packet. * With this fix, slave_pending_jobs_size_max becomes a soft limit rather than a hard limit. If the size of a packet exceeds slave_pending_jobs_size_max but is less than slave_max_allowed_packet, the transaction is held until all the slave workers have empty queues, and then processed. All subsequent transactions are held until the large transaction has been completed. The queue size for slave workers can therefore be limited while still allowing occasional larger transactions. * mysqldump could write database names in USE statements incorrectly. * If the mysql_stmt_close() C API function was called, it freed memory that later could be accessed if mysql_stmt_error(), mysql_stmt_errno(), or mysql_stmt_sqlstate() was called. To obtain error information after a call to mysql_stmt_close(), call mysql_error(), mysql_errno(), or mysql_sqlstate() instead. * Queries could be cached incorrectly, leading to incorrect query results, under these circumstances: InnoDB table; rows are being inserted but have not yet been committed; a query uses the table as a base table in a derived table; the optimizer chooses to materialize the derived table. * Man pages for a few utilities were missing from Debian/Ubuntu packages. * The field-t unit test failed to run with AddressSanitizer enabled. Thanks to Laurynas Biveinis for the patch. * Debian client packages were missing information about conflicts with native packages. * The Perl path in #! lines at the beginning of Perl scripts has been adjusted to /usr/local/bin/perl for FreeBSD 11. * The server exited abnormally attempting to access invalid memory. * A race condition could occur for CREATE TABLE statements with DATA DIRECTORY or INDEX DIRECTORY clauses. * MySQL compilation in different directories produced different builds to leakage of absolute paths into debug information and __FILE__. * mysqld_failed to start the server if the --datadir option was specified with a relative path name. * With read_only enabled, creation of non-TEMPORARY tables by non-SUPER users was permitted under certain conditions. *Certain stored functions, if used in a query WHERE clause, could be handled using Index Condition Pushdown (which should not happen), resulting in a server exit. * On x86 machines, the uint3korr() macro read 4 bytes of data instead of the intended 3 bytes. * An assertion was raised during a fetch operation by the memcached plugin. * Queries that contained UNION in a subquery and GROUP BY could return incorrect results. * LOAD XML INFILE performance became noticeably slower when the XML file being read contained a great many spaces, such as those introduced by indenting or pretty-printing. Now all leading whitespace is trimmed from each such value before reading it into memory.
Revision 1.28 / (download) - annotate - [select for diffs], Mon Jun 19 12:07:50 2017 UTC (6 years, 5 months ago) by jperkin
Branch: MAIN
CVS Tags: pkgsrc-2017Q2-base
Branch point for: pkgsrc-2017Q2
Changes since 1.27: +2 -1
lines
Diff to previous 1.27 (colored)
Change patch to use upstream 5.6+ change, fixes segfault reported by mark. Bump PKGREVISION.
Revision 1.27 / (download) - annotate - [select for diffs], Thu Aug 4 10:09:46 2016 UTC (7 years, 4 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2017Q1-base,
pkgsrc-2017Q1,
pkgsrc-2016Q4-base,
pkgsrc-2016Q4,
pkgsrc-2016Q3-base,
pkgsrc-2016Q3
Changes since 1.26: +1 -2
lines
Diff to previous 1.26 (colored)
Changes 5.5.51: Bugs Fixed Replication: When using statement-based or mixed binary logging format with --read-only=ON, it was not possible to modify temporary tables. MySQL Server upgrades performed using RPM packages failed when upgrading from MySQL 5.1 Community to MySQL 5.5 Community or MySQL 5.1 Commercial to MySQL 5.5 Commercial. A buffer overflow in the regex library was fixed. Certain arguments to NAME_CONST() could cause a server exit. Installing MySQL from a yum or zypper repository resulted in /var/log/mysqld.log being created with incorrect user and group permissions. If a stored function updated a view for which the view table had a trigger defined that updated another table, it could fail and report an error that an existing table did not exist. If an INSTALL PLUGIN statement contained invalid UTF-8 characters in the shared library name, it caused the server to hang (or to raise an assertion in debug builds). For multibyte character sets, LOAD DATA could fail to allocate space correctly and ignore input rows as a result.
Revision 1.26 / (download) - annotate - [select for diffs], Sat Jul 9 06:38:00 2016 UTC (7 years, 4 months ago) by wiz
Branch: MAIN
Changes since 1.25: +2 -1
lines
Diff to previous 1.25 (colored)
Bump PKGREVISION for perl-5.24.0 for everything mentioning perl.
Revision 1.25 / (download) - annotate - [select for diffs], Mon Apr 18 10:01:15 2016 UTC (7 years, 7 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2016Q2-base,
pkgsrc-2016Q2
Changes since 1.24: +1 -2
lines
Diff to previous 1.24 (colored)
Changes 5.5.49: Security Notes -------------- MySQL client programs now support an --ssl-mode option that enables you to specify the security state of the connection to the server. The default value is DISABLED (establish an unencrypted connection). --ssl-mode=REQUIRED) can be specified to require a secure connection, or fail if a secure connection cannot be obtained. These clients support --ssl-mode: mysql, mysqladmin, mysqlcheck, mysqldump, mysqlimport, mysqlshow, mysqlpump, mysqlslap, mysqltest, mysql_upgrade. For more information, see Command Options for Secure Connections. Bugs Fixed
Revision 1.24 / (download) - annotate - [select for diffs], Sat Mar 5 11:27:42 2016 UTC (7 years, 9 months ago) by jperkin
Branch: MAIN
CVS Tags: pkgsrc-2016Q1-base,
pkgsrc-2016Q1
Changes since 1.23: +2 -1
lines
Diff to previous 1.23 (colored)
Bump PKGREVISION for security/openssl ABI bump.
Revision 1.23 / (download) - annotate - [select for diffs], Wed Nov 11 10:59:48 2015 UTC (8 years ago) by wiz
Branch: MAIN
CVS Tags: pkgsrc-2015Q4-base,
pkgsrc-2015Q4
Changes since 1.22: +1 -2
lines
Diff to previous 1.22 (colored)
Remove REPLACE_PERL line for non-existent file.
Revision 1.22 / (download) - annotate - [select for diffs], Thu Jul 30 14:36:34 2015 UTC (8 years, 4 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2015Q3-base,
pkgsrc-2015Q3
Changes since 1.21: +1 -2
lines
Diff to previous 1.21 (colored)
Changes 5.5.45: * Security Fix: Due to the LogJam issue (https://weakdh.org/), OpenSSL has changed the Diffie-Hellman key length parameters for openssl-1.0.1n and up. OpenSSL has provided a detailed explanation at http://openssl.org/news/secadv_20150611.txt. To adopt this change in MySQL, the key length used in vio/viosslfactories.c for creating Diffie-Hellman keys has been increased from 512 to 2,048 bits. * InnoDB: On Unix-like platforms, os_file_create_simple_no_error_handling_func and os_file_create_func opened files in different modes when innodb_flush_method was set to O_DIRECT. * InnoDB: An assertion was raised when InnoDB attempted to dereference a NULL foreign key object. * InnoDB: An index record was not found on rollback due to inconsistencies in the purge_node_t structure. * The Spencer regex library used for the REGEXP operator could be subject to heap overflow in some circumstances. * A buffer-overflow error could occur for mysqlslap during option parsing. * GROUP BY or ORDER BY on a CHAR(0) NOT NULL column could lead to a server exit. * mysql-systemd-start failed if datadir was set in /etc/my.cnf. * On OS X 10.10 (Yosemite), mysqld failed to start automatically. The startup item has been replaced with a launchd job, which enables the preference pane checkbox for automatic startup to work again.
Revision 1.21 / (download) - annotate - [select for diffs], Fri Jun 12 10:48:36 2015 UTC (8 years, 5 months ago) by wiz
Branch: MAIN
CVS Tags: pkgsrc-2015Q2-base,
pkgsrc-2015Q2
Changes since 1.20: +2 -1
lines
Diff to previous 1.20 (colored)
Recursive PKGREVISION bump for all packages mentioning 'perl', having a PKGNAME of p5-*, or depending such a package, for perl-5.22.0.
Revision 1.20 / (download) - annotate - [select for diffs], Thu Oct 9 13:44:33 2014 UTC (9 years, 1 month ago) by wiz
Branch: MAIN
CVS Tags: pkgsrc-2015Q1-base,
pkgsrc-2015Q1,
pkgsrc-2014Q4-base,
pkgsrc-2014Q4
Changes since 1.19: +1 -2
lines
Diff to previous 1.19 (colored)
Remove SVR4_PKGNAME, per discussion on tech-pkg.
Revision 1.19 / (download) - annotate - [select for diffs], Wed Sep 24 10:31:28 2014 UTC (9 years, 2 months ago) by jperkin
Branch: MAIN
CVS Tags: pkgsrc-2014Q3-base,
pkgsrc-2014Q3
Changes since 1.18: +6 -1
lines
Diff to previous 1.18 (colored)
Remove WRAPPER_BINDIR references in mysqlbug.
Revision 1.18 / (download) - annotate - [select for diffs], Mon Jun 2 07:17:31 2014 UTC (9 years, 6 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2014Q2-base,
pkgsrc-2014Q2
Changes since 1.17: +1 -2
lines
Diff to previous 1.17 (colored)
Changes 5.5.38:
Bugs Fixed
InnoDB: For each insert, memset would be called three times to allocate memory for system fields. To reduce CPU usage, the three memset calls are now combined into a single call.
Replication: When used on a table employing a transactional storage engine, a failed TRUNCATE TABLE was still written to the binary log and thus replayed on the slave. This could lead to inconsistency when the master retained data that was removed on the slave.
Now in such cases TRUNCATE TABLE is logged only when it executes successfully.
Certain INFORMATION_SCHEMA queries could cause a server exit.
For indexes on prefixes or character string columns, index corruption could occur for assignment of binary data to the column due to improper character counting.
Solaris-specific scripts were included in and installed by non-Solaris packages.
EXPLAIN on a query with an EXISTS subquery containing a UNION could cause a server exit. Multiple executions of a prepared EXPLAIN on a UNION of subqueries could cause a server exit.
Executing a correlated subquery on an ARCHIVE table which has an AUTO_INCREMENT column caused the server to hang.
The client library could cause clients to exit due to incorrectly mapping the client error number to the corresponding message, if reallocation of packet buffer memory occurred.
Calling mysql_get_server_version() with an invalid connection handler argument caused the client to exit. Now it returns 0 and reports a CR_COMMANDS_OUT_OF_SYNC error.
On Windows, calling mysql_thread_init() call without mysql_init() caused the client to exit. windows. Now it returns a nonzero result because it is an error to call mysql_thread_init() before the client library is initialized with mysql_library_init().
CMake produced not-useful warnings about INTERFACE_LINK_LIBRARIES policy.
LOAD DATA LOCAL INFILE could use all CPU if import errors occurred when there were no line delimiters.
A statement of the following form broke row-based replication because it created a table having a field of data type BIGINT with a display width of 3000, which is beyond the maximum acceptable value of 255:
CREATE TABLE t1 AS SELECT REPEAT('A',1000) DIV 1 AS a;
Revision 1.17 / (download) - annotate - [select for diffs], Thu May 29 23:35:25 2014 UTC (9 years, 6 months ago) by wiz
Branch: MAIN
Changes since 1.16: +2 -1
lines
Diff to previous 1.16 (colored)
Bump for perl-5.20.0. Do it for all packages that * mention perl, or * have a directory name starting with p5-*, or * depend on a package starting with p5- like last time, for 5.18, where this didn't lead to complaints. Let me know if you have any this time.
Revision 1.15.2.1 / (download) - annotate - [select for diffs], Mon Apr 14 15:29:21 2014 UTC (9 years, 7 months ago) by tron
Branch: pkgsrc-2014Q1
Changes since 1.15: +1 -2
lines
Diff to previous 1.15 (colored) next main 1.16 (colored)
Pullup ticket #4373 - requested by taca databases/mysql55-client: security update databases/mysql56-server: update to keep in sync with with "mysql55-client" Revisions pulled up: - databases/mysql55-client/Makefile 1.16 - databases/mysql55-client/Makefile.common 1.35 - databases/mysql55-client/distinfo 1.32 - databases/mysql55-client/patches/patch-libmysql_CMakeLists.txt 1.2 - databases/mysql55-server/Makefile 1.20 - databases/mysql55-server/PLIST 1.28 --- Module Name: pkgsrc Committed By: adam Date: Mon Mar 31 08:03:23 UTC 2014 Modified Files: pkgsrc/databases/mysql55-client: Makefile Makefile.common distinfo pkgsrc/databases/mysql55-client/patches: patch-libmysql_CMakeLists.txt pkgsrc/databases/mysql55-server: Makefile PLIST Log Message: Changes 5.5.37: Functionality Added or Changed On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. Bugs Fixed InnoDB: A regression introduced by Bug 14329288 would result in a performance degradation when a compressed table does not fit into memory. InnoDB: The maximum value for innodb_thread_sleep_delay is now 1000000 microseconds. The previous maximum value (4294967295 microseconds on 32-bit and 18446744073709551615 microseconds on 64-bit) was unnecessarily large. Because the maximum value of innodb_thread_sleep_delay is limited by the value set for innodb_adaptive_max_sleep_delay (when set to a non-zero value), the maximum value for innodb_thread_sleep_delay is now the same as the maximum value for innodb_adaptive_max_sleep_delay. InnoDB: In debug builds, creating a unique index on a binary column, with input data containing duplicate keys, would cause an assertion. InnoDB: InnoDB would fail to start when innodb_data_file_path specified the data file size in kilobytes by appending K to the size value. InnoDB: An insert buffer merge would cause an assertion error due to incorrectly handled ownership information for externally stored BLOBs. InnoDB: Assertion failure in thread thread_num in file ibuf0ibuf.cc line 4080 InnoDB: Failing assertion: rec_get_deleted_flag(rec, page_is_comp(page)) InnoDB: Decreasing the auto_increment_increment value would have no affect on the next auto-increment value. Replication: The server did not handle correctly the insertion of a row larger than 4 GB when using row-based replication. Replication: When using row-based replication, an additional auto-increment column on the slave version of a table was not updated correctly; a zero was inserted instead. Replication: Statements involving the Performance Schema tables should not be written to the binary log, because the content of these tables is applicable only to a given MySQL Server instance, and may differ greatly between different servers in a replication topology. The database administrator should be able to configure (INSERT, UPDATE, or DELETE) or flush (TRUNCATE TABLE) performance schema tables on a single server without affecting others. However, when replicating from a MySQL 5.5 master to a MySQL 5.5 or later slave, warnings about unsafe statements updating Performance Schema tables were elevated to errors. For MySQL 5.6 and later slaves, this prevented the simultaneous use of performance_schema and GTIDs (see Replication with Global Transaction Identifiers, in the MySQL 5.6 Manual). This fix causes all updates on tables in the performance_schema database to be filtered on the master and not replicated, regardless of the type of logging that is in effect. Prior to this fix, statements using were handled by being marked as unsafe for replication, which caused warnings during execution; the statements were nonetheless written to the binary log, regardless of the logging format in effect. Existing replication behavior for tables in the INFORMATION_SCHEMA database is not changed by this fix. For more information, see MySQL Performance Schema. Compilation failed if MySQL was configured with CFLAGS set to include a -Werror option with an argument. A shared libmysqld embedded server library was not built on Linux. While printing the server version, the mysql client did not check for buffer overflow in a string variable. Contraction information in a collation could be mishandled, resulting in incorrect decisions about whether a character is part of a contraction, and miscalculation of contraction weights. DROP TRIGGER succeeded even with the read_only system variable enabled. Updating the Performance Schema setup_instruments table on a replication master caused a slave to exit. Due to a race condition, it was possible for two threads to end up with the same query ID for different queries. When run by root, mysqld --help --verbose exited with a nonzero error code after displaying the help message. MySQL client programs from a Community Edition distribution could not connect using SSL to a MySQL server from an Enterprise Edition. This was due to a difference in certificate handling by yaSSL and OpenSSL (used for Community and Enterprise, respectively). OpenSSL expected a blank certificate to be sent when not all of the --ssl-ca, --ssl-cert, and --ssl-key options were specified, and yaSSL did not do so. To resolve this, yaSSL has been modified to send a blank certificate when an option is missing. A deadlock error occurring during subquery execution could cause an assertion to be raised. The Performance Schema stage/sql/Waiting to get readlock instrument is no longer used and has been removed. For system variables that take a string value, SET statements permitted an unquoted value, but values that contained dots were parsed incorrectly and only part of the value was assigned. For example, SET GLOBAL slow_query_log_file = my_slow.log assigned the value my_slow. Now such values must be quoted or an error occurs. On Windows, mysql_install_db.pl could be run only from within the bin directory under the installation directory.
Revision 1.16 / (download) - annotate - [select for diffs], Mon Mar 31 08:03:22 2014 UTC (9 years, 8 months ago) by adam
Branch: MAIN
Changes since 1.15: +1 -2
lines
Diff to previous 1.15 (colored)
Changes 5.5.37: Functionality Added or Changed On Solaris, mysql_config --libs now includes -R/path/to/library so that libraries can be found at runtime. Bugs Fixed InnoDB: A regression introduced by Bug 14329288 would result in a performance degradation when a compressed table does not fit into memory. InnoDB: The maximum value for innodb_thread_sleep_delay is now 1000000 microseconds. The previous maximum value (4294967295 microseconds on 32-bit and 18446744073709551615 microseconds on 64-bit) was unnecessarily large. Because the maximum value of innodb_thread_sleep_delay is limited by the value set for innodb_adaptive_max_sleep_delay (when set to a non-zero value), the maximum value for innodb_thread_sleep_delay is now the same as the maximum value for innodb_adaptive_max_sleep_delay. InnoDB: In debug builds, creating a unique index on a binary column, with input data containing duplicate keys, would cause an assertion. InnoDB: InnoDB would fail to start when innodb_data_file_path specified the data file size in kilobytes by appending K to the size value. InnoDB: An insert buffer merge would cause an assertion error due to incorrectly handled ownership information for externally stored BLOBs. InnoDB: Assertion failure in thread thread_num in file ibuf0ibuf.cc line 4080 InnoDB: Failing assertion: rec_get_deleted_flag(rec, page_is_comp(page)) InnoDB: Decreasing the auto_increment_increment value would have no affect on the next auto-increment value. Replication: The server did not handle correctly the insertion of a row larger than 4 GB when using row-based replication. Replication: When using row-based replication, an additional auto-increment column on the slave version of a table was not updated correctly; a zero was inserted instead. Replication: Statements involving the Performance Schema tables should not be written to the binary log, because the content of these tables is applicable only to a given MySQL Server instance, and may differ greatly between different servers in a replication topology. The database administrator should be able to configure (INSERT, UPDATE, or DELETE) or flush (TRUNCATE TABLE) performance schema tables on a single server without affecting others. However, when replicating from a MySQL 5.5 master to a MySQL 5.5 or later slave, warnings about unsafe statements updating Performance Schema tables were elevated to errors. For MySQL 5.6 and later slaves, this prevented the simultaneous use of performance_schema and GTIDs (see Replication with Global Transaction Identifiers, in the MySQL 5.6 Manual). This fix causes all updates on tables in the performance_schema database to be filtered on the master and not replicated, regardless of the type of logging that is in effect. Prior to this fix, statements using were handled by being marked as unsafe for replication, which caused warnings during execution; the statements were nonetheless written to the binary log, regardless of the logging format in effect. Existing replication behavior for tables in the INFORMATION_SCHEMA database is not changed by this fix. For more information, see MySQL Performance Schema. Compilation failed if MySQL was configured with CFLAGS set to include a -Werror option with an argument. A shared libmysqld embedded server library was not built on Linux. While printing the server version, the mysql client did not check for buffer overflow in a string variable. Contraction information in a collation could be mishandled, resulting in incorrect decisions about whether a character is part of a contraction, and miscalculation of contraction weights. DROP TRIGGER succeeded even with the read_only system variable enabled. Updating the Performance Schema setup_instruments table on a replication master caused a slave to exit. Due to a race condition, it was possible for two threads to end up with the same query ID for different queries. When run by root, mysqld --help --verbose exited with a nonzero error code after displaying the help message. MySQL client programs from a Community Edition distribution could not connect using SSL to a MySQL server from an Enterprise Edition. This was due to a difference in certificate handling by yaSSL and OpenSSL (used for Community and Enterprise, respectively). OpenSSL expected a blank certificate to be sent when not all of the --ssl-ca, --ssl-cert, and --ssl-key options were specified, and yaSSL did not do so. To resolve this, yaSSL has been modified to send a blank certificate when an option is missing. A deadlock error occurring during subquery execution could cause an assertion to be raised. The Performance Schema stage/sql/Waiting to get readlock instrument is no longer used and has been removed. For system variables that take a string value, SET statements permitted an unquoted value, but values that contained dots were parsed incorrectly and only part of the value was assigned. For example, SET GLOBAL slow_query_log_file = my_slow.log assigned the value my_slow. Now such values must be quoted or an error occurs. On Windows, mysql_install_db.pl could be run only from within the bin directory under the installation directory.
Revision 1.15 / (download) - annotate - [select for diffs], Wed Feb 12 23:17:39 2014 UTC (9 years, 9 months ago) by tron
Branch: MAIN
CVS Tags: pkgsrc-2014Q1-base
Branch point for: pkgsrc-2014Q1
Changes since 1.14: +2 -1
lines
Diff to previous 1.14 (colored)
Recursive PKGREVISION bump for OpenSSL API version bump.
Revision 1.14 / (download) - annotate - [select for diffs], Thu Dec 5 14:20:02 2013 UTC (10 years ago) by wiz
Branch: MAIN
CVS Tags: pkgsrc-2013Q4-base,
pkgsrc-2013Q4
Changes since 1.13: +2 -2
lines
Diff to previous 1.13 (colored)
Remove CONFLICTS with ${PKGBASE}, these are automatic.
Avoids unnecessary pkgin warning.
Revision 1.13 / (download) - annotate - [select for diffs], Mon Sep 30 18:26:38 2013 UTC (10 years, 2 months ago) by adam
Branch: MAIN
Changes since 1.12: +1 -2
lines
Diff to previous 1.12 (colored)
Changes 5.5.34: * MySQL 5.7 changed audit log file output to a new format that has better compatibility with Oracle Audit Vault. This format has been backported to MySQL 5.5 and it is possible to select either the old or new format using the new audit_log_format system variable, which has permitted values of OLD and NEW (default OLD). For details about each format, see The Audit Log File. * InnoDB; Partitioning: Following any query on the INFORMATION_SCHEMA.PARTITIONS table, InnoDB index statistics as shown in the output of statements such as SELECT * FROM INFORMATION_SCHEMA.STATISTICS were read from the last partition, instead of from the partition containing the greatest number of rows. * InnoDB: The row_sel_sec_rec_is_for_clust_rec function would incorrectly prepare to compare a NULL column prefix in a secondary index with a non-NULL column in a clustered index. * InnoDB: An incorrect purge would occur when rolling back an update to a delete-marked record. * InnoDB: InnoDB would rename a user-defined foreign key constraint containing the string ×Àibfk_ãàin its name, resulting in a duplicate constraint. * InnoDB: Rolling back an INSERT after a failed BLOB write would result in an assertion failure. The assertion has been modified to allow NULL BLOB pointers if an error occurs during a BLOB write. * InnoDB: A regression introduced with the fix for Bug 11762038 would cause InnoDB to raise an incorrect error message. The message stated that, ãàתnnoDB cannot delete/update rows with cascading foreign key constraints that exceed max depth of 20ãà The error message would occur when killing connections reading from InnoDB tables that did not have foreign key constraints. * InnoDB: The documentation incorrectly stated that START TRANSACTION WITH CONSISTENT SNAPSHOT provides a consistent snapshot only if the current isolation level is REPEATABLE READ or SERIALIZABLE. START TRANSACTION WITH CONSISTENT SNAPSHOT only works with REPEATABLE READ. All other isolation levels are ignored. The documentation has been revised and a warning is now generated whenever the WITH CONSISTENT SNAPSHOT clause is ignored. * InnoDB: The srv_master_thread background thread, which monitors server activity and performs activities such as page flushing when the server is inactive or in a shutdown state, runs on a one second delay loop. srv_master_thread would fail to check if the server is in a shutdown state before sleeping. more...
Revision 1.12 / (download) - annotate - [select for diffs], Sat Aug 31 02:08:32 2013 UTC (10 years, 3 months ago) by taca
Branch: MAIN
CVS Tags: pkgsrc-2013Q3-base,
pkgsrc-2013Q3
Changes since 1.11: +6 -7
lines
Diff to previous 1.11 (colored)
Always create symbolic links avoid to use ".so" macro and stop ugly messages from daily (or weekly). Rebuilding man page index: man-gpl-tmp2/mysql_client_test.1: No such file or directory man-gpl-tmp2/mysqltest.1: No such file or directory Bump PKGREVISION.
Revision 1.8.2.1 / (download) - annotate - [select for diffs], Mon Aug 5 10:10:15 2013 UTC (10 years, 4 months ago) by tron
Branch: pkgsrc-2013Q2
Changes since 1.8: +2 -1
lines
Diff to previous 1.8 (colored) next main 1.9 (colored)
Pullup ticket #4200 - requested by spz databases/mysql55-client: distfile update databases/mysql55-server: distfile update Revisions pulled up: - databases/mysql55-client/Makefile 1.10 via patch - databases/mysql55-client/Makefile.common 1.29 - databases/mysql55-client/distinfo 1.24 - databases/mysql55-server/Makefile 1.14 via patch --- Module Name: pkgsrc Committed By: adam Date: Wed Jul 17 21:22:40 UTC 2013 Modified Files: pkgsrc/databases/mysql55-client: Makefile Makefile.common distinfo pkgsrc/databases/mysql55-server: Makefile Log Message: Distfile got changed (licence clause in mans). Revision bump. Don't use mk/readline.buildlink3.mk! Must be devel/readline/buildlink3.mk!
Revision 1.11 / (download) - annotate - [select for diffs], Wed Jul 31 18:51:41 2013 UTC (10 years, 4 months ago) by adam
Branch: MAIN
Changes since 1.10: +1 -2
lines
Diff to previous 1.10 (colored)
Changes 5.5.33: * Previously, program options could be specified in full or as any unambiguous prefix. For example, the --compress option could be given to mysqldump as --compr, but not as --comp because the latter is ambiguous. Option prefixes now are deprecated. They can cause problems when new options are implemented for programs. A prefix that is currently unambiguous might become ambiguous in the future. If an unambiguous prefix is given, a warning now occurs to provide feedback. For example: Warning: Using unique option prefix compr instead of compress is deprecated and will be removed in a future release. Please use the full name instead. Option prefixes are no longer supported in MySQL 5.7; only full options are accepted. * comp_err now checks to make sure that new errors are not being added to MySQL 5.1 or 5.5 because the set of errors for these series is frozen. * Bugs Fixed
Revision 1.10 / (download) - annotate - [select for diffs], Wed Jul 17 21:22:40 2013 UTC (10 years, 4 months ago) by adam
Branch: MAIN
Changes since 1.9: +2 -2
lines
Diff to previous 1.9 (colored)
Distfile got changed (licence clause in mans). Revision bump. Don't use mk/readline.buildlink3.mk! Must be devel/readline/buildlink3.mk!
Revision 1.9 / (download) - annotate - [select for diffs], Mon Jul 15 02:02:19 2013 UTC (10 years, 4 months ago) by ryoon
Branch: MAIN
Changes since 1.8: +2 -2
lines
Diff to previous 1.8 (colored)
* .include "../../devel/readline/buildlink3.mk" with USE_GNU_READLINE=yes are replaced with .include "../../devel/readline/buildlink3.mk", and USE_GNU_READLINE are removed, * .include "../../devel/readline/buildlink3.mk" without USE_GNU_READLINE are replaced with .include "../../mk/readline.buildlink3.mk".
Revision 1.8 / (download) - annotate - [select for diffs], Tue Jun 4 13:31:21 2013 UTC (10 years, 6 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2013Q2-base
Branch point for: pkgsrc-2013Q2
Changes since 1.7: +2 -2
lines
Diff to previous 1.7 (colored)
Changes 5.5.32: * mysql_upgrade now verifies that the server version matches the version against which it was compiled, and exits if there is a mismatch. In addiion, a --version-check option permits specifying whether to enable version checking (the default), or disable checking if given as --skip-version-checking. * Bugs Fixed
Revision 1.7 / (download) - annotate - [select for diffs], Fri May 31 12:39:47 2013 UTC (10 years, 6 months ago) by wiz
Branch: MAIN
Changes since 1.6: +2 -1
lines
Diff to previous 1.6 (colored)
Bump all packages for perl-5.18, that a) refer 'perl' in their Makefile, or b) have a directory name of p5-*, or c) have any dependency on any p5-* package Like last time, where this caused no complaints.
Revision 1.6 / (download) - annotate - [select for diffs], Tue Feb 12 20:36:28 2013 UTC (10 years, 9 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2013Q1-base,
pkgsrc-2013Q1
Changes since 1.5: +4 -5
lines
Diff to previous 1.5 (colored)
Changes 5.5.30: Refer to http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-30.html
Revision 1.5 / (download) - annotate - [select for diffs], Wed Feb 6 23:20:54 2013 UTC (10 years, 10 months ago) by jperkin
Branch: MAIN
Changes since 1.4: +2 -1
lines
Diff to previous 1.4 (colored)
PKGREVISION bumps for the security/openssl 1.0.1d update.
Revision 1.4 / (download) - annotate - [select for diffs], Thu Jan 3 21:23:04 2013 UTC (10 years, 11 months ago) by adam
Branch: MAIN
Changes since 1.3: +1 -2
lines
Diff to previous 1.3 (colored)
Changes 5.5.29: * The SHOW AUTHORS and SHOW CONTRIBUTORS statements are now deprecated in MySQL 5.5 and have been removed in MySQL 5.6. * Bugs Fixed
Revision 1.3 / (download) - annotate - [select for diffs], Sat Dec 22 10:56:14 2012 UTC (10 years, 11 months ago) by tron
Branch: MAIN
CVS Tags: pkgsrc-2012Q4-base,
pkgsrc-2012Q4
Changes since 1.2: +12 -2
lines
Diff to previous 1.2 (colored)
Fix mysql_client_test_embedded(1) and mysqltest_embedded(1) manual pages in case the package gets built with manual page compression. Bump package revivison because of this bug fix.
Revision 1.2 / (download) - annotate - [select for diffs], Wed Oct 3 21:54:13 2012 UTC (11 years, 2 months ago) by wiz
Branch: MAIN
Changes since 1.1: +2 -1
lines
Diff to previous 1.1 (colored)
Bump all packages that use perl, or depend on a p5-* package, or are called p5-*. I hope that's all of them.
Revision 1.1.1.1 / (download) - annotate - [select for diffs] (vendor branch), Mon Apr 25 21:12:52 2011 UTC (12 years, 7 months ago) by adam
Branch: TNF
CVS Tags: pkgsrc-base,
pkgsrc-2012Q3-base,
pkgsrc-2012Q3,
pkgsrc-2012Q2-base,
pkgsrc-2012Q2,
pkgsrc-2012Q1-base,
pkgsrc-2012Q1,
pkgsrc-2011Q4-base,
pkgsrc-2011Q4,
pkgsrc-2011Q3-base,
pkgsrc-2011Q3,
pkgsrc-2011Q2-base,
pkgsrc-2011Q2
Changes since 1.1: +0 -0
lines
Diff to previous 1.1 (colored)
MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL client programs and libraries.
Revision 1.1 / (download) - annotate - [select for diffs], Mon Apr 25 21:12:52 2011 UTC (12 years, 7 months ago) by adam
Branch: MAIN
Initial revision