【mysql】解决MySQLGPG密钥过期问题MySQL GPG 密钥过期，yum下载mysql-devel报错
正⽂开始@Assassin
⽬录：
记录make中的⼀次报错~~
刚刚centos7在执⾏make时遇到以下报错：
fatal error: mysql/mysql.h: No such file or directory
#include<mysql/mysql.h>
compilation terminated.
原因是不到mysql.h头⽂件，于是使⽤以下命令安装对应的包：
sudo yum install mysql-devel
但是却出现了如下的报错：
只能说翻来覆去了很久都没到有⽤的⽅法，还是得StackOverflow
Downloading packages:
warning: /var/cache/yum/x86_64/7/mysql57-community/packages/mysql-community-devel-5.7.37-1.el7.x86_64.rpm: Header V4 RSA/SHA256 Signature, k ey ID 3a79bd29: NOKEY
Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql
The GPG keys listed for the "MySQL 5.7 Community 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: mysql-community-devel-5.7.37-1.el7.x86_64
mysql下载后安装中出现提示不到安装包GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql
==翻译：==
警告：/var/cache/yum/ x86_64/7/mysql57-community/packages/mysql-community-libs-compat-5.7.37-1.el7.x86_64.rpm: Header V4 RSA/SHA256 Signatur e, key ID 3a79bd29: NOKEY
Retrieving key from file:/// etc/pki/rpm-gpg/RPM-GPG-KEY-mysql
为“MySQL 5.7社区服务器”存储库列出的 GPG 密钥已经安装，但它们对于这个包不正确。
检查是否为此存储库配置了正确的密钥 URL。
失败的包是：mysql-community-libs-compat-5.7.37-1.el7.x86_64
GPG 密钥配置为：file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql
症状：
官⽅ MySQL 存储库的 GPG 密钥已过期，⽆法安装或更新 MySQL 包。
为 “MySQL 5.7 社区服务器” 存储库列出的 GPG 密钥已经安装，但它们对于这个包不正确
错误类似于：
为“MySQL 8.0社区服务器”存储库列出的 GPG 密钥已安装，但对于此包来说它们不正确。检查是否为此存储库配置了正确的密钥 URL。失败的包是：mysql-c ommunity-client-8.0.28-1.el8.x86_64 GPG 密钥配置为：sql/RPM- GPG-KEY-mysql
未安装 mysql-community-client-plugins-8.0.28-1.el8.x86_64.rpm 的公钥。失败的包是：mysql-community-client-plugins-8.0.28-1.el8.x86_64 GPG 密钥配置为：sql/RPM-GPG-KEY-mysql
mysql-community 的公钥-common-8.0.28-1.el8.x86_64.rpm 未安装。失败的包是：mysql-community-common-8.0.28-1.el8.x86_64 GPG 密钥配置为：http:/ /sql/RPM-GPG-KEY-mysql
未安装 mysql-community-devel-8.0.28-1.el8.x86_64.rpm 的公钥。失败的包是：mysql-community-devel-8.0.28-1.el8.x86_64 GPG 密钥配置为：repo. mysql/RPM-GPG-KEY-mysql
mysql-community-icu 的公钥-data-files-8.0.28-1.el8.x86_64.rpm 未安装。失败的包是：mysql-community-icu-data-files-8.0.28-1.el8.x86_64 GPG 密钥配置为：sql/RPM-GPG-KEY-mysql
mysql 的公钥-community-libs-8.0.28-1.el8.x86_64.rpm 未安装。失败的包是：mysql-community-libs-8.0.28-1.el8.x86_64 GPG 密钥配置为：s ql/RPM-GPG-KEY-mysql
未安装 mysql-community-server-8.0.28-1.el8.x86_64.rpm 的公钥。失败的包是：mysql-community-server-8.0.28-1.el8.x86_64 GPG 密钥配置为：sql/RPM-GPG-KEY-mysql 错误：GPG 检查失败
描述：
MySQL GPG 密钥已过期。有关案例的其他详细信息也可以在 MySQL ⽹站上到：
解决⽅法：
Note
If you are using RPM 4.1 and it complains about (GPG) NOT OK (MISSING KEYS: GPG#3a79bd29), even though you have imported the MySQL public build key into your own GPG keyring, you need to import the key into the RPM
keyring first. RPM 4.1 no longer uses your personal GPG keyring (or GPG itself). Rather, RPM maintains a separate keyring because it is a system-wide application and a user’s GPG public keyring is a user-specific file. To import the MySQL public key into the RPM keyring, first obtain the key, then use rpm --import to import the key. For example:
可以在运⾏安装程序之前导⼊密钥：
rpm --import sql/RPM-GPG-KEY-mysql-2022
Ubuntu：
wget -q -O - sql/RPM-GPG-KEY-mysql-2022 | apt-key add -之后再执⾏yum install mysql-devel 就over了
makefile：

版权声明：本站内容均来自互联网，仅供演示用，请勿用于商业和其他非法用途。如果侵犯了您的权益请与我们联系QQ:729038198，我们将在24小时内删除。