kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/databases/mysql51-client/distinfo

31 lines
1.7 KiB
Text
Raw Normal View History

Changes 5.1.72: * 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: 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. * InnoDB: An infinite loop could occur in buf_page_get_gen when handling compressed-only pages. * Within a stored program, comparison of the value of a scalar subquery with an IN clause resulted in an error for the first execution and raised an assertion for the second execution. * The my_strtoll10() function could incorrectly convert some long string-format numbers to numeric values and fail to set the overflow flag. * For queries that accessed an INFORMATION_SCHEMA table in a subquery, and attempt to lock a mutex that had already been locked could cause a server crash. * For DIV expressions, assignment of the result to multiple variables could cause a server crash. * mysqldump wrote SET statements as SET OPTION, which failed when reloaded because the deprecated OPTION keyword has been removed from SET syntax. * If one connection changed its default database and simultaneously another connection executed SHOW PROCESSLIST, the second connection could access invalid memory when attempting to display the first connection's default database. memory.
2013-10-01 13:00:39 +02:00
$NetBSD: distinfo,v 1.26 2013/10/01 11:00:39 adam Exp $
Importing mysql51-client 5.1.44, client part of MySQL 5.1.44. For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html 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.
2010-03-04 17:27:18 +01:00
Changes 5.1.72: * 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: 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. * InnoDB: An infinite loop could occur in buf_page_get_gen when handling compressed-only pages. * Within a stored program, comparison of the value of a scalar subquery with an IN clause resulted in an error for the first execution and raised an assertion for the second execution. * The my_strtoll10() function could incorrectly convert some long string-format numbers to numeric values and fail to set the overflow flag. * For queries that accessed an INFORMATION_SCHEMA table in a subquery, and attempt to lock a mutex that had already been locked could cause a server crash. * For DIV expressions, assignment of the result to multiple variables could cause a server crash. * mysqldump wrote SET statements as SET OPTION, which failed when reloaded because the deprecated OPTION keyword has been removed from SET syntax. * If one connection changed its default database and simultaneously another connection executed SHOW PROCESSLIST, the second connection could access invalid memory when attempting to display the first connection's default database. memory.
2013-10-01 13:00:39 +02:00
SHA1 (mysql-5.1.72.tar.gz) = af1f46e56402b38a085ac592cd7df3aa25e9cea2
RMD160 (mysql-5.1.72.tar.gz) = a5ba8bedf4027af90a4612a1a7f3a848999cfbf5
Size (mysql-5.1.72.tar.gz) = 24044338 bytes
* Install my_compiler.h as public header. It is already fixed in MySQL's repository. * Add comments to patches. Bump PKGREVISION and it fixes P$ pkg/43887.
2010-09-21 17:57:30 +02:00
SHA1 (patch-aa) = 344bc9ab7013fbf64be6adbe8a9fc6279887beb1
patch-ab: take 2
2011-03-18 06:39:58 +01:00
SHA1 (patch-ab) = a1c699ebd9dc7e2cec9354035cbd9fdc2a411175
* Install my_compiler.h as public header. It is already fixed in MySQL's repository. * Add comments to patches. Bump PKGREVISION and it fixes P$ pkg/43887.
2010-09-21 17:57:30 +02:00
SHA1 (patch-ac) = a250b9797fbaad51d054cbb324feb0f7c29096d4
Importing mysql51-client 5.1.44, client part of MySQL 5.1.44. For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html 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.
2010-03-04 17:27:18 +01:00
SHA1 (patch-ad) = 4e98f696b8b5098456e53a8de710a6bcd547997c
Changes 5.1.67: Bug fixes http://dev.mysql.com/doc/relnotes/mysql/5.1/en/news-5-1-67.html
2013-01-21 09:58:43 +01:00
SHA1 (patch-ae) = 1bcec45f4cd221ba6e1d176caf01dbd3b3dbfa88
SHA1 (patch-af) = 6f310d2e033999bf2637659223bdd787f3954884
* Install my_compiler.h as public header. It is already fixed in MySQL's repository. * Add comments to patches. Bump PKGREVISION and it fixes P$ pkg/43887.
2010-09-21 17:57:30 +02:00
SHA1 (patch-ag) = 20e4f5ac5e7b7927339b8c46329533f29a3df56f
SHA1 (patch-ah) = 715bef16c95e26f4abb39eb05fd23dbc9f7fa96b
SHA1 (patch-ai) = 625474e24c6f6c7b921ffd1534fd2ff93fdf02c8
SHA1 (patch-aj) = 5b67806269894c6f1725716f96433643260184db
Update mysql51-{client,server} package to 5.1.51, MySQL 5.1.51. For full changes, please refer: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-51.html Here is summary for security fixes: * Security Fix: During evaluation of arguments to extreme-value functions (such as LEAST() and GREATEST()), type errors did not propagate properly, causing the server to crash. (Bug#55826) * Security Fix: The server could crash after materializing a derived table that required a temporary table for grouping. (Bug#55568) * Security Fix: A user-variable assignment expression that is evaluated in a logical expression context can be precalculated in a temporary table for GROUP BY. However, when the expression value is used after creation of the temporary table, it was re-evaluated, not read from the table and a server crash resulted. (Bug#55564) * Security Fix: Pre-evaluation of LIKE predicates during view preparation could cause a server crash. (Bug#54568) * Security Fix: GROUP_CONCAT() and WITH ROLLUP together could cause a server crash. (Bug#54476) * Security Fix: Queries could cause a server crash if the GREATEST() or LEAST() function had a mixed list of numeric and LONGBLOB arguments, and the result of such a function was processed using an intermediate temporary table. (Bug#54461) * Security Fix: Queries with nested joins could cause an infinite loop in the server when used from stored procedures and prepared statements. (Bug#53544) * Security Fix: The PolyFromWKB() function could crash the server when improper WKB data was passed to the function. (Bug#51875)
2010-10-06 14:37:58 +02:00
SHA1 (patch-ak) = af5309d7a5b48042368936c7540f90df3dc4aafe
* Install my_compiler.h as public header. It is already fixed in MySQL's repository. * Add comments to patches. Bump PKGREVISION and it fixes P$ pkg/43887.
2010-09-21 17:57:30 +02:00
SHA1 (patch-am) = 162c97a87ab00b407f6796b55ef839ba2e3ac2af
Importing mysql51-client 5.1.44, client part of MySQL 5.1.44. For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html 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.
2010-03-04 17:27:18 +01:00
SHA1 (patch-an) = a608060cee7aadaf8bcde84016a73131a75dea32
SHA1 (patch-ao) = dbf68af2d2ded85140aac3602d4f6ce5d68cc78a
* Install my_compiler.h as public header. It is already fixed in MySQL's repository. * Add comments to patches. Bump PKGREVISION and it fixes P$ pkg/43887.
2010-09-21 17:57:30 +02:00
SHA1 (patch-ap) = 8d27b99a54071dce99f3b287676ed88c93028cc0
Importing mysql51-client 5.1.44, client part of MySQL 5.1.44. For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html 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.
2010-03-04 17:27:18 +01:00
SHA1 (patch-aq) = d04016a2ab84709aee0c08aef71c2f79e82fc6f3
SHA1 (patch-ar) = bc0e2083ec285be8adac1027e63bf076e4c57211
SHA1 (patch-as) = 5eb3a9308b13a25fa813db0ed4a06f8e43db74f6
Changes 5.1.67: Bug fixes http://dev.mysql.com/doc/relnotes/mysql/5.1/en/news-5-1-67.html
2013-01-21 09:58:43 +01:00
SHA1 (patch-at) = b51e9044727447065cef267a469c481b66ccf64c
* Install my_compiler.h as public header. It is already fixed in MySQL's repository. * Add comments to patches. Bump PKGREVISION and it fixes P$ pkg/43887.
2010-09-21 17:57:30 +02:00
SHA1 (patch-au) = e454e1a4f4232e57f2105ac5150e1df0be709864
Update mysql51-client and mysql51-server package to 5.1.58 (MySQL 5.1.58). This is bug fix release. Since whole changes are too many to write here, please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-58.html. Especially, some important one for related to us. * On FreeBSD 64-built builds of the embedded server, exceptions were not prevented from propagating into the embedded application. (Bug #38965, Bug #11749418)
2011-08-02 16:10:34 +02:00
SHA1 (patch-av) = b8fb1065d7e71522374a16d759d2f3ab5227f590
* Install my_compiler.h as public header. It is already fixed in MySQL's repository. * Add comments to patches. Bump PKGREVISION and it fixes P$ pkg/43887.
2010-09-21 17:57:30 +02:00
SHA1 (patch-aw) = 50b811871b68506131020750f9af41e6834ec1cb
Importing mysql51-client 5.1.44, client part of MySQL 5.1.44. For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html 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.
2010-03-04 17:27:18 +01:00
SHA1 (patch-ax) = 390debbc31e710f5aa41fda6a8b1134a14a2ff23
* Install my_compiler.h as public header. It is already fixed in MySQL's repository. * Add comments to patches. Bump PKGREVISION and it fixes P$ pkg/43887.
2010-09-21 17:57:30 +02:00
SHA1 (patch-ay) = 0b9c334c1e50c0c341e38d3fb189194de2d05b87
Changes 5.1.71: Functionality Added or Changed * 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 * InnoDB: During an insert buffer merge, InnoDB would invoke lock_rec_restore_from_page_infimum() on a potentially invalid record pointer. * InnoDB: The page_zip_validate() consistency check would fail after compressing a page, in page_zip_compress(). This problem was caused by page_zip_decompress(), which would fail to set heap_no correctly when a record contained no user data bytes. A record with no user data bytes occurs when, for example, a primary key is an empty string and all secondary index fields are NULL or an empty string. * InnoDB: The pthread_mutex, commit_threads_m, which was initialized but never used, has been removed from the code base. * Partitioning: When dropping a partitioned table, the table's .par file was deleted first, before the table definition or data. This meant that, if the server failed during the drop operation, the table could be left in an inconsistent state in which it could neither be accessed nor dropped. * Shared-compatibility conflict errors occurred for RPM install operations, even if no shared-compatibility RPMs were already installed. * A user variable referenced during execution of a prepared statement is set to memory that is freed at the end of execution. A second execution of the statement could result in Valgrind warnings when accessing this memory. * Misoptimization of left expressions in prepared statements could cause a server exit. * Subsequent to Prepared statement needs to be re-prepared errors, inserts into DECIMAL columns caused a server exit. * Assigning the result of a subquery to a user variable raised an assertion when the outer query included DISTINCT and GROUP BY.
2013-08-04 12:20:24 +02:00
SHA1 (patch-vio_viossl.c) = ad922587684a635a82c2fa662be7431c63063909
Reference in a new issue Copy permalink