Bug #2735 | GLIBC_2.3, GLIBC_2.3.2 | ||
---|---|---|---|
Submitted: | 12 Feb 2004 1:59 | Modified: | 22 Feb 2004 1:00 |
Reporter: | Roberto Della Grotta | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Administrator | Severity: | S3 (Non-critical) |
Version: | OS: | Linux (Linux Mandrake 9.0) | |
Assigned to: | Alfredo Kojima | CPU Architecture: | Any |
[12 Feb 2004 1:59]
Roberto Della Grotta
[22 Feb 2004 1:00]
Alfredo Kojima
Thank you for taking the time to report a problem. Unfortunately you are not using a current version of the product your reported a problem with -- the problem might already be fixed. Please download a new version from http://www.mysql.com/downloads/ If you are able to reproduce the bug with one of the latest versions, please change the version on this bug report to the version you tested and change the status back to "Open". Again, thank you for your continued support of MySQL. Additional info: Please try the newer version (1.0.2a) when it's released next week. It will be linked to an older version of glibc, which should work for you.