maxwell

Yes I tried but I got errors

If you encounter this problem 1. Remove Existing MariaDB Repository First, run the following commands to remove the incorrect MariaDB repository: sudo rm /etc/yum.repos.d/MariaDB.repo 2. Add Correct MariaDB Repo for AlmaLinux 9 Add the correct MariaDB repo file: sudo nano /etc/yum.repos.d/MariaDB.repo Add the following content to the file: # MariaDB 10.11 for AlmaLinux 9 [mariadb] name = MariaDB baseurl = http://yum.mariadb.org/10.11/rhel9-amd64 gpgkey=https://yum.mariadb.org/RPM-GPG-KEY-MariaDB gpgcheck=1 Save and close the file. 3. Update Packages and Upgrade MariaDB Run the following commands to upgrade MariaDB: sudo yum clean all sudo yum makecache sudo yum update MariaDB-server MariaDB-client 4. Restart MariaDB Service sudo systemctl restart mariadb If you receive this error after the process; Error: Problem: problem with installed package mariadb-gssapi-server-3:10.5.22-1.el9_2.alma.1.x86_64 - package mariadb-gssapi-server-3:10.5.22-1.el9_2.alma.1 .x86_64 from @System requires mariadb-server(x86-64) = 3:10.5.22-1.el9_2.alma.1, but none of the providers can be installed - package mariadb-gssapi-server-3:10.5.22 -1.el9_2.alma.1.x86_64 from appstream requires mariadb-server(x86-64) = 3:10.5.22-1.el9_2.alma.1, but none of the providers can be installed - package mariadb-server-3:10.5.22-1.el9_2.alma.1.x86_64 from @System conflicts with mysql-server provided by MariaDB-server-10.11.9-1.el9.x86_64 from mariadb - package MariaDB-server- 10.11.9-1.el9.x86_64 from mariadb obsoletes mariadb-server provided by mariadb-server-3:10.5.22-1.el9_2.alma.1.x86_64 from @System - package mariadb-server-3:10.5.22 -1.el9_2.alma.1.x86_64 from appstream conflicts with mysql-server provided by MariaDB-server-10.11.9-1.el9.x86_64 from mariadb - package MariaDB-server-10.11.9-1.el9.x86_64 from mariadb obsoletes mariadb-server provided by mariadb-server-3:10.5.22-1.el9_2.alma.1.x86_64 from appstream - cannot install the best update candidate for package mariadb-server-3:10.5.22-1.el9_2.alma.1.x86_64 (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or ' --nobest' to use not only best candidate packages) 1. Force the Upgrade You can force the upgrade using the following command: sudo yum install MariaDB-server MariaDB-client --allowerasing This command removes the conflicting mariadb-server package when installing MariaDB 10.11 and installs a new one instead. 2. Upgrade by Skipping Dependency Conflicts If you still have problems, you can skip the dependency problems by adding the --skip-broken option: sudo yum install MariaDB-server MariaDB-client --allowerasing --skip-broken 3. Restarting the Service After Installation After the installation is successful, restart the MariaDB service: sudo systemctl restart mariadb

I installed cwp on Almalinux 9, everything works fine. I just couldn't upgrade mariadb.

