1DNF.MODULARITY(7) DNF DNF.MODULARITY(7)
2
6 dnf.modularity - Modularity in DNF
7 Modularity is new way of building, organizing and delivering packages.
9 For more details see: https://docs.pagure.org/modularity/
10
12 modulemd
13 Every repository can contain modules metadata with modulemd doc‐
14 uments. These documents hold metadata about modules such as
15 Name, Stream or list of packages.
16 (non-modular) package
18 Package that doesn't belong to a module.
19 modular package
21 Package that belongs to a module. It is listed in modulemd under
22 the artifacts section. Modular packages can be also identified
23 by having %{modularitylabel} RPM header set.
24 (module) stream
26 Stream is a collection of packages, a virtual repository. It is
27 identified with Name and Stream from modulemd separated with
28 colon, for example "postgresql:9.6".
29 Module streams can be active or inactive. active means the RPM
31 packages from this stream are included in the set of available
32 packages. Packages from inactive streams are filtered out.
33 Streams are active either if marked as default or if they are
34 explicitly enabled by a user action. Streams that satisfy depen‐
35 dencies of default or enabled streams are also considered ac‐
36 tive. Only one stream of a particular module can be active at a
37 given point in time.
38
40 Without modules, packages with the highest version are used by default.
41 Module streams can distribute packages with lower versions than avail‐
43 able in the repositories available to the operating system. To make
44 such packages available for installs and upgrades, the non-modular
45 packages are filtered out when their name or provide matches against a
46 modular package name from any enabled, default, or dependent stream.
47 Modular source packages will not cause non-modular binary packages to
48 be filtered out.
49
51 In special cases, a user wants to cherry-pick individual packages pro‐
52 vided outside module streams and make them available on along with
53 packages from the active streams. Under normal circumstances, such
54 packages are filtered out or rejected from getting on the system by
55 Fail-safe mechanisms. To make the system use packages from a reposi‐
56 tory regardless of their modularity, specify module_hotfixes=true in
57 the .repo file. This protects the repository from package filtering.
58 Please note the hotfix packages do not override module packages, they
60 only become part of available package set. It's the package Epoch, Ver‐
61 sion and Release what determines if the package is the latest.
62
64 Repositories with module metadata are unavailable
65 When a repository with module metadata is unavailable, package filter‐
66 ing must keep working. Non-modular RPMs must remain unavailable and
67 must never get on the system.
68 This happens when:
70 • user disables a repository via --disablerepo or uses --repoid
72 • user removes a .repo file from disk
74 • repository is not available and has skip_if_unavailable=true
76 DNF keeps copies of the latest modulemd for every active stream and
78 uses them if there's no modulemd available for the stream. This keeps
79 package filtering working correctly.
80 The copies are made any time a transaction is resolved and started.
82 That includes RPM transactions as well as any dnf module <enable|dis‐
83 able|reset> operations.
84 When the fail-safe data is used, dnf show such modules as part of @mod‐
86 ulefailsafe repository.
87 Orphaned modular packages
89 All packages that are built as a part of a module have %{modularityla‐
90 bel} RPM header set. If such package becomes part of RPM transaction
91 and cannot be associated with any available modulemd, DNF prevents from
92 getting it on the system (package is available, but cannot be in‐
93 stalled, upgraded, etc.). Packages from Hotfix repositories or Command‐
94 line repository are not affected by Fail-safe mechanisms.
95
97 See AUTHORS in DNF source distribution.
98
100 2012-2021, Red Hat, Licensed under GPLv2+
1014.7.0 May 13, 2021 DNF.MODULARITY(7)