Last metadata expiration check: 0:01:27 ago on Tue Feb 24 13:20:21 2026.
Rocky Linux 9 - AppStream
Name Stream Profiles Summary
mysql 8.4 api, client, filter, server [d] MySQL Module
Hint: [d]efault, [e]nabled, [x]disabled, [i]nstalled
This is holding my updates. I use mariadb which has always updateted until last major upgrade.
Could it be:
dnf module disable mysql
(See man dnf for options that the module accepts.)
Not the solution.
2026-02-24T13:41:57+0100 CRITICAL Error: Transaction test error:
file /usr/share/mysql/charsets/Index.xml conflicts between attempted installs of mysql-common-8.0.45-1.el9_7.x86_64 and MariaDB-common-10.6.25-1.el9.x86_64
file /usr/share/mysql/charsets/armscii8.xml conflicts between attempted installs of mysql-common-8.0.45-1.el9_7.x86_64 and MariaDB-common-10.6.25-1.el9.x86_64
file /usr/share/mysql/charsets/ascii.xml conflicts between attempted installs of mysql-common-8.0.45-1.el9_7.x86_64 and MariaDB-common-10.6.25-1.el9.x86_64
file /usr/share/mysql/charsets/cp1250.xml conflicts between attempted installs of mysql-common-8.0.45-1.el9_7.x86_64 and MariaDB-common-10.6.25-1.el9.x86_64
file /usr/share/mysql/charsets/cp1251.xml conflicts between attempted installs of mysql-common-8.0.45-1.el9_7.x86_64 and MariaDB-common-10.6.25-1.el9.x86_64
file /usr/share/mysql/charsets/cp1256.xml conflicts between attempted installs of mysql-common-8.0.45-1.el9_7.x86_64 and MariaDB-common-10.6.25-1.el9.x86_64
You would only have a mix and match of packages if at one point that module was used. Also, it depends if using mariadb that is available in Rocky by default, or also if you installed the MariaDB community repository. So not enough info on your situation right now.
But, usually you can use commands like:
dnf module reset mysql
which would effectively put it back to the defaults, so effectively unused. But again, it will only work if that module was used at some point.
Provide a list of repositories your system is using, eg:
dnf repolist
and also what files exist under /etc/yum.repos.d since we can then see if you are using third party repos which are not the responsibility of the Rocky team and potentially could explain the amout of problem you are having.
Also do:
rpm -qa | grep -i mysql
and:
rpm -qa | grep -i mariadb
Someone here had this exact same problem or similar already on this forum already due to misconfiguration caused by them.
[root@server5 ~]# dnf repolist
repo id repo name
appstream Rocky Linux 9 - AppStream
baseos Rocky Linux 9 - BaseOS
crb Rocky Linux 9 - CRB
devel Rocky Linux 9 - Devel WARNING! FOR BUILDROOT ONLY DO NOT LEAVE ENABLED
epel Extra Packages for Enterprise Linux 9 - x86_64
epel-cisco-openh264 Extra Packages for Enterprise Linux 9 openh264 (From Cisco) - x86_64
extras Rocky Linux 9 - Extras
mariadb-main MariaDB Server
mariadb-maxscale MariaDB MaxScale
mariadb-tools MariaDB Tools
ookla_speedtest-cli ookla_speedtest-cli
ookla_speedtest-cli-source ookla_speedtest-cli-source
plus Rocky Linux 9 - Plus
remi-modular Remi's Modular repository for Enterprise Linux 9 - x86_64
remi-safe Safe Remi's RPM repository for Enterprise Linux 9 - x86_64
rpmfusion-free-updates RPM Fusion for EL 9 - Free - Updates
rpmfusion-nonfree-updates RPM Fusion for EL 9 - Nonfree - Updates
[root@server5 ~]# rpm -qa | grep -i mysql
php-pecl-mysql-1.0.0-0.25.20210423.ca514c4.el9.remi.8.2.x86_64
postfix-mysql-3.5.25-1.el9.x86_64
perl-DBD-MySQL-4.050-13.el9.x86_64
dovecot-mysql-2.3.16-15.el9.x86_64
php-mysqlnd-8.2.29-1.el9.remi.x86_64
mysql-selinux-1.0.14-1.el9_6.noarch
[root@server5 ~]# rpm -qa | grep -i mariadb
perl-DBD-MariaDB-1.21-16.el9_0.x86_64
MariaDB-shared-10.6.24-1.el9.x86_64
MariaDB-common-10.6.24-1.el9.x86_64
MariaDB-client-10.6.24-1.el9.x86_64
MariaDB-server-10.6.24-1.el9.x86_64
MariaDB-backup-10.6.24-1.el9.x86_64
The mysql is added withe the november/december upgrade to the next version.
I installed rocky with mariadb. Mysql was never used.
dnf module reset mysql didn’t work.
These are not Rocky repositories. Also mysql-common is not installed either. Therefore a package is trying to pull it in which is conflicting with the mariadb repositories that you added to your system.
The package perl-DBD-MySQL requires mysql-common. You can try removing that package and see if the problem goes away. Assuming it doesn’t try to remove other packages that you need.
Also:
root@rocky9:~# dnf list --showduplicates perl-DBD-MySQL
Last metadata expiration check: 0:03:29 ago on Tue 24 Feb 2026 09:19:05 PM CET.
Available Packages
perl-DBD-MySQL.x86_64 4.053-1.el9.0.1 appstream
you can see why this is happening. The version you have installed is older. The one available on my system is the latest. Hence your system is trying to install the latest, because you have the old one installed. But due to the fact it has dependencies on mysql-common, it can’t be installed because it conflicts with mariadb-common.
So removing that package should fix your problem, but again you have to make sure when you remove it, it isn’t going to remove any other additional packages that you need. It probably won’t, but we will see as soon as you try to remove it, as it will tell you what else it will remove.
You also have perl-DBD-MariaDB installed, so you only need one of them. The perl-DBD-MySQL was left installed from whatever was installed on your server ages ago and the package got left behind.
I removed perl_DBD-MySQL.
It solved the problem. Update is running now.
Thanks