我知道，似乎有一个问题，围绕MariaDB回购的最近时间，它一直返回一个404未找到错误，在升级阶段的迁移从MySQL到MariaDB。
我一直在寻找不同的解决办法，虽然，我坚持与一些问题，我想知道是否有人可以建议？
我尝试在/etc/yum.repos.d/中更新我的repo配置文件中的baseurl路径-然而，在保存我在root用户级别所做的更改后，在从WHM运行“升级MySQL/MariaDB数据库”选项后，原始的baseurl会自动替换。
我已经尝试通过使用相关的yum --add-repo命令添加额外的存储库，成功添加并启用了MariaDB 10.6存储库。但是，当我尝试从WHM重新运行升级时，升级过程继续搜索10.2版本，并尝试从原始的baseurl下载MariaDB（它继续默认返回到损坏的存储库url）
我只是想知道，是否有人可以与我分享任何指针，就如何让升级过程中，以认识到第二回购我添加了10.6（与工作镜像网址），而不是升级过程中自动识别破碎的MariaDB 10.2回购。
"只是一个简短的侧记"
我已经尝试禁用10.2的默认存储库，但是，在运行升级过程后，10.2软件包再次自动重新启用。
控制台日志的输出：

Restarting mysql service.
(XID ehvnfq) The “mysql” service is disabled.
The system was not able to ensure the availability of the “MariaDB-client” package: (XID httqu8) “/usr/bin/yum” reported error code “1” when it ended: https://yum.mariadb.org/10.2/centos7-amd64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.

One of the configured repositories failed (MariaDB102),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:

1. Contact the upstream for the repository and get them to fix the problem.

2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).

3. Run the command with the repository temporarily disabled
yum --disablerepo=MariaDB102 ...

4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:

yum-config-manager --disable MariaDB102
or
subscription-manager repos --disable=MariaDB102

5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:

yum-config-manager --save --setopt=MariaDB102.skip_if_unavailable=true

failure: repodata/repomd.xml from MariaDB102: [Errno 256] No more mirrors to try.
https://yum.mariadb.org/10.2/centos7-amd64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found

非常感谢！：-）