Details

    Description

      1:10.4.1+maria~sid seems to be the latest version available

      Attachments

        Activity

          > on Sid

          Note this applies to Buster too.

          > You'll be fighting with Apt to not auto-upgrade your packages to the 10.3 packages in the Sid repositories.

          Not really, as the version is part of the package name. apt install mariadb-server-10.1 should work just fine, even if a mariadb-server-10.3 is available too.

          XTF Olaf van der Spek added a comment - > on Sid Note this applies to Buster too. > You'll be fighting with Apt to not auto-upgrade your packages to the 10.3 packages in the Sid repositories. Not really, as the version is part of the package name. apt install mariadb-server-10.1 should work just fine, even if a mariadb-server-10.3 is available too.

          You are correct that if you restrict yourself to just installing the mariadb-server-10.1 package (and other mariadb-*-10.1 packages) then things could work. I was specifically thinking of the mariadb-server metapackage which always depends on the latest version.

          However, for all versions of Debian and Ubuntu our policy is to not build for MariaDB versions that are lower than what can be found in the distribution repositories. And since both Buster and Sid now include MariaDB 10.3 in their repositories, that is the lowest version we will be building for them.

          dbart Daniel Bartholomew added a comment - You are correct that if you restrict yourself to just installing the mariadb-server-10.1 package (and other mariadb-*-10.1 packages) then things could work. I was specifically thinking of the mariadb-server metapackage which always depends on the latest version. However, for all versions of Debian and Ubuntu our policy is to not build for MariaDB versions that are lower than what can be found in the distribution repositories. And since both Buster and Sid now include MariaDB 10.3 in their repositories, that is the lowest version we will be building for them.

          > I was specifically thinking of the mariadb-server metapackage which always depends on the latest version.

          That'd affect 10.3 or 10.4 as well, depending on what's considered latest.

          > our policy is

          Fair enough, though it'd be interesting to understand the rationale for that policy.

          > to not build for MariaDB versions that are lower than what can be found in the distribution repositories.

          Does it make sense to build the same versions? As they should be already available..

          XTF Olaf van der Spek added a comment - > I was specifically thinking of the mariadb-server metapackage which always depends on the latest version. That'd affect 10.3 or 10.4 as well, depending on what's considered latest. > our policy is Fair enough, though it'd be interesting to understand the rationale for that policy. > to not build for MariaDB versions that are lower than what can be found in the distribution repositories. Does it make sense to build the same versions? As they should be already available..

          I've managed to fix the Sid builders and I've built packages for both 10.3.13 and 10.4.3. It'll take a little bit for the packages to propagate out to all of the mirrors. But I consider this task basically complete otherwise.

          dbart Daniel Bartholomew added a comment - I've managed to fix the Sid builders and I've built packages for both 10.3.13 and 10.4.3. It'll take a little bit for the packages to propagate out to all of the mirrors. But I consider this task basically complete otherwise.

          To answer your most recent questions:

          > That'd affect 10.3 or 10.4 as well, depending on what's considered latest.
          Yes.

          > it'd be interesting to understand the rationale for that policy

          It basically boils down to wanting to support as many configurations as we can with finite resources. We can't support building on everything so, we do what makes the most sense. If a distro has chosen to move to only offering 10.3, we take that as a reasonable baseline, and we'll do 10.3+ there.

          > Does it make sense to build the same versions? As they should be already available..

          It makes perfect sense. We work with distributions to fix bugs. It'd be hard to do that if we weren't building and testing what they are shipping/supporting.

          dbart Daniel Bartholomew added a comment - To answer your most recent questions: > That'd affect 10.3 or 10.4 as well, depending on what's considered latest. Yes. > it'd be interesting to understand the rationale for that policy It basically boils down to wanting to support as many configurations as we can with finite resources. We can't support building on everything so, we do what makes the most sense. If a distro has chosen to move to only offering 10.3, we take that as a reasonable baseline, and we'll do 10.3+ there. > Does it make sense to build the same versions? As they should be already available.. It makes perfect sense. We work with distributions to fix bugs. It'd be hard to do that if we weren't building and testing what they are shipping/supporting.

          People

            dbart Daniel Bartholomew
            XTF Olaf van der Spek
            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.