-
Notifications
You must be signed in to change notification settings - Fork 334
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
RHEL Packages: GPG check fails when explicitly enabled #1341
Comments
@thresheek Could you please look at this? Thank you 🙏 |
Hi @ivanov17! Did you try to remove and re-import the gpg keys as per the blog guidelines? |
Hello @thresheek! I'm building custom container images using the official CentOS Stream 9 base image and packages from the Unit repository. I don't have to re-import the gpg key since a new key is used each time I build. |
Thanks for the details. It looks like dnf's implementation for There is even a bug from 2019 on RedHat bugzilla about it: https://bugzilla.redhat.com/show_bug.cgi?id=1768206 I think for now your only solution would be to disable repo_gpgcheck and rely on packages signatures instead. |
Thank you, but it doesn't seem to work. I can only create an image if I disable both options (for repo and packages). |
Can't reproduce with:
|
@thresheek you are right. It really works with Sorry, I forgot to mention that I'm using a minimal image. The minimal base image uses
However, there is some good news. I tried using the minimal Fedora 39 image. This image uses So, this problem only applies to |
I don't think we can do anything about it. This needs to be fixed in dnf/microdnf. |
In any case, thanks for your help. I'm thinking about reporting this bug to Red Hat, but for now I'll just disable gpg checks. So, we can close this issue I guess. |
Hello team,
I'm trying to install packages from the Unit repository, but I'm getting the following error:
I have explicitly configured the GPG check. Here is my repository configuration:
I'm not sure when exactly it broke, but I know it worked before. I think this may be related to the GPG key update in early June 2024.
Please fix this. Thank you.
The text was updated successfully, but these errors were encountered: