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

Problem when upgrading from 10.0.4 to 10.0.5 on Debian

    Details

      Description

      I tried to upgrade MariaDB from 10.0.4 to 10.0.5 on my Debian Wheezy installation. 10.0.4 was a clean installation (no previous MySQL). I didn't do anything which could have broken dependencies or something else.

      I got this error when upgrading :

      dpkg: error processing /var/cache/apt/archives/libmariadbclient18_10.0.5+maria-1~wheezy_amd64.deb (--unpack) :
       trying to overwrite '/usr/lib/mysql/plugin/dialog.so' »', which is also in package mariadb-server-10.0 10.0.4+maria-1~wheezy
      Errors were encountered while processing:
       /var/cache/apt/archives/libmariadbclient18_10.0.5+maria-1~wheezy_amd64.deb
      E: Sub-process /usr/bin/dpkg returned an error code (1)
      

      Please tell me how I can fix it.

        Gliffy Diagrams

          Attachments

            Activity

            Hide
            elenst Elena Stepanova added a comment -

            Hi,

            Thanks for reporting this.
            Yes, unfortunately it so happens that the direct upgrade from alpha to beta currently does not work. Please run the following:

            sudo apt-get remove libmariadbclient18 libmysqlclient18 mariadb-client-10.0 mariadb-client-core-10.0 mariadb-server mariadb-server-10.0 mariadb-server-core-10.0
            sudo apt-get install mariadb-server

            It should fix the broken installation (and your data should remain intact, but as usual with any upgrade, the good practice is to make a backup before running it).

            Please let us know if it works for you.

            Thanks and sorry for the inconvenience.

            Show
            elenst Elena Stepanova added a comment - Hi, Thanks for reporting this. Yes, unfortunately it so happens that the direct upgrade from alpha to beta currently does not work. Please run the following: sudo apt-get remove libmariadbclient18 libmysqlclient18 mariadb-client-10.0 mariadb-client-core-10.0 mariadb-server mariadb-server-10.0 mariadb-server-core-10.0 sudo apt-get install mariadb-server It should fix the broken installation (and your data should remain intact, but as usual with any upgrade, the good practice is to make a backup before running it). Please let us know if it works for you. Thanks and sorry for the inconvenience.
            Hide
            Pfx2 Pierrick Dautrement added a comment -

            Thank you for your answer.

            Tonight, I'll do what you are advicing and I'll let you know if it works.

            Question : will it do the same problem when it will upgrade from 10.0.5 to the next betas? And from beta to final?

            Show
            Pfx2 Pierrick Dautrement added a comment - Thank you for your answer. Tonight, I'll do what you are advicing and I'll let you know if it works. Question : will it do the same problem when it will upgrade from 10.0.5 to the next betas? And from beta to final?
            Hide
            elenst Elena Stepanova added a comment -

            No, there should be no such problem in future. It's a bug that we are going to fix right away, actually it might happen that by the time you retry installation the fixed packages will already be available; but you will need to run the remove command anyway, as currently after the failed upgrade your MariaDB installation is in inconsistent state.

            Show
            elenst Elena Stepanova added a comment - No, there should be no such problem in future. It's a bug that we are going to fix right away, actually it might happen that by the time you retry installation the fixed packages will already be available; but you will need to run the remove command anyway, as currently after the failed upgrade your MariaDB installation is in inconsistent state.
            Hide
            Pfx2 Pierrick Dautrement added a comment -

            Elena, thank you, that did the trick. I also removed and reinstalled mysql-common and mariadb-common because they were still in 10.0.5, and I re-configured MariaDB. I didn't loose any data so that's cool.

            I noticed that 10.0.5 packages were removed from the mirror I used, so I think you can just close the ticket. I suppose that when the 10.0.5 packages will be added again, the bug will not happen again.

            By the way, great and fast support, thank you!

            Show
            Pfx2 Pierrick Dautrement added a comment - Elena, thank you, that did the trick. I also removed and reinstalled mysql-common and mariadb-common because they were still in 10.0.5, and I re-configured MariaDB. I didn't loose any data so that's cool. I noticed that 10.0.5 packages were removed from the mirror I used, so I think you can just close the ticket. I suppose that when the 10.0.5 packages will be added again, the bug will not happen again. By the way, great and fast support, thank you!
            Hide
            elenst Elena Stepanova added a comment -

            Right, deb packages are re-uploaded to the mirrors; maybe the mirror you are using is not up-to-date yet, but it will be soon. The new packages don't have the problem, upgrade 10.0.4 => 10.0.5 should work smoothly (I tried upgrade on Wheezy to confirm). Please let us know if you encounter further issues.

            Show
            elenst Elena Stepanova added a comment - Right, deb packages are re-uploaded to the mirrors; maybe the mirror you are using is not up-to-date yet, but it will be soon. The new packages don't have the problem, upgrade 10.0.4 => 10.0.5 should work smoothly (I tried upgrade on Wheezy to confirm). Please let us know if you encounter further issues.

              People

              • Assignee:
                Unassigned
                Reporter:
                Pfx2 Pierrick Dautrement
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: