Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-3952

Incompatible change in MariaDB-5.5.28a-client rpm adds mytop when not in MariaDB-5.5.23-client (CentOS 5)

        Details

        • Type: Bug
        • Status: Closed
        • Priority: Major
        • Resolution: Fixed
        • Affects Version/s: 5.5.28a
        • Fix Version/s: 5.5.29
        • Component/s: None
        • Labels:

          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.

            Gliffy Diagrams

              Attachments

                Issue Links

                relates to

                Bug - A problem which impairs or prevents the functions of the product. MDEV-519 mariadb-client-5.5 conflicts with package mytop

                • Critical - Crashes, loss of data, severe memory leak.
                • Closed

                Bug - A problem which impairs or prevents the functions of the product. MDEV-286 mytop is not installed in 5.5

                • Major - Major loss of function.
                • Closed

                Task - A task that needs to be done. MDEV-4476 mytop tracker

                • Minor - Minor loss of function, or other problem where easy workaround is present.
                • Open

                  Activity

                  Hide
                  Permalink
                  sjmudd Simon Mudd added a comment -

                  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:

                  [root@myhost2 ~]# rpm -qa | grep -E '(MariaDB|mytop)'
MariaDB-common-5.5.25-1
MariaDB-server-5.5.23-1
MariaDB-client-5.5.25-1
mytop-1.4-2.el5.rf
[root@myhost2 ~]#

                  So it looks to me as if /usr/bin/mytop was added to MariaDB-client after version 5.5.25-1.

                  Show
                  sjmudd Simon Mudd added a comment - 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: [root@myhost2 ~]# rpm -qa | grep -E '(MariaDB|mytop)' MariaDB-common-5.5.25-1 MariaDB-server-5.5.23-1 MariaDB-client-5.5.25-1 mytop-1.4-2.el5.rf [root@myhost2 ~]# So it looks to me as if /usr/bin/mytop was added to MariaDB-client after version 5.5.25-1.

                    People

                    • Assignee:
                      serg Sergei Golubchik
                      Reporter:
                      sjmudd Simon Mudd
                    • Votes:
                      0 Vote for this issue
                      Watchers:
                      2 Start watching this issue

                      Dates

                      • Created:
                        Updated:
                        Resolved:

                        Time Tracking

                        Estimated:
                        Original Estimate - Not Specified
                        Not Specified
                        Remaining:
                        Remaining Estimate - 0 minutes
                        0m
                        Logged:
                        Time Spent - 10 minutes
                        10m