Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
5.5.28a
-
None
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:
[root@myhost ~]# rpm -Uvh MariaDB-5.5.28a-centos5-x86_64-{server,client,common}.rpm
|
warning: MariaDB-5.5.28a-centos5-x86_64-server.rpm: Header V3 DSA signature: NOKEY, key ID 1bb943db
|
Preparing... ########################################### [100%]
|
file /usr/bin/mytop from install of MariaDB-client-5.5.28a-1.x86_64 conflicts with file from package mytop-1.4-2.el5.rf.noarch
|
[root@myhost ~]# rpm -Uvh MariaDB-5.5.28a-centos5-x86_64-{server,common}.rpm
|
warning: MariaDB-5.5.28a-centos5-x86_64-server.rpm: Header V3 DSA signature: NOKEY, key ID 1bb943db
|
Preparing... ########################################### [100%]
|
1:MariaDB-common ########################################### [ 50%]
|
2:MariaDB-server ########################################### [100%]
|
[root@myhost ~]#
|
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.
Attachments
Issue Links
- relates to
-
-
- Closed
-
-
-
- Closed
-
-
MDEV-4476 mytop tracker
-
- Closed
-
-
-
- Closed
-