Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-2667

maxscale RPMs not named consistently what content reports

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 2.3.11
    • 2.5.0
    • Packaging
    • None
    • centos.7

    Description

      The maxscale RPM is not named consistent with what is reported by the package. When attempting to install with entire named version, it cannot find it:

      yum install maxscale-2.3.11-1.centos.7.x86_64
      Loaded plugins: fastestmirror
      Loading mirror speeds from cached hostfile
      csf                                                               | 1.4 kB  00:00:00
      csf/prima{{monospaced text}}ry                                                       | 2.3 MB  00:00:05
      csf                                                                            6409/6409
      No package maxscale-2.3.11-1.centos.7.x86_64 available.
      Error: Nothing to do
      

      See how maxscale is reported vs galera and MariaDB, which is consistent:

      rpm -qp --queryformat="--> %{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n" maxscale-2.3.11-1.centos.7.x86_64.rpm
      --> maxscale-2.3.11-1.x86_64
       
      rpm -qp --queryformat="--> %{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n" galera-25.3.26-1.rhel7.el7.centos.x86_64.rpm
      --> galera-25.3.26-1.rhel7.el7.centos.x86_64
       
      rpm -qp --queryformat="--> %{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n" MariaDB-10.2.17-centos73-x86_64-client.rpm
      --> MariaDB-client-10.2.17-1.el7.centos.x86_64
      

      Attachments

        Activity

          People

            markus makela markus makela
            rvlane Richard Lane
            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.