-
Notifications
You must be signed in to change notification settings - Fork 99
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
Limit search pattern for remove command #1126
Conversation
6d49ac8
to
55b0c1a
Compare
Could you make a commit subject more specific? Like "Limit search pattern for remove command to NEVRAs and files" |
This is a quite serious change which deserves a test. Do you plan enhancing ci-dnf-stack? |
It prevents additional removal after succesful remove using the same spec. Spec `foo`. The original code during the first run removes (dnf5 remove foo) all packages with the name `foo`. In the next run (dnf5 remove foo) it removes all packages providing `foo`. The next run will remove packages providing binary `foo`. This behavior is inconsistent. Resolves: https://issues.redhat.com/browse/RHEL-5747
a58f0ac
to
75ba583
Compare
The code require following change of CI - rpm-software-management/ci-dnf-stack#1430. It removes all tests for formal behavior and add one test for the new behavior. |
The new behavior is more stable for cases when the same spec is used multiple times with remove command. Requires: rpm-software-management/dnf5#1126
@ppisar Done |
It unify style with remove command, because it uses the same argument type.
75ba583
to
b26fe41
Compare
@ppisar Thank you for couching it. Fixed. |
870a8a0
The new behavior is more stable for cases when the same spec is used multiple times with remove command. Requires: rpm-software-management/dnf5#1126
The new behavior is more stable for cases when the same spec is used multiple times with remove command. Requires: rpm-software-management/dnf5#1126
It prevents additional removal after succesful remove using the same spec. Spec
foo
. The original code during the first run removes (dnf5 remove foo) all packages with the namefoo
. In the next run (dnf5 remove foo) it removes all packages providingfoo
. The next run will remove packages providing binaryfoo
. This behavior is inconsistent.Resolves: https://issues.redhat.com/browse/RHEL-5747
CI-tests - rpm-software-management/ci-dnf-stack#1430