Require only dnf5 in ELN #1518
Merged
Require only dnf5 in ELN #1518
Conversation
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
ELN uses dnf5 in which versionlock is a built-in command.
6 tasks
Collaborator
|
LGTM +1 |
While some packages still need to be ported from libdnf or python3-dnf and will remain in ELN in the meantime, the goal is to fully transition to dnf5 for RHEL 11 and therefore dnf-4 should not be listed as required. dnf5 also provides/obsoletes microdnf, so the minimal workload is obsolete.
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.
While some packages still need to be ported from libdnf or python3-dnf and will remain in ELN in the meantime, the goal is to fully transition to dnf5 for RHEL 11 and therefore dnf-4 should not be listed as required.
dnf5 also provides/obsoletes microdnf, so the minimal workload is obsolete.
versionlock is a built-in command in dnf5.
/cc @tdawson wrt azure image, let's make sure that's not being installed in our image?