[MDEV-3952] Incompatible change in MariaDB-5.5.28a-client rpm adds mytop when not in MariaDB-5.5.23-client (CentOS 5) Created: 2012-12-19 Updated: 2020-05-26 Resolved: 2013-01-21 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | None |
| Affects Version/s: | 5.5.28a |
| Fix Version/s: | 5.5.29 |
| Type: | Bug | Priority: | Major |
| Reporter: | Simon Mudd | Assignee: | Sergei Golubchik |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | packaging | ||
| Issue Links: |
|
||||||||||||||||||||
| Description |
|
While maybe not a huge thing it's a nuisance if during minor version changes packages suddenly change. On a previously installed CentOS 5 server with MariaDB 5.5.23 server/client/common rpms installed I see that when trying to install the equivalent 5.5.28a packages there's a conflict with an already installed mytop package from a different source:
So if you want to provide mytop for the systems you have MariaDB 5.5 on please provide this as a separate package. If mytop is going to be installed on MariaDB 10 versions that's fine as there's no change, but don't break upgrades of existing systems as this is a nuisance. |
| Comments |
| Comment by Simon Mudd [ 2012-12-19 ] | ||||||
|
Note: a similar server, running CentOS release 5.4 (Final), which I haven't upgraded to MariaDB 5.5.28a is configured using the following packages:
So it looks to me as if /usr/bin/mytop was added to MariaDB-client after version 5.5.25-1. |