> * The most noticeable change is that RPM now refuses to install > packages whose signature hasn't been positively verified, whether due > to being unsigned, missing key or otherwise. This can be worked around > by supplying `--nosignature` on the command line, or more permanently, > changing the `%_pkgverify_level` macro to the former default of > `digest`, but these should be only temporary measures, users are > encouraged to import necessary keys and/or setup automatic signing for > their (local) builds instead. Does this impact installations via “dnf install”? What's the impact on typical Fedora CI tests? Thanks, Flroian -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
