pkgsrc/databases/mysql51-client/distinfo

33 lines
1.9 KiB
Text
Raw Normal View History

$NetBSD: distinfo,v 1.30 2018/02/01 23:14:55 jperkin Exp $
Updated databases/mysql51-{client,server} to 5.1.73 ------------------------------------------------------------ The ChangeLog since 5.1.72 is too huge, so the beginning some lines are listed here: ------------------------------------------------------------ timestamp: Fri 2013-11-01 16:39:19 +0100 message: Bug#17617945 BUFFER OVERFLOW IN GET_MERGE_MANY_BUFFS_COST WITH SMALL SORT_BUFFER_SIZE get_cost_calc_buff_size() could return wrong value for the size of imerge_cost_buff. ------------------------------------------------------------ timestamp: Thu 2013-10-31 22:53:56 +0000 message: BUG#17662398: REMOVE DUPLICATE TEST CASES Remove duplicate test cases. ------------------------------------------------------------ timestamp: Thu 2013-10-31 23:02:44 +0530 message: Bug #12917164 DROP USER CAN'T DROP USERS WITH LEGACY UPPER CASE HOST NAME ANYMORE Description: It is not possible to drop users with host names with upper case letters in them. i.e DROP USER 'root'@'Tmp_Host_Name'; is failing with error. Analysis: Since the fix 11748570 we came up with lower case hostnames as standard. But in the current bug the hostname is created by mysql_install_db script is still having upper case hostnames. So, if we have the hostname with upper case letters like(Tmp_Host_Name) then we will have as it is stored in the mysql.user table. In this case if use "'DROP USER 'root'@'Tmp_Host_Name';" it gives error because we do compare with the lower case of hostname since the 11748570 fix. Fix: We need to convert the hostname to lower case before storing into the mysql.user table when we run the mysql_install_db script. ------------------------------------------------------------
2017-04-13 15:44:49 +02:00
SHA1 (mysql-5.1.73.tar.gz) = 6cb1c547dec873a0afda825c83fd8e5a32b9a619
RMD160 (mysql-5.1.73.tar.gz) = ceee36663abbf135d3ddbebe52ebc537ecba25a6
SHA512 (mysql-5.1.73.tar.gz) = 2e3651ebc1370dad7e01158cdd99133ed3f90c985114766b6282d58b743ae7bce16db797e82819fa5bbc2fa53d89811fd76b278c7459338288e7957634a8c3ff
Size (mysql-5.1.73.tar.gz) = 24023347 bytes
SHA1 (patch-aa) = 344bc9ab7013fbf64be6adbe8a9fc6279887beb1
2011-03-18 06:39:58 +01:00
SHA1 (patch-ab) = a1c699ebd9dc7e2cec9354035cbd9fdc2a411175
SHA1 (patch-ac) = a250b9797fbaad51d054cbb324feb0f7c29096d4
SHA1 (patch-ad) = 4e98f696b8b5098456e53a8de710a6bcd547997c
SHA1 (patch-ae) = 1bcec45f4cd221ba6e1d176caf01dbd3b3dbfa88
SHA1 (patch-af) = 6f310d2e033999bf2637659223bdd787f3954884
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
SHA1 (patch-am) = 162c97a87ab00b407f6796b55ef839ba2e3ac2af
SHA1 (patch-an) = a608060cee7aadaf8bcde84016a73131a75dea32
SHA1 (patch-ao) = dbf68af2d2ded85140aac3602d4f6ce5d68cc78a
SHA1 (patch-ap) = 6ebebc93e7bbcf4cd5bb7c9284c7587558a61784
SHA1 (patch-aq) = d04016a2ab84709aee0c08aef71c2f79e82fc6f3
SHA1 (patch-ar) = bc0e2083ec285be8adac1027e63bf076e4c57211
SHA1 (patch-as) = 5eb3a9308b13a25fa813db0ed4a06f8e43db74f6
SHA1 (patch-at) = b51e9044727447065cef267a469c481b66ccf64c
SHA1 (patch-au) = e454e1a4f4232e57f2105ac5150e1df0be709864
SHA1 (patch-av) = b8fb1065d7e71522374a16d759d2f3ab5227f590
SHA1 (patch-aw) = 50b811871b68506131020750f9af41e6834ec1cb
SHA1 (patch-ax) = 390debbc31e710f5aa41fda6a8b1134a14a2ff23
SHA1 (patch-ay) = 0b9c334c1e50c0c341e38d3fb189194de2d05b87
SHA1 (patch-client_mysql.cc) = 206914bcaac3ecb67968f27260a69634edc2e788
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