Error message you get when updating MariaDB Server via Yum Update:
Solution, run the following command:
Done, you can run the Yum Update command again, to continue the update!
Source:
mariadb.org
The GPG keys listed for the "MariaDB Server" repository are already installed but they are not correct for this package.
Check that the correct key URLs are configured for this repository.. Failing package is: MariaDB-backup-10.6.12-1.el8.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/MariaDB-Server-GPG-KEY
Public key for MariaDB-client-10.6.12-1.el8.x86_64.rpm is not installed. Failing package is: MariaDB-client-10.6.12-1.el8.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/MariaDB-Server-GPG-KEY
Public key for MariaDB-common-10.6.12-1.el8.x86_64.rpm is not installed. Failing package is: MariaDB-common-10.6.12-1.el8.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/MariaDB-Server-GPG-KEY
Public key for MariaDB-server-10.6.12-1.el8.x86_64.rpm is not installed. Failing package is: MariaDB-server-10.6.12-1.el8.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/MariaDB-Server-GPG-KEY
Public key for MariaDB-shared-10.6.12-1.el8.x86_64.rpm is not installed. Failing package is: MariaDB-shared-10.6.12-1.el8.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/MariaDB-Server-GPG-KEY
Public key for galera-4-26.4.14-1.el8.x86_64.rpm is not installed. Failing package is: galera-4-26.4.14-1.el8.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/MariaDB-Server-GPG-KEY
The downloaded packages were saved in cache until the next successful transaction.
Solution, run the following command:
Code:
You must be logged-in to view.
(1 lines)Done, you can run the Yum Update command again, to continue the update!
Source:
mariadb.org
As mentioned in the previous batch of release notes (e.g. 10.6.11), our Yum/DNF/Zypper repositories for Red Hat Enterprise Linux, Centos, Fedora, openSUSE and SUSE will, from our next set of releases, be migrated to being signed with a new GPG key with SHA2 digest algorithms instead of SHA1.
The key we are migrating to is the same one we already use for our Debian and Ubuntu repositories.
You should apply package manager specific commands to clean and refresh the package cache.
- The short Key ID is: 0xC74CD1D8
- The long Key ID is: 0xF1656F24C74CD1D8
- The full fingerprint of the key is: 177F 4010 FE56 CA33 3630 0305 F165 6F24 C74C D1D8