-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Certificate issue with the COPR repo... #82
Comments
Hm, this is news to me! My usage of copr is pretty basic, i.e. I simply trigger builds manually and the repository keys are automagically generated and maintained by the copr service. I recently triggered a new build since there wasn't a f40 native build yet and a few changes have been in the pipeline. I can reproduce the issue right now:
It seems that I have to improve the error reporting of my dnf-auto-update cron job ... The gpg key on my system reads:
That system was upgraded the last few fedora releases via So it looks like the copr client integration for some reason doesn't take care of importing follow-up public keys that are generated on the copr server side, i.e. in time before the original one expires. Thus, it appears that this still the key that was imported when I added that copr repository via Ok, there is an open upstream copr bug report about this: |
FWIW, a work-around:
This pulls in the latest/greatest public key like this:
|
Something happened recently with the copr?
The text was updated successfully, but these errors were encountered: