2020-03-13 11:05:43 by Nia Alarie | Files touched by this commit (76) | ![Package removed](https://pkgsrc.se/images/remove.gif) |
Log message:
*: Remove mysql51 - EOL since 2013, completely broken with OpenSSL 1.1
|
2020-01-18 22:51:16 by Jonathan Perkin | Files touched by this commit (1836) |
Log message:
*: Recursive revision bump for openssl 1.1.1.
|
2019-11-02 16:38:12 by Roland Illig | Files touched by this commit (115) |
Log message:
databases: align variable assignments
pkglint -Wall -F --only aligned -r
No manual corrections.
|
2019-08-11 15:25:21 by Thomas Klausner | Files touched by this commit (3557) |
Log message:
Bump PKGREVISIONs for perl 5.30.0
|
2019-04-30 19:20:23 by David Brownlee | Files touched by this commit (8) |
Log message:
Bump PKGREVISION for addition of USE_GCC_RUNTIME
|
2018-08-22 11:48:07 by Thomas Klausner | Files touched by this commit (3558) |
Log message:
Recursive bump for perl5-5.28.0
|
2018-01-01 23:30:04 by Roland Illig | Files touched by this commit (537) |
Log message:
Sort PLIST files.
Unsorted entries in PLIST files have generated a pkglint warning for at
least 12 years. Somewhat more recently, pkglint has learned to sort
PLIST files automatically. Since pkglint 5.4.23, the sorting is only
done in obvious, simple cases. These have been applied by running:
pkglint -Cnone,PLIST -Wnone,plist-sort -r -F
|
2017-06-24 17:18:43 by Amitai Schleier | Files touched by this commit (8) |
Log message:
Disassociate from controlling terminal (using Perl, already a
dependency) and run the logger as ${mysqld_user}, not root.
Bump PKGREVISIONs.
|
2017-04-13 15:44:49 by Makoto Fujiwara | Files touched by this commit (6) |
Log message:
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.
------------------------------------------------------------
|
2016-06-08 12:16:57 by Jonathan Perkin | Files touched by this commit (89) |
Log message:
Remove the stability entity, it has no meaning outside of an official context.
|