Please bump, thanks :)
I would much rather see dev-db/mysql get a 5.1 ebuild. I don't think the mysql-community stuff is sticking around.
Version 5.1.20 was released with important NDB Cluster bugfixes...
*** Bug 190979 has been marked as a duplicate of this bug. ***
*** Bug 191062 has been marked as a duplicate of this bug. ***
Can this be bumped up in severity? There are important bug fixes in recent MySQL 5.1 (as well as new features) that are desperately needed on some of my production servers.
Since noone seems to care as long as 5.1 is in beta, i wrote a quick and very dirty howto on bumping to 5.1.21 http://forums.gentoo.org/viewtopic-t-579941-highlight-.html according to this guide on amd64 i have the following build results: big-tables WORKS debug DIDNT TRY embedded DIDNT TRY minimal DIDNT TRT perl WORKS selinux DIDNT TRY ssl WORKS static DIDNT TRY latin1 DIDNT TRY cluster WORKS extraengine WORKS max-idx-128 DOESNT WORK innodb WORKS pbxt DOESNT WORK
Don't worry, I haven't forgotten you. This will probably hit the tree at the same time as 5.0.48 in a few days. There's more critical failures at the moment however: ... FEATURES=test USE='cluster big-tables embedded extraengine' time ebuild mysql-community-5.1.21_beta.ebuild test ... Failed 1/511 tests, 99.80% were successful. ... main.mysql_client_test [ fail ] Errors are (from /dev/shm/portage/dev-db/mysql-community-5.1.21_beta/work/mysql/mysql-test/var/log/mysqltest-time) : sh: line 1: 18982 Aborted /dev/shm/portage/dev-db/mysql-community-5.1.21_beta/work/mysql/tests/mysql_client_test --no-defaults --testcase --user=root --port=9306 --socket=/dev/shm/portage/dev-db/mysql-community-5.1.21_beta/temp/WDggC00lh4/master.sock --vardir=/dev/shm/portage/dev-db/mysql-community-5.1.21_beta/work/mysql/mysql-test/var --getopt-ll-test=25600M >> /dev/shm/portage/dev-db/mysql-community-5.1.21_beta/work/mysql/mysql-test/var/log/mysql_client_test.log 2>&1 mysqltest: At line 12: command "$MYSQL_CLIENT_TEST --getopt-ll-test=25600M >> $MYSQLTEST_VARDIR/log/mysql_client_test.log 2>&1" failed (the last lines may be the most important ones) ...
in tree now.