[MXS-2667] maxscale RPMs not named consistently what content reports Created: 2019-09-06  Updated: 2019-10-18  Resolved: 2019-10-18

Status: Closed
Project: MariaDB MaxScale
Component/s: Packaging
Affects Version/s: 2.3.11
Fix Version/s: 2.5.0

Type: Bug Priority: Major
Reporter: Richard Lane Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None
Environment:

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



 Comments   
Comment by markus makela [ 2019-10-16 ]

With the fix the output looks like this:

rpm -qp --queryformat="--> %{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n" maxscale-2.5.0-1.centos.7.x86_64.rpm
 
--> maxscale-2.5.0-1.centos.7.x86_64

Generated at Thu Feb 08 04:15:49 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.