Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
None
Description
I know this is an "EOL" operating system, but there are some people still using the package (some pay their OS vendor for extended support)
At https://archive.mariadb.org/mariadb-10.3/yum/centos/6/x86_64/
You guys published new RPMs recently, but the repodata does not match.
Anyone running a CentOS 6 or similar OS (like CloudLinux 6) who attempts to install from the archive will run into the following error:
[root@cloud ~]# yum install MariaDB-server
|
...
|
Resolving Dependencies
|
--> Running transaction check
|
---> Package MariaDB-server.x86_64 0:10.3.27-1.el6 will be installed
|
--> Processing Dependency: galera for package: MariaDB-server-10.3.27-1.el6.x86_64
|
--> Processing Dependency: MariaDB-common for package: MariaDB-server-10.3.27-1.el6.x86_64
|
--> Processing Dependency: MariaDB-client for package: MariaDB-server-10.3.27-1.el6.x86_64
|
--> Running transaction check
|
---> Package MariaDB-client.x86_64 0:10.3.27-1.el6 will be installed
|
---> Package MariaDB-common.x86_64 0:10.3.27-1.el6 will be installed
|
--> Processing Dependency: MariaDB-compat for package: MariaDB-common-10.3.27-1.el6.x86_64
|
---> Package galera.x86_64 0:25.3.29-1.rhel6.el6 will be installed
|
--> Running transaction check
|
---> Package MariaDB-compat.x86_64 0:10.3.27-1.el6 will be installed
|
--> Finished Dependency Resolution
|
|
|
Dependencies Resolved
|
|
|
==========================================================================================================================================================================================================
|
Package Arch Version Repository Size
|
==========================================================================================================================================================================================================
|
Installing:
|
MariaDB-server x86_64 10.3.27-1.el6 MariaDB103 136 M
|
Installing for dependencies:
|
MariaDB-client x86_64 10.3.27-1.el6 MariaDB103 59 M
|
MariaDB-common x86_64 10.3.27-1.el6 MariaDB103 176 k
|
MariaDB-compat x86_64 10.3.27-1.el6 MariaDB103 4.0 M
|
galera x86_64 25.3.29-1.rhel6.el6 MariaDB103 9.2 M
|
|
|
Transaction Summary
|
==========================================================================================================================================================================================================
|
Install 5 Package(s)
|
|
|
Total download size: 209 M
|
Installed size: 209 M
|
Is this ok [y/N]: y
|
Downloading Packages:
|
(1/5): MariaDB-client-10.3.27-1.el6.x86_64.rpm | 59 MB 00:04
|
https://archive.mariadb.org/mariadb-10.3/yum/centos/6/x86_64/rpms/MariaDB-client-10.3.27-1.el6.x86_64.rpm: [Errno -1] Package does not match intended download. Suggestion: run yum --enablerepo=MariaDB103 clean metadata
|
Trying other mirror.
|
(2/5): MariaDB-common-10.3.27-1.el6.x86_64.rpm | 177 kB 00:00
|
https://archive.mariadb.org/mariadb-10.3/yum/centos/6/x86_64/rpms/MariaDB-common-10.3.27-1.el6.x86_64.rpm: [Errno -1] Package does not match intended download. Suggestion: run yum --enablerepo=MariaDB103 clean metadata
|
...
|
Error Downloading Packages:
|
MariaDB-client-10.3.27-1.el6.x86_64: failure: rpms/MariaDB-client-10.3.27-1.el6.x86_64.rpm from MariaDB103: [Errno 256] No more mirrors to try.
|
galera-25.3.29-1.rhel6.el6.x86_64: failure: rpms/galera-25.3.29-1.rhel6.el6.x86_64.rpm from MariaDB103: [Errno 256] No more mirrors to try.
|
MariaDB-common-10.3.27-1.el6.x86_64: failure: rpms/MariaDB-common-10.3.27-1.el6.x86_64.rpm from MariaDB103: [Errno 256] No more mirrors to try.
|
MariaDB-compat-10.3.27-1.el6.x86_64: failure: rpms/MariaDB-compat-10.3.27-1.el6.x86_64.rpm from MariaDB103: [Errno 256] No more mirrors to try.
|
MariaDB-server-10.3.27-1.el6.x86_64: failure: rpms/MariaDB-server-10.3.27-1.el6.x86_64.rpm from MariaDB103: [Errno 256] No more mirrors to try.
|
Running "yum --enablerepo=MariaDB103 clean metadata" does not resolve it, since the metadata actually on the archive server is out of date. The RPMs are from 2023, but the repo metadata is from 2021.
Would it be possible to update the metadata to match the new packages?