Bug #42953 | Enterprise 5.0.66sp1 to 5.0.72sp1 upgrade fails on RHEL5 | ||
---|---|---|---|
Submitted: | 18 Feb 2009 2:18 | Modified: | 29 Jul 2009 20:39 |
Reporter: | Roel Van de Paar | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server: Installing | Severity: | S2 (Serious) |
Version: | 5.0.66sp1 | OS: | Linux |
Assigned to: | Assigned Account | CPU Architecture: | Any |
[18 Feb 2009 2:18]
Roel Van de Paar
[18 Feb 2009 9:33]
Sveta Smirnova
Thank you for the report. Please explain what is the bug: corrupted letter in the MySQL AB or requirement in manual upgrade to 5.0.72 instead of just running rpm -U?
[18 Feb 2009 9:34]
Sveta Smirnova
Regarding to the corrupted letter please also send output of `locale`
[20 Feb 2009 2:16]
Roel Van de Paar
> Please explain what is the bug: corrupted letter in the MySQL AB or requirement in manual upgrade to 5.0.72 instead of just running rpm -U? Both :) though obviously the manual upgrade requirement is more important. > Regarding to the corrupted letter please also send output of `locale` locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL=
[20 Feb 2009 8:35]
Sveta Smirnova
Thank you for the feedback. Failed rpm-U verified as described. RHEL4 affected as well. But I can not repeat garbled "MySQL AB".
[21 Feb 2009 5:50]
Roel Van de Paar
Some more info: o Exact command used for attempting to upgrade MySQL originally: rpm -Uvh *.rpm after extracting the tarball and stopping the server o The upgrade was from 5.0.66sp1-0.rhel5.x86_64 to 5.0.72sp1-0.rhel5.x86_64
[17 Jun 2009 14:07]
Lars Heill
See also Bug#45534. Assigning this to Kent, too.
[29 Jul 2009 20:39]
Joerg Bruehe
This seems to be the same issue as the one reported in bug#45534, which I am currently working on. Therefore I grab this one, too. Yes, I know this is the older one, but the other was brought to my attention, so I set this one to "duplicate", explicitly acknowledging that the priority of telling us about the problem would demand the reverse relationship. My only excuse is that bug#45534 is referenced in support issues.