[MDEV-30607] CentOS 6 MariaDB 10.3 archive repo broke recently Created: 2023-02-07 Updated: 2023-06-05 Resolved: 2023-03-01 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Repositories |
| Affects Version/s: | None |
| Fix Version/s: | 10.3.38 |
| Type: | Bug | Priority: | Major |
| Reporter: | Hans Borresen | Assignee: | Daniel Bartholomew |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | 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/ Anyone running a CentOS 6 or similar OS (like CloudLinux 6) who attempts to install from the archive will run into the following error:
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? |
| Comments |
| Comment by Daniel Bartholomew [ 2023-02-07 ] |
|
Confirmed. Working on getting these deprecated repositories fixed ASAP. |
| Comment by Daniel Bartholomew [ 2023-02-07 ] |
|
I think I've got the 10.3 repositories restored and working for RHEL 6 and the old Fedora releases we had 10.3 packages for. Now looking into other possibly affected repositories (e.g. 10.4 and etc...). |
| Comment by Daniel Bartholomew [ 2023-02-09 ] |
|
Other legacy repositories for deprecated platforms have been fixed, mainly old Fedoras. I'll now look into what needs to be done to fix the signing issue that caused the problems. The core issue is with the part of the release process where packages get signed, the glob to gather up the packages is simply too broad and is matching rpms that don't need to be signed. It needs to be restricted to just signing new packages. |
| Comment by Quark [ 2023-05-26 ] |
|
Same thing with 10.4 btw. |
| Comment by Weydson Lima [ 2023-06-01 ] |
|
I see this issue marked as closed, but I just faced this exact issue when trying to rebuild an AMI image on AWS - it's failing when installing MariaDB and preventing the AMI image to be created. |
| Comment by Hans Borresen [ 2023-06-05 ] |
|
I've gone ahead and opened a new issue for the re-occurrence – I think it's unlikely this will happen again – it was the very last update to 10.3 before it went EOL that seems to have caused the problem. |