Merged
Conversation
This makes cnf use dnf4 data if you have /usr/bin/dnf, but not /usr/bin/dnf5.
The CI tests are identical to the dnf5 ones, except they use dnf instead of dnf5.
vyskocilm
approved these changes
Aug 30, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I don't know why I bothered with this (is there any reason to use
dnfoverdnf5, even when running the simply test cases it's noticibly slower), but sincednfv4 is in the openSUSE Tumbleweed repositories, I felt likecnfwas incomplete without it.Note that the docker image for dnf4 could trivially be generated by:
The changes to he rust code are a little less trivial as
dnfuses different folders for the.repoandsolvfiles.This relies on various changes made by my previous pull requests (#34, #35, and #36), only the last 3 commits are new.
Hopefully this will be my last pull request.