@A,

That sounds frustrating! It seems like a dependency issue with the MariaDB version and the connector. Have you tried rebuilding the RPM database using 'rpm --rebuilddb' or checking if there’s a specific version of MariaDB that matches the required dependencies? Sometimes clearing the cache with 'dnf clean packages' can help too.

Let me know if you need any further assistance!

Running transaction check  
Error: transaction check vs depsolve:  
(mariadb >= 3:10.3.27 if mariadb) is needed by mariadb-connector-c-3.1.11-2.el8_3.x86_64  
(mariadb-connector-c-config = 3.1.11-2.el8_3 if mariadb-connector-c-config) is needed by mariadb-connector-c-3.1.11-2.el8_3.x86_64  
rpmlib(RichDependencies) <= 4.12.0-1 is needed by mariadb-connector-c-3.1.11-2.el8_3.x86_64  

To diagnose the problem, try running: 'rpm -Va --nofiles --nodigest'.  
You probably have a corrupted RPMDB, and running 'rpm --rebuilddb' might fix the issue.  
The downloaded packages were saved in cache until the next successful transaction.  
You can remove cached packages by executing 'dnf clean packages'.  

I lost 2 hours and couldn’t find a way to install the desired MariaDB version as there’s a loop break with the desired mariadb-connector-c-3.1.11-2.el8_3.x86_64, and it simply does not work.

@Thuy,

You have libssh2-1.8.0-4.el7_9.1.aarch64 installed, which belongs to CentOS Linux 7 repository, which isn’t compatible with your CentOS 8 system.

Updating it to the latest libssh2 version might fix the issue.

sudo sudo dnf update
sudo dnf update libssh2

I got this issue when trying to sync the package with Centos 8.

# dnf --releasever=8 --setopt=deltarpm=false --setopt=protected_packages=  distro-sync -y

CentOS Linux 8 - BaseOS
CentOS Linux 8 - AppStream
Failed to synchronize cache for repo 'baseos', ignoring this repo.
Failed to synchronize cache for repo 'appstream', ignoring this repo.
Last metadata expiration check: 1:02:50 ago on Mon 04 Mar 2024 12:31:47 AM EST.
Error: 
 Problem: problem with installed package libssh2-1.8.0-4.el7_9.1.aarch64
  - libssh2-1.8.0-4.el7_9.1.aarch64 does not belong to a distupgrade repository
  - nothing provides libcrypto.so.1.1()(64bit) needed by libssh2-1.10.0-1.el8.aarch64
  - nothing provides libcrypto.so.1.1(OPENSSL_1_1_0)(64bit) needed by libssh2-1.10.0-1.el8.aarch64
  - nothing provides libssl.so.1.1()(64bit) needed by libssh2-1.10.0-1.el8.aarch64
  - nothing provides libcrypto.so.1.1(OPENSSL_1_1_1)(64bit) needed by libssh2-1.10.0-1.el8.aarch64

# dnf distro-sync

CentOS Linux 8 - BaseOS            
CentOS Linux 8 - AppStream         
Failed to synchronize cache for repo 'baseos', ignoring this repo.
Failed to synchronize cache for repo 'appstream', ignoring this repo.
Last metadata expiration check: 1:06:38 ago on Mon 04 Mar 2024 12:31:47 AM EST.
Error: 
 Problem: problem with installed package libssh2-1.8.0-4.el7_9.1.aarch64
  - libssh2-1.8.0-4.el7_9.1.aarch64 does not belong to a distupgrade repository
  - nothing provides libcrypto.so.1.1()(64bit) needed by libssh2-1.10.0-1.el8.aarch64
  - nothing provides libcrypto.so.1.1(OPENSSL_1_1_0)(64bit) needed by libssh2-1.10.0-1.el8.aarch64
  - nothing provides libssl.so.1.1()(64bit) needed by libssh2-1.10.0-1.el8.aarch64
  - nothing provides libcrypto.so.1.1(OPENSSL_1_1_1)(64bit) needed by libssh2-1.10.0-1.el8.aarch64

And when I tried to remove the package libssh2, this is what I got:

# dnf remove libssh2

Error: 
 Problem: The operation would result in removing the following protected packages: systemd

Is there any ideas to fix this?

@Martin,

It seems like you’re encountering an issue with the DNF package manager on CentOS 8, to fix this issue you can try the following steps:

1. Update the DNF package to the latest version available in the repository.

sudo dnf update dnf

2. After updating DNF, try running the system update again.

sudo dnf --releasever=8 --allowerasing --setopt=deltarpm=false distro-sync

If the issue persists, you may try reinstalling the ‘dnf’ package:

sudo dnf reinstall dnf

If the problem is related to dependencies, you may need to address those dependencies before attempting the update.