centos5_mariadb5_upgrade.txt
[MDEV-4896] Older RPMs Not Being Removed During Upgrade Created: 2013-08-14 Updated: 2014-04-18 Resolved: 2014-04-18 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | None |
| Affects Version/s: | 5.5.32 |
| Fix Version/s: | 5.5.37 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Will Fong | Assignee: | Sergei Golubchik |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | packaging | ||
| Environment: |
CentOS 5 |
||
| Attachments: |
centos5_mariadb5_upgrade.txt
|
| Description |
|
In CentOS 5, when upgrading a minor release of 5.5 (only tested 5.5.30->5.5.31, 5.5.31->5.5.32), if the mysqld server instance is not running, the previous MariaDB-server package is not removed. The server itself has successfully been upgraded. This seems to only affect upgrading CentOS 5, not CentOS 6, and only if the service instance is not running. This seems to indicate an RPM packaging issue. It looks to be because of the post uninstall script, as seen by this error: %postun(MariaDB-server-5.5.31-1.x86_64) scriptlet failed, exit status 3 Attached shows the old RPM still present in the system. Thanks, |
| Comments |
| Comment by Hoffmann Liu [ 2014-01-06 ] |
|
I can confirm this one with 10.0.x too. I am using Centos 5.7 and this happens when I updated from 10.0.6 to 10.0.7 too. But I think this doesn't happen too all of my CentOS 5 servers , however. Just some of them do. |