-
Notifications
You must be signed in to change notification settings - Fork 102
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
[REGRESSION] dnf5 does not pull signing keys #2134
Comments
Commit in question: 0f1242b This fix is invalid since this does not match the behaviour of |
Thanks for reporting! This looks quite serious. I noticed interesting warning in dnf5.log during terra repository metadata downloading:
which seems wrong since the repo doesn't have skip_if_unavaileble set (thus should default to |
Quick temporary workaround for rpm-software-management/dnf5#2134
dnf5
5.2.11.0
has a regression where it refuses to pull missing signing keys from repos during syncing. This worked fine on5.2.10.0
.To Reproduce
podman pull ghcr.io/terrapkg/builder:frawhide
, this pulls the latest podman image from our buildersAs of today, the sha is a5f3fd92ce13
podman run -it ghcr.io/terrapkg/builder:frawhide
dnf in -y 'pkgconfig(astal-io-0.1)'
Old Behaviour
This is generated using
podman run -it 8b8895c43b10
(an older builder image withdnf5
5.2.10.0
)If you would like to reproduce, try downloading
5.2.11.0
from koji manually.The text was updated successfully, but these errors were encountered: