Package filtering filters packages out from the available package
set, making them invisible to most of dnf commands. They cannot
be used in a transaction. Packages can be filtered out by either
Exclude Filtering or Modular Filtering.
Exclude Filtering
Exclude Filtering is a mechanism used by a user or by a DNF
plugin to modify the set of available packages. Exclude Filtering
can be modified by either includepkgs or excludepkgs
configuration options in configuration files. The -‐
-disableexcludes command line option can be used to override
excludes from configuration files. In addition to user-configured
excludes, plugins can also extend the set of excluded packages.
To disable excludes from a DNF plugin you can use the -‐
-disableplugin command line option.
To disable all excludes for e.g. the install command you can use
the following combination of command line options:
dnf --disableexcludes=all --disableplugin="*" install bash
Modular Filtering
Please see the modularity documentation for details on how
Modular Filtering works.
With modularity, only RPM packages from active module streams are
included in the available package set. RPM packages from inactive
module streams, as well as non-modular packages with the same
name or provides as a package from an active module stream, are
filtered out. Modular filtering is not applied to packages added
from the command line, installed packages, or packages from
repositories with module_hotfixes=true in their .repo file.
Disabling of modular filtering is not recommended, because it
could cause the system to get into a broken state. To disable
modular filtering for a particular repository, specify
module_hotfixes=true in the .repo file or use
--setopt=<repo_id>.module_hotfixes=true.
To discover the module which contains an excluded package use dnf
module provides.
