Stabilization request. In portage is only 5.5.30. Reproducible: Always Steps to Reproduce: 1. install MariaDB-5.5.30 or 31 2. use it 3. Server: MariaDB 5.5.31 on Ubuntu 8.04 amd64 (EOL) seems work better than old MySQL 5.0.51a. On this server running huge Java with Hibernate framework. My computer: MariaDB 5.5.30 on Gentoo ~amd64, desktop usage (Amarok etc.) works perfect.
Created attachment 349498 [details] dev-db:mariadb-5.5.31:20130528-190925.log.gz The ebuild is in the overlay now, but there are multiple test failures, so it's NOT suitable for the main tree yet. main-pbxt.ctype_ucs2_query_cache [ fail ] main-pbxt.partition_pruning [ fail ] main-pbxt.group_by 'innodb_plugin' [ fail ] main-pbxt.subselect2 'innodb_plugin' [ fail ] main-pbxt.subselect_innodb 'innodb_plugin' [ fail ] main-pbxt.subselect_sj2 'innodb_plugin' [ fail ] main-pbxt.subselect_sj2_mat 'innodb_plugin' [ fail ] main-pbxt.group_by 'xtradb' [ fail ] main-pbxt.subselect2 'xtradb' [ fail ] main-pbxt.subselect_innodb 'xtradb' [ fail ] Compressed log is attached.
Sergii: please see the test failures in 5.5.31 I attached in the previous comment.
We don't build pbxt in 5.5 anymore. It's disabled by default, unless enabled explicitly. Why do you guys enable it?
It is disabled by default, users need to select USE=pbxt, I just test with it enabled for coverage.
I'd suggest to remove pbxt from IUSE. It seems to be not maintained, and it is certainly not supported in MariaDB 5.5 anymore.
jmbsvicetto and I discussed the pbxt issue on irc a week or so ago. Perhaps it is best to deprecate USE="pbxt" as it has basically been abandoned by its author. http://www.primebase.org is also unavailable. I've personally seen storage engine level errors when it came to primary keys on pbxt.
well, I vote for masking pxbt USE and add it to portage :) and then stabilizate it.
*** Bug 471012 has been marked as a duplicate of this bug. ***
The pbxt use flag was masked and mariadb-5.5.31 added to the overlay and tree.
