mariadb-10.7.3 is out. https://mariadb.org/mariadb/all-releases/ Reproducible: Always
Yeah, need bumps for all branches.
Security bug already exists, version bump bug is not a security bug.
Ping whissi
*** Bug 836823 has been marked as a duplicate of this bug. ***
mariadb-10.4.24 with security fixes fir 10.4 branch is available
Is there a reason updates get delayed? And is there something we can do to help?
@qa, FWICS the new version includes fixes for 5 CVEs. The maintainer has blocked the update almost a month ago based on unexplained "serious regressions" and has not replied since.
Other branches need doing.
This also blocks bug #832012, because upstream fixed the segfault in versions 10.5.16, 10.6.8, 10.7.4, 10.8.3 (cf. https://jira.mariadb.org/browse/MDEV-27900).
(In reply to Dennis Schridde from comment #9) > This also blocks bug #832012, because upstream fixed the segfault in > versions 10.5.16, 10.6.8, 10.7.4, 10.8.3 (cf. > https://jira.mariadb.org/browse/MDEV-27900). Sorry, I just noticed these versions are not yet released. Nevertheless a backport would probably be easier, if we had the latest released versions available in Gentoo.
https://bugs.gentoo.org/832490#c7 All done by now, I think.
(In reply to Sam James from comment #11) > https://bugs.gentoo.org/832490#c7 > > All done by now, I think. How? As latest releases are 10.8.3, 10.7.4, 10.6.8, 10.5.16, 10.4.25, 10.3.35, 10.2.44.
Oh right, 10.7.x and 10.8.x not done. But the rest are.
Seems like the release cycles are speeding up and 10.7, 10.8, 10.9 are only short living releases with EOL next year. The 10.6 branch will be supported until 07/2026. I know it would be best to have all versions in portage, but it takes some time and no Gentoo developer is doing it at the moment as @Whissi left Gentoo. https://mariadb.com/kb/en/mariadb-server-release-dates/
Could take a look into becomming a maintainer, but might take some time as I haven't spend much time on ebuilds yet. But the lack of proper builds is really becoming unworkable.
Not going to maintain this, do not have the required skill set to maintain the custom patchset.
Feedback for mariadb-10.11.1 from the PR is welcome. It passed the included tests and successfully updated from 10.6 to 10.11 on amd64. I'd skip 10.7 .. 10.10 as they'll EOL soon (as mentioned previously).
Don't see anything strange in the PR, will try to build and use it sometime this weekend.
/var/tmp/portage/dev-db/mariadb-10.11.1/temp/environment: line 1280: /var/tmp/portage/dev-db/mariadb-10.11.1/files/mariadb-10.6.12-gcc-13.patch: No such file or directory /var/tmp/portage/dev-db/mariadb-10.11.1/temp/environment: line 1283: /var/tmp/portage/dev-db/mariadb-10.11.1/files/mariadb-10.6.12-gcc-13.patch: No such file or directory [ !! ] * ERROR: dev-db/mariadb-10.11.1::gentoo failed (prepare phase): * patch -p1 failed with /var/tmp/portage/dev-db/mariadb-10.11.1/files/mariadb-10.6.12-gcc-13.patch * * Call stack: * ebuild.sh, line 136: Called src_prepare * environment, line 4397: Called eapply '/var/tmp/portage/dev-db/mariadb-10.11.1/files/mariadb-10.6.12-gcc-13.patch' * environment, line 1348: Called _eapply_patch '/var/tmp/portage/dev-db/mariadb-10.11.1/files/mariadb-10.6.12-gcc-13.patch' * environment, line 1286: Called __helpers_die 'patch -p1 failed with /var/tmp/portage/dev-db/mariadb-10.11.1/files/mariadb-10.6.12-gcc-13.patch' * isolated-functions.sh, line 112: Called die * The specific snippet of code: * die "$@" * * If you need support, post the output of `emerge --info '=dev-db/mariadb-10.11.1::gentoo'`, * the complete build log and the output of `emerge -pqv '=dev-db/mariadb-10.11.1::gentoo'`. !!! When you file a bug report, please include the following information: GENTOO_VM= CLASSPATH="" JAVA_HOME="/etc/java-config-2/current-system-vm" JAVACFLAGS="" COMPILER="" and of course, the output of emerge --info =mariadb-10.11.1 * The complete build log is located at '/var/log/portage/dev-db:mariadb-10.11.1:20230213-153753.log'. * For convenience, a symlink to the build log is located at '/var/tmp/portage/dev-db/mariadb-10.11.1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-db/mariadb-10.11.1/temp/environment'. * Working directory: '/var/tmp/portage/dev-db/mariadb-10.11.1/work/mysql' * S: '/var/tmp/portage/dev-db/mariadb-10.11.1/work/mysql'
(In reply to Michiel Hazelhof from comment #19) > /var/tmp/portage/dev-db/mariadb-10.11.1/temp/environment: line 1280: > /var/tmp/portage/dev-db/mariadb-10.11.1/files/mariadb-10.6.12-gcc-13.patch: > No such file or directory > /var/tmp/portage/dev-db/mariadb-10.11.1/temp/environment: line 1283: > /var/tmp/portage/dev-db/mariadb-10.11.1/files/mariadb-10.6.12-gcc-13.patch: > No such file or directory > [ !! ] > * ERROR: dev-db/mariadb-10.11.1::gentoo failed (prepare phase): > * patch -p1 failed with > /var/tmp/portage/dev-db/mariadb-10.11.1/files/mariadb-10.6.12-gcc-13.patch > * > * Call stack: > * ebuild.sh, line 136: Called src_prepare > * environment, line 4397: Called eapply > '/var/tmp/portage/dev-db/mariadb-10.11.1/files/mariadb-10.6.12-gcc-13.patch' > * environment, line 1348: Called _eapply_patch > '/var/tmp/portage/dev-db/mariadb-10.11.1/files/mariadb-10.6.12-gcc-13.patch' > * environment, line 1286: Called __helpers_die 'patch -p1 > failed with > /var/tmp/portage/dev-db/mariadb-10.11.1/files/mariadb-10.6.12-gcc-13.patch' > * isolated-functions.sh, line 112: Called die > * The specific snippet of code: > * die "$@" > * > * If you need support, post the output of `emerge --info > '=dev-db/mariadb-10.11.1::gentoo'`, > * the complete build log and the output of `emerge -pqv > '=dev-db/mariadb-10.11.1::gentoo'`. > !!! When you file a bug report, please include the following information: > GENTOO_VM= CLASSPATH="" JAVA_HOME="/etc/java-config-2/current-system-vm" > JAVACFLAGS="" COMPILER="" > and of course, the output of emerge --info =mariadb-10.11.1 > * The complete build log is located at > '/var/log/portage/dev-db:mariadb-10.11.1:20230213-153753.log'. > * For convenience, a symlink to the build log is located at > '/var/tmp/portage/dev-db/mariadb-10.11.1/temp/build.log'. > * The ebuild environment file is located at > '/var/tmp/portage/dev-db/mariadb-10.11.1/temp/environment'. > * Working directory: '/var/tmp/portage/dev-db/mariadb-10.11.1/work/mysql' > * S: '/var/tmp/portage/dev-db/mariadb-10.11.1/work/mysql' The patch is not in the repository yet, you can get it from: https://github.com/gentoo/gentoo/blob/121164b2dfa1f75469c9a9efce0a1e7f82ed2a6d/dev-db/mariadb/files/mariadb-10.6.12-gcc-13.patch https://raw.githubusercontent.com/gentoo/gentoo/121164b2dfa1f75469c9a9efce0a1e7f82ed2a6d/dev-db/mariadb/files/mariadb-10.6.12-gcc-13.patch
Compiled and upgraded just fine on ~AMD64, seems to work just fine after mysql_upgrade. Will keep everyone informed if something happens.
(In reply to Michiel Hazelhof from comment #21) > Compiled and upgraded just fine on ~AMD64, seems to work just fine after > mysql_upgrade. > > Will keep everyone informed if something happens. Thanks for testing Michiel!
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4fd429dd2c0b2a2fd2c519553560f1e7e3a02d1e commit 4fd429dd2c0b2a2fd2c519553560f1e7e3a02d1e Author: Tomáš Mózes <hydrapolic@gmail.com> AuthorDate: 2023-02-08 21:33:35 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2023-02-15 05:50:52 +0000 dev-db/mariadb: add 10.11.1 No keywords for now Closes: https://bugs.gentoo.org/833760 Signed-off-by: Tomáš Mózes <hydrapolic@gmail.com> Closes: https://github.com/gentoo/gentoo/pull/29498 Signed-off-by: Sam James <sam@gentoo.org> dev-db/mariadb/Manifest | 2 + dev-db/mariadb/mariadb-10.11.1.ebuild | 1319 +++++++++++++++++++++++++++++++++ dev-db/mariadb/mariadb-10.4.28.ebuild | 4 + dev-db/mariadb/mariadb-10.5.19.ebuild | 4 + dev-db/mariadb/mariadb-10.6.12.ebuild | 4 + 5 files changed, 1333 insertions(+)
(In reply to Tomáš Mózes from comment #22) > (In reply to Michiel Hazelhof from comment #21) > > Compiled and upgraded just fine on ~AMD64, seems to work just fine after > > mysql_upgrade. > > > > Will keep everyone informed if something happens. > > Thanks for testing Michiel! +1
Tried 10.11.2 (has a nice regression patch), but that fails unexpectedly: 1 out of 3 hunks FAILED -- saving rejects to file support-files/CMakeLists.txt.rej [ !! ] * ERROR: dev-db/mariadb-10.11.2::gentoo failed (prepare phase): * patch -p1 failed with /var/tmp/portage/dev-db/mariadb-10.11.2/work/mariadb-patches/0004-cmake-don-t-install-mysql-d-.service-symlinks.patch
(In reply to Michiel Hazelhof from comment #25) > Tried 10.11.2 (has a nice regression patch), but that fails unexpectedly: > > 1 out of 3 hunks FAILED -- saving rejects to file > support-files/CMakeLists.txt.rej > [ !! ] > * ERROR: dev-db/mariadb-10.11.2::gentoo failed (prepare phase): > * patch -p1 failed with > /var/tmp/portage/dev-db/mariadb-10.11.2/work/mariadb-patches/0004-cmake-don- > t-install-mysql-d-.service-symlinks.patch You can try https://github.com/gentoo/gentoo/pull/30079
Works, thanks
Mariadb 10.11 is LTS release. It's been stable since Feb 23 according to upstream https://mariadb.org/about/#maintenance-policy. Is there any reason why it isn't prefixed (~arch) yet?
On how many machines do you run it? The more reports the sooner we can add keywords.
Apologie if the previous comment sounded demanding. But I'm really curious. It builded fine on amd64. Let me know if you need more info/reports.
(In reply to Rahil Bhimjiani from comment #30) > Apologie if the previous comment sounded demanding. But I'm really curious. > It builded fine on amd64. Let me know if you need more info/reports. I'm migrating my prod instances to 10.6 and just started to migrate my testing instances to 10.11. KW added in https://github.com/gentoo/gentoo/pull/31847.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=97ac0ea14cca574ce4c9aaf8cd596e798b80b19f commit 97ac0ea14cca574ce4c9aaf8cd596e798b80b19f Author: Tomáš Mózes <hydrapolic@gmail.com> AuthorDate: 2023-07-12 11:54:01 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2023-07-13 07:58:50 +0000 dev-db/mariadb: restore keywords for 10.11.4 Bug: https://bugs.gentoo.org/833760 Signed-off-by: Tomáš Mózes <hydrapolic@gmail.com> Signed-off-by: Sam James <sam@gentoo.org> dev-db/mariadb/mariadb-10.11.4.ebuild | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
