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

RPM packages of MariaDB-Galera are not available in yum repositories after a new version of the main server gets released

Details

    Description

      Our repository configuration tool provides a generic link for both MariaDB server and MariaDB-Galera, e.g. http://yum.mariadb.org/5.5/centos5-amd64

      Main server and Galera server are not released in sync, so, as soon as the main server is released, the link starts pointing at the new version, which does not contain MariaDB-Galera-server, and yum install can't find Galera server anymore.

      We need either to have different repositories for server and Galera-server (which in turn might cause problems), or be careful placing the last released version of Galera-server, whichever it is, with the last version of the main server.

      Attachments

        Activity

          elenst Elena Stepanova added a comment - - edited

          Workaround for the time being: for Galera, use
          http://yum.mariadb.org/5.5.28a/centos5-amd64 and such
          instead of
          http://yum.mariadb.org/5.5/centos5-amd64

          then switch to the normal repo and upgrade other components if needed.

          elenst Elena Stepanova added a comment - - edited Workaround for the time being: for Galera, use http://yum.mariadb.org/5.5.28a/centos5-amd64 and such instead of http://yum.mariadb.org/5.5/centos5-amd64 then switch to the normal repo and upgrade other components if needed.

          issue is fixed

          dbart Daniel Bartholomew added a comment - issue is fixed

          People

            dbart Daniel Bartholomew
            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.