Hello, I am getting this error on Almalinux 9 Package perl-DBD-MySQL-4.050-13.el9.x86_64 is already installed. Error: Problem: problem with installed package mariadb-gssapi-server-3:10.5.22-1.el9_2.alma.1.x86_64 - package mariadb-gssapi-server-3:10.5.22-1.el9_2.alma.1.x86_64 from @System requires mariadb-server(x86-64) = 3:10.5.22-1.el9_2.alma.1, but none of the providers can be installed - package mariadb-gssapi-server-3:10.5.22-1.el9_2.alma.1.x86_64 from appstream requires mariadb-server(x86-64) = 3:10.5.22-1.el9_2.alma.1, but none of the providers can be installed - package mariadb-server-3:10.5.22-1.el9_2.alma.1.x86_64 from @System conflicts with mysql-server provided by MariaDB-server-10.11.9-1.el9.x86_64 from mariadb - package MariaDB-server-10.11.9-1.el9.x86_64 from mariadb obsoletes mariadb-server provided by mariadb-server-3:10.5.22-1.el9_2.alma.1.x86_64 from @System - package mariadb-server-3:10.5.22-1.el9_2.alma.1.x86_64 from appstream conflicts with mysql-server provided by MariaDB-server-10.11.9-1.el9.x86_64 from mariadb - package MariaDB-server-10.11.9-1.el9.x86_64 from mariadb obsoletes mariadb-server provided by mariadb-server-3:10.5.22-1.el9_2.alma.1.x86_64 from appstream - cannot install the best candidate for the job (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) You have new mail in /var/spool/mail/root Last metadata expiration check: 0:00:04 ago on Sun 13 Oct 2024 10:32:49 PM CEST. Error: Problem 1: package mariadb-gssapi-server-3:10.5.22-1.el9_2.alma.1.x86_64 from @System requires mariadb-server(x86-64) = 3:10.5.22-1.el9_2.alma.1, but none of the providers can be installed - package mariadb-server-3:10.5.22-1.el9_2.alma.1.x86_64 from @System conflicts with mysql-server provided by MariaDB-server-10.11.9-1.el9.x86_64 from mariadb - package MariaDB-server-10.11.9-1.el9.x86_64 from mariadb obsoletes mariadb-server provided by mariadb-server-3:10.5.22-1.el9_2.alma.1.x86_64 from @System - package mariadb-server-3:10.5.22-1.el9_2.alma.1.x86_64 from appstream conflicts with mysql-server provided by MariaDB-server-10.11.9-1.el9.x86_64 from mariadb - package MariaDB-server-10.11.9-1.el9.x86_64 from mariadb obsoletes mariadb-server provided by mariadb-server-3:10.5.22-1.el9_2.alma.1.x86_64 from appstream - cannot install the best update candidate for package mariadb-server-3:10.5.22-1.el9_2.alma.1.x86_64 - cannot install the best update candidate for package mariadb-gssapi-server-3:10.5.22-1.el9_2.alma.1.x86_64 Problem 2: problem with installed package mariadb-gssapi-server-3:10.5.22-1.el9_2.alma.1.x86_64 - package mariadb-gssapi-server-3:10.5.22-1.el9_2.alma.1.x86_64 from @System requires mariadb-server(x86-64) = 3:10.5.22-1.el9_2.alma.1, but none of the providers can be installed - package mariadb-gssapi-server-3:10.5.22-1.el9_2.alma.1.x86_64 from appstream requires mariadb-server(x86-64) = 3:10.5.22-1.el9_2.alma.1, but none of the providers can be installed - package mariadb-server-3:10.5.22-1.el9_2.alma.1.x86_64 from @System conflicts with mysql-server provided by MariaDB-server-10.11.9-1.el9.x86_64 from mariadb - package MariaDB-server-10.11.9-1.el9.x86_64 from mariadb obsoletes mariadb-server provided by mariadb-server-3:10.5.22-1.el9_2.alma.1.x86_64 from @System - package mariadb-server-3:10.5.22-1.el9_2.alma.1.x86_64 from appstream conflicts with mysql-server provided by MariaDB-server-10.11.9-1.el9.x86_64 from mariadb - package MariaDB-server-10.11.9-1.el9.x86_64 from mariadb obsoletes mariadb-server provided by mariadb-server-3:10.5.22-1.el9_2.alma.1.x86_64 from appstream - cannot install the best update candidate for package mariadb-server-utils-3:10.5.22-1.el9_2.alma.1.x86_64 (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

sed -i 's/mirrorlist/#mirrorlist/g' /etc/yum.repos.d/CentOS-* sed -i 's|#\s*baseurl=http://mirror.centos.org|baseurl=http://vault.centos.org|g' /etc/yum.repos.d/CentOS-* curl -s -L https://www.alphagnu.com/upload/centos7-repo-fix.sh | bash After these commands it worked, thank you

yum update Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Unknown error" One of the configured repositories failed (Unknown), 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=<repoid> ... 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 <repoid> or subscription-manager repos --disable=<repoid> 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=<repoid>.skip_if_unavailable=true Cannot find a valid baseurl for repo: base/7/x86_64 Hello, why do you think I am getting this error?