| Summary: | dev-db/mysql version bump to 5.0.70 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Wolfram Schlich (RETIRED) <wschlich> |
| Component: | Current packages | Assignee: | Gentoo Linux MySQL bugs team <mysql-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | CC: | asturm, Dessa, idl0r, jan+gentoo, mabi, mattsch, mno2go, Sergiy.Borodych, tais.hansen, tm |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | http://dev.mysql.com/doc/refman/5.0/en/releasenotes-es-5-0.html | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 237166 | ||
|
Description
Wolfram Schlich (RETIRED)
2008-08-01 09:17:09 UTC
Latest version is 5.0.68. Any status updates on this? I would be very happy, if this could go into portage... There are really some fixes, which are usefull (e.g. WBB3) agreed. i'm looking into migrating my wbbs away from mysql as wbb just keeps crashing here. could we have an up2date mysql? we have problem with http://bugs.mysql.com/bug.php?id=35480 that is fixed since 5.0.66, please update portage Latest version is 5.0.70. May we assume MySQL on Gentoo to be dead? Not dead. Just that as the only person on the MySQL team, I'm overworked in trying to port the Gentoo patchset to the newer versions. I can report a successful build of 5.0.67 with unmodified 5.0.60-r1 ebuild. Settings were: USE="embedded perl ssl" gcc-4.3.2 I can report a successful build (and use) of 5.0.68 with unmodified 5.0.60-r1 ebuild. Settings were: USE="extraengine ssl" gcc-4.3.2 (In reply to comment #8) > I can report a successful build (and use) of 5.0.68 with unmodified 5.0.60-r1 > ebuild. confirmed. And to give a little more info about my settings: Portage 2.2_rc13 (default/linux/amd64/2008.0/desktop, gcc-4.3.2, glibc-2.8_p20080602-r0, 2.6.27-ext4-r1 x86_64) CFLAGS="-march=k8-sse3 -O2 -pipe -finline-functions -ftree-vectorize" mysql USE="embedded perl ssl" *** Bug 246128 has been marked as a duplicate of this bug. *** Just so folks know, I haven't forgotten about this bug, I just haven't gotten to porting all the required patches (both the old ones and the new requested ones [like the google patchset]) to work smoothly yet. Thanks for the update, I appreciate your hard work! :) 5.0.70 is in the tree now, with the identical patchset to .60-r1. Later revisions of .70 will contain new patches. This release is just so that we can unblock the security bugs. My testing issues ultimately stemmed from very weird issues with FEATURES=usersandbox. Additionally, I do not have direct access to any big-endian boxes anymore, so I don't know if the archive_gis test has been fixed by upstream or not yet - I suspect not, so we may need to disable it in src_test like previous releases. Interesting, I emerged 5.0.70 last night, but the internal MySQL version is still reported as 5.0.60... is something wrong on my end or is it because you used the patches from 60-r1? (In reply to comment #14) > Interesting, I emerged 5.0.70 last night, but the internal MySQL version is > still reported as 5.0.60... is something wrong on my end or is it because you > used the patches from 60-r1? > i can confirm that. afaik points nothing in the patches to 5.0.60. (In reply to comment #14) > Interesting, I emerged 5.0.70 last night, but the internal MySQL version is > still reported as 5.0.60... is something wrong on my end or is it because you > used the patches from 60-r1? I don't see anything like that. Could you open new bug report and give us more details? Thanks. mysql> status -------------- mysql Ver 14.12 Distrib 5.0.70, for pc-linux-gnu (i686) using readline 5.2 [snip] Server version: 5.0.70-log Gentoo Linux mysql-5.0.70 [snip] -------------- (In reply to comment #14) > Interesting, I emerged 5.0.70 last night, but the internal MySQL version is > still reported as 5.0.60... is something wrong on my end or is it because you > used the patches from 60-r1? > For me version is correct too Server version: 5.0.70 Gentoo Linux mysql-5.0.70 Maybe you forgot restart mysql ? (In reply to comment #15) > (In reply to comment #14) > > Interesting, I emerged 5.0.70 last night, but the internal MySQL version is > > still reported as 5.0.60... is something wrong on my end or is it because you > > used the patches from 60-r1? > > > > i can confirm that. > afaik points nothing in the patches to 5.0.60. > ok in my case it was a problem with a 3rd party app. just ignore my comment (#15) :) (In reply to comment #14) > Interesting, I emerged 5.0.70 last night, but the internal MySQL version is > still reported as 5.0.60... is something wrong on my end or is it because you > used the patches from 60-r1? > Sorry nevermind, for me it was also an error in 3rd party app. Mysql status shows .70. :) |
