Skip to content

Commit

Permalink
Don't use --allowerasing for more DNF commands
Browse files Browse the repository at this point in the history
  • Loading branch information
FrostyX committed Mar 3, 2024
1 parent fc1f7d4 commit 3dad233
Show file tree
Hide file tree
Showing 2 changed files with 9 additions and 1 deletion.
8 changes: 7 additions & 1 deletion mock/py/mockbuild/config.py
Original file line number Diff line number Diff line change
Expand Up @@ -328,7 +328,13 @@ def setup_default_config_opts():
config_opts['dnf5_disable_plugins'] = []
# No --allowerasing with remove, per
# https://github.com/rpm-software-management/dnf5/issues/729
config_opts["dnf5_avoid_opts"] = {"remove": ["--allowerasing"]}
config_opts["dnf5_avoid_opts"] = {
"remove": ["--allowerasing"],
"repoquery": ["--allowerasing"],
"makecache": ["--allowerasing"],
"search": ["--allowerasing"],
"info": ["--allowerasing"],
}

config_opts['microdnf_command'] = '/usr/bin/microdnf'
# "dnf-install" is special keyword which tells mock to use install but with DNF
Expand Down
2 changes: 2 additions & 0 deletions releng/release-notes-next/allowerasing.bugfix
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
Don't use the `--allowerasing` parameter for DNF subcommands such as
`repoquery`, `makecache`, `search`, and `info`.

0 comments on commit 3dad233

Please sign in to comment.