MySQL-5.7.9 was released on 2015-10-21 and was declared production ready. Would be nice to have it for experiments.
5.7.10 was just released: http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-10.html
Anything we can do to help? I might need to create an internal ebuild within a couple of weeks for MySQL 5.7, if it hasn't made it to portage by then. Would it be useful if I contributed the ebuild here? Is there anything in need of testing if any work has already begun on the issue? I could volunteer to help there as well.
(In reply to Guillaume Ceccarelli from comment #2) > Anything we can do to help? > > I might need to create an internal ebuild within a couple of weeks for MySQL > 5.7, if it hasn't made it to portage by then. Would it be useful if I > contributed the ebuild here? > Is there anything in need of testing if any work has already begun on the > issue? I could volunteer to help there as well. 5.7 is not able to be added because of a hard dependency on a version of dev-libs/boost which is not in the tree. (See the depending bug). I cannot even test it myself without adding it in an overlay.
(In reply to Brian Evans from comment #3) > (In reply to Guillaume Ceccarelli from comment #2) > > Anything we can do to help? > > > > I might need to create an internal ebuild within a couple of weeks for MySQL > > 5.7, if it hasn't made it to portage by then. Would it be useful if I > > contributed the ebuild here? > > Is there anything in need of testing if any work has already begun on the > > issue? I could volunteer to help there as well. > > 5.7 is not able to be added because of a hard dependency on a version of > dev-libs/boost which is not in the tree. (See the depending bug). I cannot > even test it myself without adding it in an overlay. I see. I'm sorry for the noise, I missed that there was a dependency. My offer still stands though. If something pops up in the future, I'll be glad to help. MySQL is at the heart of production infrastructures I manage, so I should keep being in a good spot to help test things in the foreseeable future.
5.7.11 was just released: http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-11.html
5.7.12 has been released: http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-12.html Anything we can do to help speed up the inclusion of the 5.7 series into the main portage tree? Extra hands for testing maybe? Anything else?
(In reply to Guillaume Ceccarelli from comment #6) > 5.7.12 has been released: > http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-12.html > > Anything we can do to help speed up the inclusion of the 5.7 series into the > main portage tree? Extra hands for testing maybe? Anything else? I need to review/update the rest of the Gentoo patch set. When it does get added, it will be masked because of the virtuals until MariaDB can provide a .so.20 client library
(In reply to Guillaume Ceccarelli from comment #6) > 5.7.12 has been released: > http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-12.html > > Anything we can do to help speed up the inclusion of the 5.7 series into the > main portage tree? Extra hands for testing maybe? Anything else? I tried 5.7.12 and there is a hard requirement on boost-1.59.0 and will not accept any other version. I could try to patch that out of the cmake scripts, but dunno if it will break anything.
(In reply to Brian Evans from comment #8) > (In reply to Guillaume Ceccarelli from comment #6) > > 5.7.12 has been released: > > http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-12.html > > > > Anything we can do to help speed up the inclusion of the 5.7 series into the > > main portage tree? Extra hands for testing maybe? Anything else? > > I tried 5.7.12 and there is a hard requirement on boost-1.59.0 and will not > accept any other version. I could try to patch that out of the cmake > scripts, but dunno if it will break anything. I can perform some tests with a version built against Boost 1.60 Both a standard OLTP and set up MySQL 5.7 against a staging system emulating a production-like workflow. Can grab you work somewhere? Overlay? Attachment to this bug?
your* work
(In reply to Guillaume Ceccarelli from comment #9) > (In reply to Brian Evans from comment #8) > > I tried 5.7.12 and there is a hard requirement on boost-1.59.0 and will not > > accept any other version. I could try to patch that out of the cmake > > scripts, but dunno if it will break anything. > > I can perform some tests with a version built against Boost 1.60 > > Both a standard OLTP and set up MySQL 5.7 against a staging system emulating > a production-like workflow. > > Can grab you work somewhere? Overlay? Attachment to this bug? 5.7.12 has just been posted to the Gentoo mysql overlay. Testing would be helpful particularly with the spacial geometry functions which use Boost. Oracle pegged boost at 1.59 exactly, but i fudged it.
The gis tests failed with boost-1.60. I guess we'll have to build a static boost in-line along with mysql. I'm not happy about this and debating if dev-db/mysql will continue to be in Gentoo. All over some functions that are not the most popular feature. I'll try the inline build then consider what it would take to disable gis functions before taking up the removal thought.
I've updated the ebuild in the mysql overlay to download and use boost-1.59 statically. Besides gis, mysqlpump tool uses libboost.a
(In reply to Brian Evans from comment #13) > I've updated the ebuild in the mysql overlay to download and use boost-1.59 > statically. I've just added the mysql repo in layman and unmasked the 5.7.12 package (and required virtuals) and tried to update, but unfortunately it fails almost immediately complaining about the version of boost: -- MySQL 5.7.12 -- Packaging as: mysql-5.7.12-Linux-i686 -- Found /usr/include/boost/version.hpp -- BOOST_VERSION_NUMBER is #define BOOST_VERSION 106100 CMake Warning at cmake/boost.cmake:266 (MESSAGE): Boost minor version found is 61 we need 59 Call Stack (most recent call first): CMakeLists.txt:451 (INCLUDE) Is there anything else I have to do to be able to test this out?
To anyone struggling with this issue - in the ebuild from mysql overlay src_configure should go as follows: src_configure() { local MYSQL_CMAKE_NATIVE_DEFINES=( -DWITH_LZ4=system -DWITH_NUMA=OFF ) local MYSQL_CMAKE_EXTRA_DEFINES=( -DWITH_BOOST="${WORKDIR}/boost_1_59_0" ) mysql-multilib-r1_src_configure } Otherwise on multilib builds 32bit configuration was still finding system boost, thus failing. I'm trying out building 5.7.12 right now and will go for 5.7.16 after that (I really need JSON support locally and within workbench GUI). Will report my findings.
Just a note from experimenting: the newest build from mysql overlay works flawlessly when built with ABI_X86="64" (without 32bit).
Me too I need MySQL 5.7 Tomorrow I will try from overlay It's not possible to merge into official tree with hard mask ?
Update on this issue would be much appreciated as MySQL 5.7 is becoming required on many new projects and has been stable for months now.
Can 5.7.* be finally imported into the main repository? Otherwise gentoo pretty much falls behind other production distros...
(In reply to Mikle Kolyada from comment #19) > Can 5.7.* be finally imported into the main repository? Otherwise gentoo > pretty much falls behind other production distros... At least hardmasked I meant
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2d09ba7465ce45ce75eb647f0c953e0b23cd6907 commit 2d09ba7465ce45ce75eb647f0c953e0b23cd6907 Author: Brian Evans <grknight@gentoo.org> AuthorDate: 2018-04-22 00:51:22 +0000 Commit: Brian Evans <grknight@gentoo.org> CommitDate: 2018-04-22 01:10:04 +0000 dev-db/mysql: Version bump for 5.7.22 Closes: https://bugs.gentoo.org/567590 Package-Manager: Portage-2.3.31, Repoman-2.3.9 dev-db/mysql/Manifest | 2 + dev-db/mysql/files/my.cnf-5.7 | 3 + dev-db/mysql/files/my.cnf.distro-client | 21 + dev-db/mysql/files/my.cnf.distro-server | 28 ++ dev-db/mysql/metadata.xml | 1 + dev-db/mysql/mysql-5.7.22.ebuild | 843 ++++++++++++++++++++++++++++++++ 6 files changed, 898 insertions(+)
