Debian Codegraph @

upstream/debian-trixie/man7/dnf4.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 "DNF4.MODULARITY" "7" "Mar 09, 2025" "4.23.0" "DNF"
31 .SH NAME
32 dnf4.modularity \- Modularity in DNF
33 .sp
34 Modularity is new way of building, organizing and delivering packages.
35 For more details see: \X'tty: link https://docs.pagure.org/modularity/'\fI\%https://docs.pagure.org/modularity/\fP\X'tty: link'
36 .SH DEFINITIONS
37 .INDENT 0.0
38 .TP
39 .B modulemd
40 Every repository can contain \fBmodules\fP metadata with modulemd documents.
41 These documents hold metadata about modules such as \fBName\fP, \fBStream\fP or list of packages.
42 .TP
43 .B (non\-modular) package
44 Package that doesn\(aqt belong to a module.
45 .TP
46 .B modular package
47 Package that belongs to a module. It is listed in modulemd under the \fBartifacts\fP section.
48 Modular packages can be also identified by having \fB%{modularitylabel}\fP RPM header set.
49 .TP
50 .B (module) stream
51 Stream is a collection of packages, a virtual repository. It is identified with
52 \fBName\fP and \fBStream\fP from modulemd separated with colon, for example \(dqpostgresql:9.6\(dq.
53 .sp
54 Module streams can be \fBactive\fP or \fBinactive\fP\&. \fBactive\fP means the RPM
55 packages from this stream are included in the set of available packages.
56 Packages from \fBinactive\fP streams are filtered out. Streams are
57 \fBactive\fP either if marked as \fBdefault\fP or if they are explicitly
58 \fBenabled\fP by a user action. Streams that satisfy dependencies of
59 \fBdefault\fP or \fBenabled\fP streams are also considered \fBactive\fP\&. Only
60 one stream of a particular module can be \fBactive\fP at a given point in
61 time.
62 .UNINDENT
63 .SH PACKAGE FILTERING
64 .sp
65 Without modules, packages with the highest version are used by default.
66 .sp
67 Module streams can distribute packages with lower versions than available in the
68 repositories available to the operating system. To make such packages available
69 for installs and upgrades, the non\-modular packages are filtered out when their
70 name or provide matches against a modular package name from any enabled, default,
71 or dependent stream. Modular source packages will not cause non\-modular binary
72 packages to be filtered out.
73 .SS Demodularized rpms
74 .sp
75 Contains names of RPMs excluded from package filtering for particular module stream. When defined in the latest active
76 module, non\-modular RPMs with the same name or provide which were previously filtered out will reappear.
77 .SH HOTFIX REPOSITORIES
78 .sp
79 In special cases, a user wants to cherry\-pick individual packages provided outside module
80 streams and make them available on along with packages from the active streams.
81 Under normal circumstances, such packages are filtered out or rejected from getting on the system by
82 Fail\-safe mechanisms.
83 To make the system use packages from a repository regardless of their modularity,
84 specify \fBmodule_hotfixes=true\fP in the .repo file. This protects the repository from package filtering.
85 .sp
86 Please note the hotfix packages do not override module packages, they only become
87 part of available package set. It\(aqs the package \fBEpoch\fP, \fBVersion\fP and \fBRelease\fP
88 what determines if the package is the latest.
89 .SH FAIL-SAFE MECHANISMS
90 .SS Repositories with module metadata are unavailable
91 .sp
92 When a repository with module metadata is unavailable, package filtering must keep working.
93 Non\-modular RPMs must remain unavailable and must never get on the system.
94 .sp
95 This happens when:
96 .INDENT 0.0
97 .IP \(bu 2
98 user disables a repository via \fB\-\-disablerepo\fP or uses \fB\-\-repoid\fP
99 .IP \(bu 2
100 user removes a .repo file from disk
101 .IP \(bu 2
102 repository is not available and has \fBskip_if_unavailable=true\fP
103 .UNINDENT
104 .sp
105 DNF keeps copies of the latest modulemd for every active stream
106 and uses them if there\(aqs no modulemd available for the stream.
107 This keeps package filtering working correctly.
108 .sp
109 The copies are made any time a transaction is resolved and started.
110 That includes RPM transactions as well as any \fBdnf module <enable|disable|reset>\fP operations.
111 .sp
112 When the fail\-safe data is used, dnf show such modules as part of @modulefailsafe repository.
113 .SS Orphaned modular packages
114 .sp
115 All packages that are built as a part of a module have \fB%{modularitylabel}\fP RPM header set.
116 If such package becomes part of RPM transaction and cannot be associated with any available
117 modulemd, DNF prevents from getting it on the system (package is available, but cannot be
118 installed, upgraded, etc.). Packages from Hotfix repositories or Commandline repository are not
119 affected by Fail\-safe mechanisms.
120 .SH AUTHOR
121 See AUTHORS in DNF source distribution.
122 .SH COPYRIGHT
123 2012-2020, Red Hat, Licensed under GPLv2+
124 .\" Generated by docutils manpage writer.
125 .