Debian Codegraph @

upstream/mageia-cauldron/man7/dnf5-modularity.7

raw
1 .\" Man page generated from reStructuredText.
2 .
3 .
4 .nr rst2man-indent-level 0
5 .
6 .de1 rstReportMargin
7 \\$1 \\n[an-margin]
8 level \\n[rst2man-indent-level]
9 level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
10 -
11 \\n[rst2man-indent0]
12 \\n[rst2man-indent1]
13 \\n[rst2man-indent2]
14 ..
15 .de1 INDENT
16 .\" .rstReportMargin pre:
17 . RS \\$1
18 . nr rst2man-indent\\n[rst2man-indent-level] \\n[an-margin]
19 . nr rst2man-indent-level +1
20 .\" .rstReportMargin post:
21 ..
22 .de UNINDENT
23 . RE
24 .\" indent \\n[an-margin]
25 .\" old: \\n[rst2man-indent\\n[rst2man-indent-level]]
26 .nr rst2man-indent-level -1
27 .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
28 .in \\n[rst2man-indent\\n[rst2man-indent-level]]u
29 ..
30 .TH "DNF5-MODULARITY" "7" "May 10, 2026" "" "dnf5"
31 .SH NAME
32 dnf5-modularity \- Modularity Overview
33 .SH DESCRIPTION
34 .sp
35 Modularity is an alternative way of building, organizing and delivering packages.
36 For more details see: \X'tty: link https://docs.pagure.org/modularity/'\fI\%https://docs.pagure.org/modularity/\fP\X'tty: link'\&.
37 .SH DEFINITIONS
38 .INDENT 0.0
39 .TP
40 .B modulemd
41 Every repository can contain \fBmodules\fP metadata with modulemd documents.
42 These documents hold metadata about modules such as \fBName\fP, \fBStream\fP or list of packages.
43 .TP
44 .B (non\-modular) package
45 Package that doesn\(aqt belong to a module.
46 .TP
47 .B modular package
48 Package that belongs to a module. It is listed in modulemd under the \fBartifacts\fP section.
49 Modular packages can be also identified by having \fB%{modularitylabel}\fP RPM header set.
50 .TP
51 .B (module) stream
52 Stream is a collection of packages, a virtual repository. It is identified with
53 \fBName\fP and \fBStream\fP from modulemd separated with colon, for example \(dqpostgresql:9.6\(dq.
54 .sp
55 Module streams can be \fBactive\fP or \fBinactive\fP\&. \fBactive\fP means the RPM
56 packages from this stream are included in the set of available packages.
57 Packages from \fBinactive\fP streams are filtered out. Streams are
58 \fBactive\fP either if marked as \fBdefault\fP or if they are explicitly
59 \fBenabled\fP by a user action. Streams that satisfy dependencies of
60 \fBdefault\fP or \fBenabled\fP streams are also considered \fBactive\fP\&. Only
61 one stream of a particular module can be \fBactive\fP at a given point in
62 time.
63 .UNINDENT
64 .SH PACKAGE FILTERING
65 .sp
66 Without modules, packages with the highest version are used by default.
67 .sp
68 Module streams can distribute packages with lower versions than available in the
69 repositories available to the operating system. To make such packages available
70 for installs and upgrades, the non\-modular packages are filtered out when their
71 name or provide matches against a modular package name from any enabled, default,
72 or dependent stream. Modular source packages will not cause non\-modular binary
73 packages to be filtered out.
74 .SH DEMODULARIZED RPMS
75 .sp
76 Contains names of RPMs excluded from package filtering for particular module stream. When defined in the latest active
77 module, non\-modular RPMs with the same name or provide which were previously filtered out will reappear.
78 .SH HOTFIX REPOSITORIES
79 .sp
80 In special cases, a user wants to cherry\-pick individual packages provided outside module
81 streams and make them available on along with packages from the active streams.
82 Under normal circumstances, such packages are filtered out or rejected from getting on the system by
83 Fail\-safe mechanisms.
84 To make the system use packages from a repository regardless of their modularity,
85 specify \fBmodule_hotfixes=true\fP in the .repo file. This protects the repository from package filtering.
86 .sp
87 Please note the hotfix packages do not override module packages, they only become
88 part of available package set. It\(aqs the package \fBEpoch\fP, \fBVersion\fP and \fBRelease\fP
89 what determines if the package is the latest.
90 .SH FAIL-SAFE MECHANISMS
91 .SH REPOSITORIES WITH MODULE METADATA ARE UNAVAILABLE
92 .sp
93 When a repository with module metadata is unavailable, package filtering must keep working.
94 Non\-modular RPMs must remain unavailable and must never get on the system.
95 .sp
96 This happens when:
97 .INDENT 0.0
98 .IP \(bu 2
99 user disables a repository via \fB\-\-disable\-repo\fP or uses \fB\-\-repo\fP
100 .IP \(bu 2
101 user removes a .repo file from disk
102 .IP \(bu 2
103 repository is not available and has \fBskip_if_unavailable=true\fP
104 .UNINDENT
105 .sp
106 DNF5 keeps copies of the latest modulemd for every active stream
107 and uses them if there\(aqs no modulemd available for the stream.
108 This keeps package filtering working correctly.
109 .sp
110 The copies are made any time a transaction is resolved and started.
111 That includes RPM transactions as well as any \fBdnf5 module <enable|disable|reset>\fP operations.
112 .sp
113 When the fail\-safe data is used, DNF5 show such modules as part of @modulefailsafe repository.
114 .SH ORPHANED MODULAR PACKAGES
115 .sp
116 All packages that are built as a part of a module have \fB%{modularitylabel}\fP RPM header set.
117 If such package becomes part of RPM transaction and cannot be associated with any available
118 modulemd, DNF5 prevents from getting it on the system (package is available, but cannot be
119 installed, upgraded, etc.). Packages from Hotfix repositories or Commandline repository are not
120 affected by Fail\-safe mechanisms.
121 .SH AUTHOR
122 See AUTHORS.md in dnf5 source distribution.
123 .SH COPYRIGHT
124 Contributors to the dnf5 project.
125 .\" Generated by docutils manpage writer.
126 .