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

Ubuntu Bionic MariaDB has epoch version that makes 10.1 and 10.2 installs fail

Details

    Description

      The epoch version appears in the version string before the real version number and apt considers it higher than any version number without an epoch version, which means that the current MariaDB version 1:10.1.29-6 in the Ubuntu Bionic repo is considered higher than MariaDB 10.2.14 from the MariaDB repo (or the 10.2.15 packages in buildbot). So apt always chooses it.

      This has already been fixed in 10.3 by otto in this commit.

      From the commit message:

      A non-MariaDB.org contributor introduced the epoch 1: in Debian.
      		 
      There is no way to revert it, so we just need to adapt to it to
      		 
      ensure no 10.3 installation would downgrade to that version in
      		 
      Debian/Ubuntu, as 1: is considered higher than any version before.

      This fix should be backported to 10.1 and 10.2 so that installs of those versions of MariaDB from the MariaDB repositories will work on Ubuntu Bionic and future versions of Debian and Ubuntu.

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          dbart Daniel Bartholomew created issue -
          dbart Daniel Bartholomew made changes -
          Field Original Value New Value
          Description The epoch version appears in the version string before the _real_ version number and apt considers it higher than any version number without an epoch version, which means that the current 10.1.29 in the Ubuntu Bionic repo is considered higher than 10.2.15 from the MariaDB repo. So apt always chooses it above ours.

          This has already been fixed in 10.3 by [~otto] in [this commit|https://github.com/MariaDB/server/commit/ec53e031bb364b3a6eea2308fa31a542c903dc7e].

          From the commit message:
          bq. A non-MariaDB.org contributor introduced the epoch 1: in Debian.
          bq. There is no way to revert it, so we just need to adapt to it to
          bq. ensure no 10.3 installation would downgrade to that version in
          bq. Debian/Ubuntu, as 1: is considered higher than any version before.

          This fix should be backported to 10.1 and 10.2 so that installs of those versions of MariaDB from the MariaDB repositories will work on Ubuntu Bionic and future versions of Debian and Ubuntu.
          		The epoch version appears in the version string before the _real_ version number and apt considers it higher than any version number without an epoch version, which means that the current MariaDB version *1:10.1.29-6* in the Ubuntu Bionic repo is considered higher than MariaDB *10.2.15* from the MariaDB repo. So apt always chooses it above ours.

          This has already been fixed in 10.3 by [~otto] in [this commit|https://github.com/MariaDB/server/commit/ec53e031bb364b3a6eea2308fa31a542c903dc7e].

          From the commit message:
          bq. A non-MariaDB.org contributor introduced the epoch 1: in Debian.
          bq. There is no way to revert it, so we just need to adapt to it to
          bq. ensure no 10.3 installation would downgrade to that version in
          bq. Debian/Ubuntu, as 1: is considered higher than any version before.

          This fix should be backported to 10.1 and 10.2 so that installs of those versions of MariaDB from the MariaDB repositories will work on Ubuntu Bionic and future versions of Debian and Ubuntu.
          dbart Daniel Bartholomew made changes -
          Description The epoch version appears in the version string before the _real_ version number and apt considers it higher than any version number without an epoch version, which means that the current MariaDB version *1:10.1.29-6* in the Ubuntu Bionic repo is considered higher than MariaDB *10.2.15* from the MariaDB repo. So apt always chooses it above ours.

          This has already been fixed in 10.3 by [~otto] in [this commit|https://github.com/MariaDB/server/commit/ec53e031bb364b3a6eea2308fa31a542c903dc7e].

          From the commit message:
          bq. A non-MariaDB.org contributor introduced the epoch 1: in Debian.
          bq. There is no way to revert it, so we just need to adapt to it to
          bq. ensure no 10.3 installation would downgrade to that version in
          bq. Debian/Ubuntu, as 1: is considered higher than any version before.

          This fix should be backported to 10.1 and 10.2 so that installs of those versions of MariaDB from the MariaDB repositories will work on Ubuntu Bionic and future versions of Debian and Ubuntu.
          		The epoch version appears in the version string before the _real_ version number and apt considers it higher than any version number without an epoch version, which means that the current MariaDB version *1:10.1.29-6* in the Ubuntu Bionic repo is considered higher than MariaDB *10.2.14* from the MariaDB repo (or the 10.2.15 packages in buildbot). So apt always chooses it.

          This has already been fixed in 10.3 by [~otto] in [this commit|https://github.com/MariaDB/server/commit/ec53e031bb364b3a6eea2308fa31a542c903dc7e].

          From the commit message:
          bq. A non-MariaDB.org contributor introduced the epoch 1: in Debian.
          bq. There is no way to revert it, so we just need to adapt to it to
          bq. ensure no 10.3 installation would downgrade to that version in
          bq. Debian/Ubuntu, as 1: is considered higher than any version before.

          This fix should be backported to 10.1 and 10.2 so that installs of those versions of MariaDB from the MariaDB repositories will work on Ubuntu Bionic and future versions of Debian and Ubuntu.
          dbart Daniel Bartholomew made changes -
          Description The epoch version appears in the version string before the _real_ version number and apt considers it higher than any version number without an epoch version, which means that the current MariaDB version *1:10.1.29-6* in the Ubuntu Bionic repo is considered higher than MariaDB *10.2.14* from the MariaDB repo (or the 10.2.15 packages in buildbot). So apt always chooses it.

          This has already been fixed in 10.3 by [~otto] in [this commit|https://github.com/MariaDB/server/commit/ec53e031bb364b3a6eea2308fa31a542c903dc7e].

          From the commit message:
          bq. A non-MariaDB.org contributor introduced the epoch 1: in Debian.
          bq. There is no way to revert it, so we just need to adapt to it to
          bq. ensure no 10.3 installation would downgrade to that version in
          bq. Debian/Ubuntu, as 1: is considered higher than any version before.

          This fix should be backported to 10.1 and 10.2 so that installs of those versions of MariaDB from the MariaDB repositories will work on Ubuntu Bionic and future versions of Debian and Ubuntu.
          		The epoch version appears in the version string before the _real_ version number and apt considers it higher than any version number without an epoch version, which means that the current MariaDB version *1:10.1.29-6* in the Ubuntu Bionic repo is considered higher than MariaDB *10.2.14* from the MariaDB repo (or the 10.2.15 packages in buildbot). So apt always chooses it.

          This has already been fixed in 10.3 by [~otto] in [this commit|https://github.com/MariaDB/server/commit/ec53e031bb364b3a6eea2308fa31a542c903dc7e].

          From the commit message:

          {code}
          A non-MariaDB.org contributor introduced the epoch 1: in Debian.
          There is no way to revert it, so we just need to adapt to it to
          ensure no 10.3 installation would downgrade to that version in
          Debian/Ubuntu, as 1: is considered higher than any version before.
          {code}


          This fix should be backported to 10.1 and 10.2 so that installs of those versions of MariaDB from the MariaDB repositories will work on Ubuntu Bionic and future versions of Debian and Ubuntu.
          serg Sergei Golubchik made changes -
          Component/s Packaging [ 10700 ]
          Component/s Platform Debian [ 10136 ]
          Fix Version/s 10.2.15 [ 23006 ]
          Fix Version/s 10.3.7 [ 23005 ]
          Assignee Sergei Golubchik [ serg ]
          Resolution Fixed [ 1 ]
          Status Open [ 1 ] Closed [ 6 ]
          dbart Daniel Bartholomew made changes -
          Resolution Fixed [ 1 ]
          Status Closed [ 6 ] Stalled [ 10000 ]
          serg Sergei Golubchik made changes -
          Fix Version/s 10.1.34 [ 23100 ]
          Resolution Fixed [ 1 ]
          Status Stalled [ 10000 ] Closed [ 6 ]
          serg Sergei Golubchik made changes -
          Workflow MariaDB v3 [ 87271 ] MariaDB v4 [ 154370 ]

          People

            serg Sergei Golubchik
            dbart Daniel Bartholomew
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.