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

Upgrade from 10.0 to 10.1 on Vivid does not work with normal source list

Details

    • 10.1.10

    Description

      It's MDEV-5977 all over again, only the next generation of it – new Ubuntu, new MariaDB.

      If MariaDB 10.0 is installed, even from MariaDB's own packages, and either vivid-security universe or vivid-updates universe are in the sources.list (which has both normally), installation of 10.1 mariadb-server fails in the same way as it did in MDEV-5977:

      • mariadb-server fails to install pointing at mariadb-server-10.1;
      • mariadb-server-10.1 fails to install pointing at mariadb-server-core-10.1;
      • mariadb-server-core-10.1, if requested explicitly, installs all right and pulls other packages.

      That's the reason of Buildbot's upgrade2 failures on Vivid:
      http://buildbot.askmonty.org/buildbot/builders/kvm-deb-vivid-amd64/builds/201/steps/test_2/logs/stdio

      So, there are two workarounds for the problem:

      • disable vivid-security universe and vivid-updates universe to upgrade MariaDB;
      • specify mariadb-server-core-10.1 on apt-get install command line.

      None of these is good enough when 10.1 goes GA.

      Attachments

        Issue Links

          blocks

          Task - A task that needs to be done. MDEV-7069 Fix buildbot failures in main server trees

          • Major - Major loss of function.
          • Closed
          is blocked by

          Task - A task that needs to be done. MDEV-6284 Merge downstream Debian/Ubuntu packaging into upstream MariaDB

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            elenst Elena Stepanova added a comment -

            It's possible there is also the 3rd workaround, having 10.0 repo in the source list along with 10.1 (I believe on whatever reason it worked in my experiments), but it will need to be confirmed if we don't have a real solution for the problem. I still hope that we will.

            elenst Elena Stepanova added a comment - It's possible there is also the 3rd workaround, having 10.0 repo in the source list along with 10.1 (I believe on whatever reason it worked in my experiments), but it will need to be confirmed if we don't have a real solution for the problem. I still hope that we will.
            otto Otto Kekäläinen added a comment -

            For the record, I solved these issues a few days ago in my repo https://github.com/ottok/mariadb/tree/ok-debpkg-10.1 but I cannot open a pull request as the buildbot column is not all green yet. due to test failures that most likely are inherited from failing master 10.1 branch, though I am not sure.

            otto Otto Kekäläinen added a comment - For the record, I solved these issues a few days ago in my repo https://github.com/ottok/mariadb/tree/ok-debpkg-10.1 but I cannot open a pull request as the buildbot column is not all green yet. due to test failures that most likely are inherited from failing master 10.1 branch, though I am not sure.
            serg Sergei Golubchik added a comment -

            Hmm, couldn't repeat this manually in a vivid upgrade2 VM.

            serg Sergei Golubchik added a comment - Hmm, couldn't repeat this manually in a vivid upgrade2 VM.
            otto Otto Kekäläinen added a comment -

            I believe this was fixed in https://github.com/MariaDB/server/pull/97 and backported to 10.0 too in https://github.com/MariaDB/server/pull/124

            otto Otto Kekäläinen added a comment - I believe this was fixed in https://github.com/MariaDB/server/pull/97 and backported to 10.0 too in https://github.com/MariaDB/server/pull/124

            People

              serg Sergei Golubchik
              elenst Elena Stepanova
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.