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

mariadb-client-5.5 conflicts with package mytop

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 5.5.27
    • Fix Version/s: 5.5.28
    • Component/s: None
    • Labels:
      None

      Description

      Recently in MDEV-286, the mytop program was added to mariadb-client-5.5 .deb.

      But this is a problem - because there is already a standalone debian/ubuntu mytop package. So now install/upgrade of mariadb-client-5.5 conflicts if mytop is already installed.

      I do not think there is a pressing need to deliver an alternative to mytop on .deb platforms, so I suggest just removing mytop again from .deb.

      However, if we really want to provide an alternative .deb for mytop, then we

      • need to put it in a separate package, with proper /usr/share/doc/mytop/* and so on
      • need to create correct dependencies so upgrades will go smooth
      • need to check existing mytop package - there are a number of patches included, and we need to review them and include relevant ones so users do not loose important functionality in the upgrade

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

              Hide
              jb-boin Jean Weisbuch added a comment -

              Here is the error that is produced during the apt-get/dpkg operation :
              --------
              Preparing to replace mariadb-client-5.5 5.5.25-mariadb1~squeeze (using .../mariadb-client-5.5_5.5.27-mariadb1~squeeze_i386.deb) ...
              Unpacking replacement mariadb-client-5.5 ...
              dpkg: error processing /var/cache/apt/archives/mariadb-client-5.5_5.5.27-mariadb1~squeeze_i386.deb (--unpack):
              trying to overwrite '/usr/bin/mytop', which is also in package mytop 1.6-6
              configured to not write apport reports
              dpkg-deb: subprocess paste killed by signal (Broken pipe)
              Processing triggers for man-db ...
              Errors were encountered while processing:
              /var/cache/apt/archives/mariadb-client-5.5_5.5.27-mariadb1~squeeze_i386.deb
              E: Sub-process /usr/bin/dpkg returned an error code (1)
              --------

              Workaround :
              To avoid/correct the problem, remove the mytop package by doing : dpkg -r mytop
              Then (if you did try to install the mariadb-client-5.5 package before removing mytop), re-try the package installation by doing : apt-get -f install

              There is another small issue on this mytop version if you want it to drop-in replace the debian one : by default the debian packaged mytop will connect on the "mysql" database and the Maria one try to connect on the "test" database, if you dont have an existing database named "test", mytop will fail to start with this error :
              Unknown database 'test'

              To workaround that, you can add "database=mysql" (as all servers will have a "mysql" database) on your ~/.my.cnf or ~/.mytop (depending on which file you use).
              Another solution is to specify the "mysql" databse instead of "test" as the default setting on /usr/bin/mytop at line 80 (but if its not modified upstream you will have to modify that again on the next update).

              Show
              jb-boin Jean Weisbuch added a comment - Here is the error that is produced during the apt-get/dpkg operation : -------- Preparing to replace mariadb-client-5.5 5.5.25-mariadb1~squeeze (using .../mariadb-client-5.5_5.5.27-mariadb1~squeeze_i386.deb) ... Unpacking replacement mariadb-client-5.5 ... dpkg: error processing /var/cache/apt/archives/mariadb-client-5.5_5.5.27-mariadb1~squeeze_i386.deb (--unpack): trying to overwrite '/usr/bin/mytop', which is also in package mytop 1.6-6 configured to not write apport reports dpkg-deb: subprocess paste killed by signal (Broken pipe) Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/mariadb-client-5.5_5.5.27-mariadb1~squeeze_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -------- Workaround : To avoid/correct the problem, remove the mytop package by doing : dpkg -r mytop Then (if you did try to install the mariadb-client-5.5 package before removing mytop), re-try the package installation by doing : apt-get -f install There is another small issue on this mytop version if you want it to drop-in replace the debian one : by default the debian packaged mytop will connect on the "mysql" database and the Maria one try to connect on the "test" database, if you dont have an existing database named "test", mytop will fail to start with this error : Unknown database 'test' To workaround that, you can add "database=mysql" (as all servers will have a "mysql" database) on your ~/.my.cnf or ~/.mytop (depending on which file you use). Another solution is to specify the "mysql" databse instead of "test" as the default setting on /usr/bin/mytop at line 80 (but if its not modified upstream you will have to modify that again on the next update).
              Hide
              elenst Elena Stepanova added a comment -

              See also https://bugs.launchpad.net/maria/+bug/1047337 (needs to be updated when the problem is fixed).

              Show
              elenst Elena Stepanova added a comment - See also https://bugs.launchpad.net/maria/+bug/1047337 (needs to be updated when the problem is fixed).
              Hide
              knielsen Kristian Nielsen added a comment -

              Fix (removing mytop from mariadb-client-5.5 .deb) pushed to lp:maria/5.5

              Show
              knielsen Kristian Nielsen added a comment - Fix (removing mytop from mariadb-client-5.5 .deb) pushed to lp:maria/5.5

                People

                • Assignee:
                  knielsen Kristian Nielsen
                  Reporter:
                  knielsen Kristian Nielsen
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  6 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 - 1 hour
                    1h