| Summary: | dev-db/mysql 5.5.32 stable request | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Guillaume Hilt <gentoo> |
| Component: | [OLD] Keywording and Stabilization | Assignee: | Gentoo Linux MySQL bugs team <mysql-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | bug, gentoo |
| Priority: | Normal | Keywords: | STABLEREQ |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Guillaume Hilt
2013-11-13 09:35:38 UTC
Please don't mark this version as a stable. Please look at http://bugs.mysql.com/bug.php?id=69623 , I'm also hitted by this bug. I had to downgrade mysql to older version. Probably 5.5.33 could be better candidate for stable. Where did you see that i was hit by a bug ? I'm using MySQL 5.5.32 without any issue. I'm simply requesting a 5.5 stable mysql. And what you're describing isn't a bug but a documented limitation. I've used word "also" in context of mysql bug, I didn't mean we both are affected by mentioned bug. " Added a changelog entry for 5.5.33, 5.6.13, 5.7.2: "InnoDB would fail to open a tablespace that has multiple data files." " So this, ekhm, "limitations" wasn't known when version 5.5.32 was relased. Imho it is documented bug. (When some software looses its 80% of capabilities and it's documented you still would call it as "limitations"?). I don't want to start flame, I just want to call attention there is serious issue in this version of mysql. And I'm voting to not mark this version as a stable. Sorry, i read your answer too quickly :) Well, a stable 5.3.33 would be good for me too, as long as it's a 5.5. *** This bug has been marked as a duplicate of bug 474800 *** |
