Open praiskup opened 1 year ago
[root@pc-loznice yum.repos.d]# rpm -qi gpg-pubkey-d1c452b2-59ac3ee9
Name : gpg-pubkey
Version : d1c452b2
Release : 59ac3ee9
Architecture: (none)
Install Date: Pá 14. prosince 2018, 15:18:58
Group : Public Keys
Size : 0
License : pubkey
Signature : (none)
Source RPM : (none)
Build Date : Ne 3. září 2017, 19:42:01
Build Host : localhost
Packager : praiskup_myvpn (None) <praiskup#myvpn@copr.fedorahosted.org>
Summary : gpg(praiskup_myvpn (None) <praiskup#myvpn@copr.fedorahosted.org>)
Description :
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: rpm-4.14.2.1 (NSS-3)
mQENBFmsPukBCADQShlYpNGZu+8+4gGWvDB82Z2AyWso+d9DpTHy/qTvU93oOR6V
hwVZgVT4ci9EU82GpC4HX9KEzm7CtJ9FC73r48W7zVzIpR4Crpci1l3zWEfiHSON
rTdcyifdHt9e1pG6WgiOLv8ToeNXZH7xpj0ijtepN0vngw0KNujFxYXZ+JH+SRPo
Dmaa8s/YQb9Pd1F3laDJm+I+rjz4MuSuBDpDxwUfJYhtItJM4tCMXMtIgUF5rT4/
Fax5GgpCFTsR+d0pg4S/sIx+qY14g2T3ibeqCmJdvLIIogxSK9XxEN46JiKnWz/W
fOGP7YyFovRNIJDxNK4fDFBAzHd+SNgRl821ABEBAAG0PHByYWlza3VwX215dnBu
IChOb25lKSA8cHJhaXNrdXAjbXl2cG5AY29wci5mZWRvcmFob3N0ZWQub3JnPokB
PQQTAQgAJwUCWaw+6QIbLwUJCWYBgAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAK
CRBFRySn0cRSshOOCADNOp6wJU92iMOfIMYLH7nbs2NFyPrboeuLFpRaxO3LFqyK
RuLzJP8hEqAoiVqsR0+GckLZ9D+LE3lAElgiHX52LRVSwdNv2w1sqm/NSNfBuqdj
U1Gu5vOnRgeYgPlll7HK+gnGJ6zhXrR7M+ZuY36sEI7LrtYUTAy6CY47kjYuqgss
sTYHQT3VzALbK7SY32V1BBS9p4iMwkMPDfHzR6tBKNmf8nE7cGpjHPds9ZJXOlVD
Z/HMuhAtTqwFy1yOJUVi6foGQGHvxh+0pmlaeR4Or57pAii1hLWH2ScE4dY2xEf/
kWOQeu3lqU7KR5asFBd2xjQpHVMAvAzmT/xkJzF4
=U0/K
-----END PGP PUBLIC KEY BLOCK-----
Way around:
$ # drop the old key
$ rpm -e gpg-pubkey-d1c452b2-59ac3ee9 # drop the old key
$ # install the prolonged one
$ rpm --import https://download.copr.fedorainfracloud.org/results/praiskup/myvpn/pubkey.gpg
Is there a way to automatize this?
Mirek claims that DNF and RPM has a separate gpg key database
From Mirek, see also: https://bugzilla.redhat.com/show_bug.cgi?id=1768206
See also discussion in #2935 -> that might open a door for very fast RPM re-signing.
Triage: We probably need to solve this in the DNF Copr plugin
Related RPM discussion: https://github.com/rpm-software-management/rpm-sequoia/issues/50#issuecomment-1682313430
Triage time:
dnf copr enable
(re-enable) and do some magic in the background?dnf copr refres-keys
?For the record, this happened to me with korkeala/clojure, we also got Matrix report about agriffis/neovim-nightly and Reddit post here https://www.reddit.com/r/Fedora/comments/181omz0/how_to_fix_expired_gpg_keys_on_old_copr_repos/
New ticket against DNF4 https://github.com/rpm-software-management/dnf/issues/2075
Certificiate
I've hit this issue too. As an aside, I greped a few repos to find this typo and I couldn't. If anyone could point me to that code I'd be interested, thanks!
Hello @purpleidea, I am not sure what typo do you mean and what code are you interested in. But here are few relevant links for you :-)
We keep this Copr issue open so that users know this can happen and use it as a starting point but there isn't actually any relevant bug in Copr. Everything needs to be fixed on the Dnf and RPM side of things.
Current status:
rpm
and rpm-sequoia
code is finished and merged to master
but not released yet--enableplugin=expired-pgp-keys
or enable the plugin in /etc/dnf/plugins/expired-pgp-keys.conf
. We agreed with @jan-kolarik that it needs to be disabled by default but that we should change the "GPG check FAILED" error to provide instructions to use the plugin for resolving the issue.