On Thu, Jun 19, 2025 at 11:11 PM gaosong <gaos...@loongson.cn> wrote: > > 在 2025/6/20 上午4:39, Stefan Hajnoczi 写道: > > gpg: using RSA key CA473C44D6A09C189A193FCD452B96852B268216 > > gpg: Can't check signature: No public key > > > > Why has the GPG key changed? Your previous pull request was signed > > with key B8FF1DA0D2FDCB2DA09C6C2C40A2FFF239263EDF. > > > > If you would like to change keys, please sign your new key using your > > old key and upload the new key to the key servers again. That way I > > know that the new key really belongs to you. > Hi, Stefan > > I had sign new key using old key and send to the key server again > should I need pull again?
Thanks! The pull request does not need to be resent. I wasn't able to fetch your new key with the signature from the keyservers though. Did you `gpg --send-keys 0x452B96852B268216`? Alternatively, you could attach your new signed gpg key and send it as an email attachment. Stefan > > Thanks. > Song Gao > > gpg --list-signatures > /home/gaosong/.gnupg/pubring.kbx > -------------------------------- > pub rsa1024 2022-09-16 [SC] > B8FF1DA0D2FDCB2DA09C6C2C40A2FFF239263EDF > uid [ 未知 ] Song Gao <m17746591...@163.com> > sig 3 40A2FFF239263EDF 2022-09-16 Song Gao <m17746591...@163.com> > sig 452B96852B268216 2025-06-20 Song Gao <gaos...@loongson.cn> > > pub rsa1024 2022-09-16 [SC] > CA473C44D6A09C189A193FCD452B96852B268216 > uid [ 未知 ] Song Gao <gaos...@loongson.cn> > sig 3 452B96852B268216 2022-09-16 Song Gao <gaos...@loongson.cn> > sig 40A2FFF239263EDF 2025-06-20 Song Gao <m17746591...@163.com> > > > gpg --send-keys CA473C44D6A09C189A193FCD452B96852B268216 > gpg: 正在发送密钥 452B96852B268216 到 hkps://keys.openpgp.org > gpg --recv-keys CA473C44D6A09C189A193FCD452B96852B268216 > gpg: 密钥 452B96852B268216：“Song Gao <gaos...@loongson.cn>” 未改变 > gpg: 处理的总数：1 > gpg: 未改变：1 > > >
