We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
microdnf will ignore a repo's gpgkey URL if it is https:// when the repo's baseurl is file://.
microdnf
gpgkey
https://
baseurl
file://
Here's an example /etc/yum.repos.d/build.repo file that triggers this:
/etc/yum.repos.d/build.repo
[build] name = my builds baseurl = file:///build enabled = 1 gpgcheck = 1 gpgkey = https://www.example.com/MY-RPM-GPG-KEY
microdnf will say that the packages in this repo are unsigned and refuse to install them. It will not import the GPG key.
dnf will download GPG key over HTTPS, add it to the trust store, and properly verify the packages.
dnf
As a workaround, I must download the GPG key to local disk, and then use a file:// URL for gpgkey. Then microdnf will import the key as expected.
Tested with:
libdnf-0.69.0-8.el9
microdnf-3.9.1-3.el9
dnf-4.14.0-9.el9
The text was updated successfully, but these errors were encountered:
No branches or pull requests
microdnf
will ignore a repo'sgpgkey
URL if it ishttps://
when the repo'sbaseurl
isfile://
.Here's an example
/etc/yum.repos.d/build.repo
file that triggers this:microdnf
will say that the packages in this repo are unsigned and refuse to install them. It will not import the GPG key.dnf
will download GPG key over HTTPS, add it to the trust store, and properly verify the packages.As a workaround, I must download the GPG key to local disk, and then use a
file://
URL forgpgkey
. Thenmicrodnf
will import the key as expected.Tested with:
libdnf-0.69.0-8.el9
microdnf-3.9.1-3.el9
dnf-4.14.0-9.el9
The text was updated successfully, but these errors were encountered: