NAME<\/a> dnf.modularity \u2212 Modularity in DNF<\/p>\n Modularity is new way of building, organizing and delivering packages. For more details see: https:\/\/docs.pagure.org\/modularity\/<\/i><\/p>\n modulemd<\/b><\/i><\/p>\n Every repository can contain modules<\/b> metadata with modulemd documents. These documents hold metadata about modules such as Name<\/b>, Stream<\/b> or list of packages.<\/p>\n (non\u2212modular) package<\/b><\/p>\n Package that doesn’t belong to a module.<\/p>\n modular package<\/b><\/p>\n Package that belongs to a module. It is listed in modulemd under the artifacts<\/b> section. Modular packages can be also identified by having %{modularitylabel}<\/b> RPM header set.<\/p>\n (module) stream<\/b><\/p>\n Stream is a collection of packages, a virtual repository. It is identified with Name<\/b> and Stream<\/b> from modulemd separated with colon, for example “postgresql:9.6”.<\/p>\n Module streams can be active<\/b> or inactive<\/b>. active<\/b> means the RPM packages from this stream are included in the set of available packages. Packages from inactive<\/b> streams are filtered out. Streams are active<\/b> either if marked as default<\/b> or if they are explicitly enabled<\/b> by a user action. Streams that satisfy dependencies of default<\/b> or enabled<\/b> streams are also considered active<\/b>. Only one stream of a particular module can be active<\/b> at a given point in time.<\/p>\n Without modules, packages with the highest version are used by default.<\/p>\n Module streams can distribute packages with lower versions than available in the repositories available to the operating system. To make such packages available for installs and upgrades, the non\u2212modular packages are filtered out when their name or provide matches against a modular package name from any enabled, default, or dependent stream. Modular source packages will not cause non\u2212modular binary packages to be filtered out.<\/p>\n In special cases, a user wants to cherry\u2212pick individual packages provided outside module streams and make them available on along with packages from the active streams. Under normal circumstances, such packages are filtered out. To make the system use packages from a repository regardless of their modularity, specify module_hotfixes=true<\/b> in the .repo file. This protects the repository from package filtering.<\/p>\n Please note the hotfix packages do not override module packages, they only become part of available package set. It’s the package Epoch<\/b>, Version<\/b> and Release<\/b> what determines if the package is the latest.<\/p>\n Repositories with module metadata are unavailable<\/b> This happens when:<\/p>\n
DEFINITIONS<\/a>
PACKAGE FILTERING<\/a>
HOTFIX REPOSITORIES<\/a>
FAIL-SAFE MECHANISMS<\/a>
AUTHOR<\/a>
COPYRIGHT<\/a> <\/p>\n
\nNAME <\/a> <\/h2>\n
DEFINITIONS <\/a> <\/h2>\n
PACKAGE FILTERING <\/a> <\/h2>\n
HOTFIX REPOSITORIES <\/a> <\/h2>\n
FAIL-SAFE MECHANISMS <\/a> <\/h2>\n
When a repository with module metadata is unavailable, package filtering must keep working. Non\u2212modular RPMs must remain unavailable and must never get on the system.<\/p>\n