From 4366fe04f5a6596e687e43b393dc7a908862ffe6 Mon Sep 17 00:00:00 2001
From: bbrucezhang <bbrucezhang@tencent.com>
Date: Wed, 16 Oct 2024 15:09:34 +0800
Subject: [PATCH 1/2] init

---
 README.en.md | 36 ------------------------------------
 README.md    | 39 ---------------------------------------
 hello.py     |  3 +++
 3 files changed, 3 insertions(+), 75 deletions(-)
 delete mode 100644 README.en.md
 delete mode 100644 README.md
 create mode 100644 hello.py

diff --git a/README.en.md b/README.en.md
deleted file mode 100644
index 6787b7f..0000000
--- a/README.en.md
+++ /dev/null
@@ -1,36 +0,0 @@
-# epol-test
-
-#### Description
-{**When you're done, you can delete the content in this README and update the file with details for others getting started with your repository**}
-
-#### Software Architecture
-Software architecture description
-
-#### Installation
-
-1.  xxxx
-2.  xxxx
-3.  xxxx
-
-#### Instructions
-
-1.  xxxx
-2.  xxxx
-3.  xxxx
-
-#### Contribution
-
-1.  Fork the repository
-2.  Create Feat_xxx branch
-3.  Commit your code
-4.  Create Pull Request
-
-
-#### Gitee Feature
-
-1.  You can use Readme\_XXX.md to support different languages, such as Readme\_en.md, Readme\_zh.md
-2.  Gitee blog [blog.gitee.com](https://blog.gitee.com)
-3.  Explore open source project [https://gitee.com/explore](https://gitee.com/explore)
-4.  The most valuable open source project [GVP](https://gitee.com/gvp)
-5.  The manual of Gitee [https://gitee.com/help](https://gitee.com/help)
-6.  The most popular members  [https://gitee.com/gitee-stars/](https://gitee.com/gitee-stars/)
diff --git a/README.md b/README.md
deleted file mode 100644
index ffee57e..0000000
--- a/README.md
+++ /dev/null
@@ -1,39 +0,0 @@
-# epol-test
-
-#### 介绍
-{**以下是 Gitee 平台说明，您可以替换此简介**
-Gitee 是 OSCHINA 推出的基于 Git 的代码托管平台（同时支持 SVN）。专为开发者提供稳定、高效、安全的云端软件开发协作平台
-无论是个人、团队、或是企业，都能够用 Gitee 实现代码托管、项目管理、协作开发。企业项目请看 [https://gitee.com/enterprises](https://gitee.com/enterprises)}
-
-#### 软件架构
-软件架构说明
-
-
-#### 安装教程
-
-1.  xxxx
-2.  xxxx
-3.  xxxx
-
-#### 使用说明
-
-1.  xxxx
-2.  xxxx
-3.  xxxx
-
-#### 参与贡献
-
-1.  Fork 本仓库
-2.  新建 Feat_xxx 分支
-3.  提交代码
-4.  新建 Pull Request
-
-
-#### 特技
-
-1.  使用 Readme\_XXX.md 来支持不同的语言，例如 Readme\_en.md, Readme\_zh.md
-2.  Gitee 官方博客 [blog.gitee.com](https://blog.gitee.com)
-3.  你可以 [https://gitee.com/explore](https://gitee.com/explore) 这个地址来了解 Gitee 上的优秀开源项目
-4.  [GVP](https://gitee.com/gvp) 全称是 Gitee 最有价值开源项目，是综合评定出的优秀开源项目
-5.  Gitee 官方提供的使用手册 [https://gitee.com/help](https://gitee.com/help)
-6.  Gitee 封面人物是一档用来展示 Gitee 会员风采的栏目 [https://gitee.com/gitee-stars/](https://gitee.com/gitee-stars/)
diff --git a/hello.py b/hello.py
new file mode 100644
index 0000000..6df61b5
--- /dev/null
+++ b/hello.py
@@ -0,0 +1,3 @@
+#!/usr/bin/env python3
+
+print("Hola")
-- 
Gitee


From 5187d774495fceaf57545cba099dc02a3366f21e Mon Sep 17 00:00:00 2001
From: bbrucezhang <bbrucezhang@tencent.com>
Date: Fri, 18 Oct 2024 10:53:46 +0800
Subject: [PATCH 2/2] init

---
 ...ash-completion-due-to-sqlite-changes.patch |   25 +
 0002-Protect-dnf.patch                        |   21 +
 5000-default-zchunk-false.patch               |   32 +
 dnf-automatic.8                               |  178 ++
 dnf-transaction-json.5                        |  194 ++
 dnf.8                                         | 2123 +++++++++++++++++
 dnf.conf.5                                    | 1312 ++++++++++
 dnf.modularity.7                              |  125 +
 dnf.spec                                      |  289 +++
 hello.py                                      |    3 -
 sources                                       |    1 +
 yum-aliases.1                                 | 2123 +++++++++++++++++
 yum-shell.8                                   | 2123 +++++++++++++++++
 yum.8                                         | 2123 +++++++++++++++++
 yum.conf.5                                    | 1312 ++++++++++
 yum2dnf.8                                     |  717 ++++++
 16 files changed, 12698 insertions(+), 3 deletions(-)
 create mode 100644 0001-Fix-bash-completion-due-to-sqlite-changes.patch
 create mode 100644 0002-Protect-dnf.patch
 create mode 100644 5000-default-zchunk-false.patch
 create mode 100644 dnf-automatic.8
 create mode 100644 dnf-transaction-json.5
 create mode 100644 dnf.8
 create mode 100644 dnf.conf.5
 create mode 100644 dnf.modularity.7
 create mode 100644 dnf.spec
 delete mode 100644 hello.py
 create mode 100644 sources
 create mode 100644 yum-aliases.1
 create mode 100644 yum-shell.8
 create mode 100644 yum.8
 create mode 100644 yum.conf.5
 create mode 100644 yum2dnf.8

diff --git a/0001-Fix-bash-completion-due-to-sqlite-changes.patch b/0001-Fix-bash-completion-due-to-sqlite-changes.patch
new file mode 100644
index 0000000..afc4ee8
--- /dev/null
+++ b/0001-Fix-bash-completion-due-to-sqlite-changes.patch
@@ -0,0 +1,25 @@
+From 7fb385ca63aedb086a0cd7cacf2106f148bec76d Mon Sep 17 00:00:00 2001
+From: Ze Zhang <bbrucezhang@tencent.com>
+Date: Thu, 1 Feb 2024 20:10:05 +0800
+Subject: [PATCH] Fix bash completion due to sqlite changes
+
+---
+ etc/bash_completion.d/dnf | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/etc/bash_completion.d/dnf b/etc/bash_completion.d/dnf
+index eb34b80..8a9256a 100644
+--- a/etc/bash_completion.d/dnf
++++ b/etc/bash_completion.d/dnf
+@@ -112,7 +112,7 @@ _dnf_query_db()
+ {
+     local table=$1
+     local prefix=$2
+-    local query="select pkg from $table where pkg like \"$prefix%\""
++    local query="select pkg from $table where pkg like '$prefix%'"
+     if [ "$table" = "available" ]; then
+         # The available table contains both installed and non-installed
+         # packages. Exclude the installed packages.
+-- 
+2.41.0
+
diff --git a/0002-Protect-dnf.patch b/0002-Protect-dnf.patch
new file mode 100644
index 0000000..74b1da8
--- /dev/null
+++ b/0002-Protect-dnf.patch
@@ -0,0 +1,21 @@
+From 54c06c52652cb7ac2d85c0d6ad69b448dd1b9734 Mon Sep 17 00:00:00 2001
+From: Ze Zhang <bbrucezhang@tencent.com>
+Date: Thu, 17 Oct 2024 17:04:18 +0800
+Subject: [PATCH] Protect dnf
+
+---
+ etc/dnf/protected.d/dnf.conf | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/etc/dnf/protected.d/dnf.conf b/etc/dnf/protected.d/dnf.conf
+index c2b5885..15b8aa9 100644
+--- a/etc/dnf/protected.d/dnf.conf
++++ b/etc/dnf/protected.d/dnf.conf
+@@ -1,3 +1,3 @@
+ # DNF is obsoleted in Fedora 39 by DNF 5 and should no longer be marked as protected.
+ 
+-# dnf
++dnf
+-- 
+2.41.1
+
diff --git a/5000-default-zchunk-false.patch b/5000-default-zchunk-false.patch
new file mode 100644
index 0000000..6ff4daf
--- /dev/null
+++ b/5000-default-zchunk-false.patch
@@ -0,0 +1,32 @@
+From 8733ed15f14dabf2de0f8c7d37a42257226a996d Mon Sep 17 00:00:00 2001
+From: victorzhong <victorzhong@tencent.com>
+Date: Mon, 19 Sep 2022 16:45:07 +0800
+Subject: [PATCH] default zchunk false
+
+---
+ etc/dnf/dnf-strict.conf | 1 +
+ etc/dnf/dnf.conf        | 2 ++
+ 2 files changed, 3 insertions(+)
+
+diff --git a/etc/dnf/dnf-strict.conf b/etc/dnf/dnf-strict.conf
+index 3d08d07..b211b39 100644
+--- a/etc/dnf/dnf-strict.conf
++++ b/etc/dnf/dnf-strict.conf
+@@ -4,3 +4,4 @@ installonly_limit=3
+ clean_requirements_on_remove=True
+ best=True
+ skip_if_unavailable=False
++zchunk=False
+diff --git a/etc/dnf/dnf.conf b/etc/dnf/dnf.conf
+index 460dd25..899f178 100644
+--- a/etc/dnf/dnf.conf
++++ b/etc/dnf/dnf.conf
+@@ -6,3 +6,5 @@ installonly_limit=3
+ clean_requirements_on_remove=True
+ best=False
+ skip_if_unavailable=True
++zchunk=False
++
+-- 
+2.27.0
+
diff --git a/dnf-automatic.8 b/dnf-automatic.8
new file mode 100644
index 0000000..82cd229
--- /dev/null
+++ b/dnf-automatic.8
@@ -0,0 +1,178 @@
+.\" Man page generated from reStructuredText.
+.
+.
+.nr rst2man-indent-level 0
+.
+.de1 rstReportMargin
+\\$1 \\n[an-margin]
+level \\n[rst2man-indent-level]
+level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
+-
+\\n[rst2man-indent0]
+\\n[rst2man-indent1]
+\\n[rst2man-indent2]
+..
+.de1 INDENT
+.\" .rstReportMargin pre:
+. RS \\$1
+. nr rst2man-indent\\n[rst2man-indent-level] \\n[an-margin]
+. nr rst2man-indent-level +1
+.\" .rstReportMargin post:
+..
+.de UNINDENT
+. RE
+.\" indent \\n[an-margin]
+.\" old: \\n[rst2man-indent\\n[rst2man-indent-level]]
+.nr rst2man-indent-level -1
+.\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
+.in \\n[rst2man-indent\\n[rst2man-indent-level]]u
+..
+.TH "DNF-AUTOMATIC" "8" "Apr 29, 2022" "4.12.0" "DNF"
+.SH NAME
+dnf-automatic \- DNF Automatic
+.SH SYNOPSIS
+.sp
+\fBdnf\-automatic [<config file>]\fP
+.SH DESCRIPTION
+.sp
+Alternative CLI to \fBdnf upgrade\fP with specific facilities to make it suitable to be executed automatically and regularly from systemd timers, cron jobs and similar.
+.sp
+The operation of the tool is usually controlled by the configuration file or the function\-specific timer units (see below). The command only accepts a single optional argument pointing to the config file, and some control arguments intended for use by the services that back the timer units. If no configuration file is passed from the command line, \fB/etc/dnf/automatic.conf\fP is used.
+.sp
+The tool synchronizes package metadata as needed and then checks for updates available for the given system and then either exits, downloads the packages or downloads and applies the packages. The outcome of the operation is then reported by a selected mechanism, for instance via the standard output, email or MOTD messages.
+.sp
+The systemd timer unit \fBdnf\-automatic.timer\fP will behave as the configuration file specifies (see below) with regard to whether to download and apply updates. Some other timer units are provided which override the configuration file with some standard behaviours:
+.INDENT 0.0
+.IP \(bu 2
+dnf\-automatic\-notifyonly
+.IP \(bu 2
+dnf\-automatic\-download
+.IP \(bu 2
+dnf\-automatic\-install
+.UNINDENT
+.sp
+Regardless of the configuration file settings, the first will only notify of available updates. The second will download, but not install them. The third will download and install them.
+.SH RUN DNF-AUTOMATIC
+.sp
+You can select one that most closely fits your needs, customize \fB/etc/dnf/automatic.conf\fP for any specific behaviors, and enable the timer unit.
+.sp
+For example: \fBsystemctl enable \-\-now dnf\-automatic\-notifyonly.timer\fP
+.SH CONFIGURATION FILE FORMAT
+.sp
+The configuration file is separated into topical sections.
+.SS \fB[commands]\fP section
+.sp
+Setting the mode of operation of the program.
+.INDENT 0.0
+.TP
+.B \fBapply_updates\fP
+boolean, default: False
+.sp
+Whether packages comprising the available updates should be applied by \fBdnf\-automatic.timer\fP, i.e. installed via RPM. Implies \fBdownload_updates\fP\&. Note that if this is set to \fBFalse\fP, downloaded packages will be left in the cache till the next successful DNF transaction. Note that the other timer units override this setting.
+.TP
+.B \fBdownload_updates\fP
+boolean, default: False
+.sp
+Whether packages comprising the available updates should be downloaded by \fBdnf\-automatic.timer\fP\&. Note that the other timer units override this setting.
+.TP
+.B \fBnetwork_online_timeout\fP
+time in seconds, default: 60
+.sp
+Maximal time dnf\-automatic will wait until the system is online. 0 means that network availability detection will be skipped.
+.TP
+.B \fBrandom_sleep\fP
+time in seconds, default: 0
+.sp
+Maximal random delay before downloading.  Note that, by default, the \fBsystemd\fP timers also apply a random delay of up to 1 hour.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBupgrade_type\fP
+either one of \fBdefault\fP, \fBsecurity\fP, default: \fBdefault\fP
+.sp
+What kind of upgrades to look at. \fBdefault\fP signals looking for all available updates, \fBsecurity\fP only those with an issued security advisory.
+.UNINDENT
+.SS \fB[emitters]\fP section
+.sp
+Choosing how the results should be reported.
+.INDENT 0.0
+.TP
+.B \fBemit_via\fP
+list, default: \fBemail, stdio, motd\fP
+.sp
+List of emitters to report the results through. Available emitters are \fBstdio\fP to print the result to standard output, \fBcommand\fP to send the result to a custom command, \fBcommand_email\fP to send an email using a command, and \fBemail\fP to send the report via email and \fBmotd\fP sends the result to \fI/etc/motd\fP file.
+.TP
+.B \fBsystem_name\fP
+string, default: hostname of the given system
+.sp
+How the system is called in the reports.
+.UNINDENT
+.SS \fB[command]\fP section
+.sp
+The command emitter configuration. Variables usable in format string arguments are \fBbody\fP with the message body.
+.INDENT 0.0
+.TP
+.B \fBcommand_format\fP
+format string, default: \fBcat\fP
+.sp
+The shell command to execute.
+.TP
+.B \fBstdin_format\fP
+format string, default: \fB{body}\fP
+.sp
+The data to pass to the command on stdin.
+.UNINDENT
+.SS \fB[command_email]\fP section
+.sp
+The command email emitter configuration. Variables usable in format string arguments are \fBbody\fP with message body, \fBsubject\fP with email subject, \fBemail_from\fP with the "From:" address and \fBemail_to\fP with a space\-separated list of recipients.
+.INDENT 0.0
+.TP
+.B \fBcommand_format\fP
+format string, default: \fBmail \-Ssendwait \-s {subject} \-r {email_from} {email_to}\fP
+.sp
+The shell command to execute.
+.TP
+.B \fBemail_from\fP
+string, default: \fBroot\fP
+.sp
+Message\(aqs "From:" address.
+.TP
+.B \fBemail_to\fP
+list, default: \fBroot\fP
+.sp
+List of recipients of the message.
+.TP
+.B \fBstdin_format\fP
+format string, default: \fB{body}\fP
+.sp
+The data to pass to the command on stdin.
+.UNINDENT
+.SS \fB[email]\fP section
+.sp
+The email emitter configuration.
+.INDENT 0.0
+.TP
+.B \fBemail_from\fP
+string, default: \fBroot\fP
+.sp
+Message\(aqs "From:" address.
+.TP
+.B \fBemail_host\fP
+string, default: \fBlocalhost\fP
+.sp
+Hostname of the SMTP server used to send the message.
+.TP
+.B \fBemail_to\fP
+list, default: \fBroot\fP
+.sp
+List of recipients of the message.
+.UNINDENT
+.SS \fB[base]\fP section
+.sp
+Can be used to override settings from DNF\(aqs main configuration file. See conf_ref\&.
+.SH AUTHOR
+See AUTHORS in DNF source distribution.
+.SH COPYRIGHT
+2012-2022, Red Hat, Licensed under GPLv2+
+.\" Generated by docutils manpage writer.
+.
diff --git a/dnf-transaction-json.5 b/dnf-transaction-json.5
new file mode 100644
index 0000000..8003e3a
--- /dev/null
+++ b/dnf-transaction-json.5
@@ -0,0 +1,194 @@
+.\" Man page generated from reStructuredText.
+.
+.
+.nr rst2man-indent-level 0
+.
+.de1 rstReportMargin
+\\$1 \\n[an-margin]
+level \\n[rst2man-indent-level]
+level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
+-
+\\n[rst2man-indent0]
+\\n[rst2man-indent1]
+\\n[rst2man-indent2]
+..
+.de1 INDENT
+.\" .rstReportMargin pre:
+. RS \\$1
+. nr rst2man-indent\\n[rst2man-indent-level] \\n[an-margin]
+. nr rst2man-indent-level +1
+.\" .rstReportMargin post:
+..
+.de UNINDENT
+. RE
+.\" indent \\n[an-margin]
+.\" old: \\n[rst2man-indent\\n[rst2man-indent-level]]
+.nr rst2man-indent-level -1
+.\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
+.in \\n[rst2man-indent\\n[rst2man-indent-level]]u
+..
+.TH "DNF-TRANSACTION-JSON" "5" "Apr 29, 2022" "4.12.0" "DNF"
+.SH NAME
+dnf-transaction-json \- DNF Stored Transaction JSON
+.sp
+The stored transaction format is considered unstable and may change in an
+incompatible way at any time. It will work if the same version of dnf is used
+to store and replay (or between versions as long as it stays the same).
+.SH TOP-LEVEL OBJECT
+.INDENT 0.0
+.TP
+.B \fBversion\fP
+Type: string
+.sp
+The version of the stored transaction format, in the form \fBMAJOR.MINOR\fP\&.
+.sp
+\fBMAJOR\fP version denotes backwards incompatible changes (old dnf won\(aqt work with
+new transaction JSON).
+.sp
+\fBMINOR\fP version denotes extending the format without breaking backwards
+compatibility (old dnf can work with new transaction JSON).
+.TP
+.B \fBrpms\fP
+Type: an array of \fI\%rpm\fP objects
+.sp
+A list of RPM packages in the transaction.
+.TP
+.B \fBgroups\fP
+Type: an array of \fI\%group\fP objects
+.sp
+A list of groups in the transaction.
+.TP
+.B \fBenvironments\fP
+Type: an array of \fI\%group\fP objects
+.sp
+A list of environment groups in the transaction.
+.UNINDENT
+.SH RPM OBJECT
+.INDENT 0.0
+.TP
+.B \fBaction\fP
+Type: string
+.sp
+Possible values: \fBDowngrade, Downgraded, Install, Obsoleted, Reason Change, Reinstall, Reinstalled, Removed, Upgrade, Upgraded\fP
+.sp
+The action performed on the package in the transaction.
+.TP
+.B \fBnevra\fP
+Type: string
+.sp
+\fBNEVRA\fP (\fBname\-epoch:version\-release.arch\fP) of the package.
+.TP
+.B \fBreason\fP
+Type: string
+.sp
+Possible values: \fBdependency, clean, group, unknown, user, weak\-dependency\fP
+.sp
+The reason why the package was pulled into the transaction.
+.TP
+.B \fBrepo_id\fP
+Type: string
+.sp
+The id of the repository this package is coming from. Note repository ids are defined in the local repository configuration and may differ between systems.
+.UNINDENT
+.SH GROUP OBJECT
+.INDENT 0.0
+.TP
+.B \fBaction\fP
+Type: string
+.sp
+Possible values: \fBInstall, Upgrade, Removed\fP
+.sp
+The action performed on the group in the transaction.
+.TP
+.B \fBid\fP
+Type: string
+.sp
+The id of the group.
+.TP
+.B \fBpackage_types\fP
+Type: string
+.sp
+Possible values: \fBconditional, default, mandatory, optional\fP
+.sp
+The types of packages in the group that will be installed. Valid only for
+the \fBInstall\fP action.
+.TP
+.B \fBpackages\fP
+Type: an array of \fI\%group\-package\fP objects
+.sp
+The packages belonging to the group in the transaction.
+.UNINDENT
+.SH ENVIRONMENT OBJECT
+.INDENT 0.0
+.TP
+.B \fBaction\fP
+Type: string
+.sp
+Possible values: \fBInstall, Upgrade, Removed\fP
+.sp
+The action performed on the environment group in the transaction.
+.TP
+.B \fBid\fP
+Type: string
+.sp
+The id of the environment group.
+.TP
+.B \fBpackage_types\fP
+Type: string
+.sp
+Possible values: \fBconditional, default, mandatory, optional\fP
+.sp
+The types of packages in the environment group that will be installed.
+Valid only for the \fBInstall\fP action.
+.TP
+.B \fBgroup\fP
+Type: an array of \fI\%environment\-group\fP objects
+.sp
+The groups belonging to the environment in the transaction.
+.UNINDENT
+.SH GROUP-PACKAGE OBJECT
+.INDENT 0.0
+.TP
+.B \fBinstalled\fP
+Type: boolean
+.sp
+Whether the package is considered installed as part of the group.
+.TP
+.B \fBname\fP
+Type: string
+.sp
+The name of the package.
+.TP
+.B \fBpackage_type\fP
+Type: string
+.sp
+Possible values: \fBconditional, default, mandatory, optional\fP
+.sp
+The type of the package in the group.
+.UNINDENT
+.SH ENVIRONMENT-GROUP OBJECT
+.INDENT 0.0
+.TP
+.B \fBgroup_type\fP
+Type: string
+.sp
+Possible values: \fBmandatory, optional\fP
+.sp
+The type of the group in the environment.
+.TP
+.B \fBid\fP
+Type: string
+.sp
+The id of the group.
+.TP
+.B \fBinstalled\fP
+Type: boolean
+.sp
+Whether the group is considered installed as part of the environment.
+.UNINDENT
+.SH AUTHOR
+See AUTHORS in DNF source distribution.
+.SH COPYRIGHT
+2012-2022, Red Hat, Licensed under GPLv2+
+.\" Generated by docutils manpage writer.
+.
diff --git a/dnf.8 b/dnf.8
new file mode 100644
index 0000000..57f224b
--- /dev/null
+++ b/dnf.8
@@ -0,0 +1,2123 @@
+.\" Man page generated from reStructuredText.
+.
+.
+.nr rst2man-indent-level 0
+.
+.de1 rstReportMargin
+\\$1 \\n[an-margin]
+level \\n[rst2man-indent-level]
+level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
+-
+\\n[rst2man-indent0]
+\\n[rst2man-indent1]
+\\n[rst2man-indent2]
+..
+.de1 INDENT
+.\" .rstReportMargin pre:
+. RS \\$1
+. nr rst2man-indent\\n[rst2man-indent-level] \\n[an-margin]
+. nr rst2man-indent-level +1
+.\" .rstReportMargin post:
+..
+.de UNINDENT
+. RE
+.\" indent \\n[an-margin]
+.\" old: \\n[rst2man-indent\\n[rst2man-indent-level]]
+.nr rst2man-indent-level -1
+.\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
+.in \\n[rst2man-indent\\n[rst2man-indent-level]]u
+..
+.TH "DNF" "8" "Apr 29, 2022" "4.12.0" "DNF"
+.SH NAME
+dnf \- DNF Command Reference
+.SH SYNOPSIS
+.sp
+\fBdnf [options] <command> [<args>...]\fP
+.SH DESCRIPTION
+.sp
+\fI\%DNF\fP is the next upcoming major version of \fI\%YUM\fP, a package manager for RPM\-based Linux
+distributions. It roughly maintains CLI compatibility with YUM and defines a strict API for
+extensions and plugins.
+.sp
+Plugins can modify or extend features of DNF or provide additional CLI commands on top of those
+mentioned below. If you know the name of such a command (including commands mentioned below), you
+may find/install the package which provides it using the appropriate virtual provide in the form of
+\fBdnf\-command(<alias>)\fP, where \fB<alias>\fP is the name of the command; e.g.\(ga\(gadnf install
+\(aqdnf\-command(versionlock)\(aq\(ga\(ga installs a \fBversionlock\fP plugin. This approach also applies to
+specifying dependencies of packages that require a particular DNF command.
+.sp
+Return values:
+.INDENT 0.0
+.IP \(bu 2
+\fB0\fP  : Operation was successful.
+.IP \(bu 2
+\fB1\fP  : An error occurred, which was handled by dnf.
+.IP \(bu 2
+\fB3\fP  : An unknown unhandled error occurred during operation.
+.IP \(bu 2
+\fB100\fP: See \fI\%check\-update\fP
+.IP \(bu 2
+\fB200\fP: There was a problem with acquiring or releasing of locks.
+.UNINDENT
+.sp
+Available commands:
+.INDENT 0.0
+.IP \(bu 2
+\fI\%alias\fP
+.IP \(bu 2
+\fI\%autoremove\fP
+.IP \(bu 2
+\fI\%check\fP
+.IP \(bu 2
+\fI\%check\-update\fP
+.IP \(bu 2
+\fI\%clean\fP
+.IP \(bu 2
+\fI\%deplist\fP
+.IP \(bu 2
+\fI\%distro\-sync\fP
+.IP \(bu 2
+\fI\%downgrade\fP
+.IP \(bu 2
+\fI\%group\fP
+.IP \(bu 2
+\fI\%help\fP
+.IP \(bu 2
+\fI\%history\fP
+.IP \(bu 2
+\fI\%info\fP
+.IP \(bu 2
+\fI\%install\fP
+.IP \(bu 2
+\fI\%list\fP
+.IP \(bu 2
+\fI\%makecache\fP
+.IP \(bu 2
+\fI\%mark\fP
+.IP \(bu 2
+\fI\%module\fP
+.IP \(bu 2
+\fI\%provides\fP
+.IP \(bu 2
+\fI\%reinstall\fP
+.IP \(bu 2
+\fI\%remove\fP
+.IP \(bu 2
+\fI\%repoinfo\fP
+.IP \(bu 2
+\fI\%repolist\fP
+.IP \(bu 2
+\fI\%repoquery\fP
+.IP \(bu 2
+\fI\%repository\-packages\fP
+.IP \(bu 2
+\fI\%search\fP
+.IP \(bu 2
+\fI\%shell\fP
+.IP \(bu 2
+\fI\%swap\fP
+.IP \(bu 2
+\fI\%updateinfo\fP
+.IP \(bu 2
+\fI\%upgrade\fP
+.IP \(bu 2
+\fI\%upgrade\-minimal\fP
+.UNINDENT
+.sp
+Additional information:
+.INDENT 0.0
+.IP \(bu 2
+\fI\%Options\fP
+.IP \(bu 2
+\fI\%Specifying Packages\fP
+.IP \(bu 2
+\fI\%Specifying Provides\fP
+.IP \(bu 2
+\fI\%Specifying File Provides\fP
+.IP \(bu 2
+\fI\%Specifying Groups\fP
+.IP \(bu 2
+\fI\%Specifying Transactions\fP
+.IP \(bu 2
+\fI\%Metadata Synchronization\fP
+.IP \(bu 2
+\fI\%Configuration Files Replacement Policy\fP
+.IP \(bu 2
+\fI\%Files\fP
+.IP \(bu 2
+\fI\%See Also\fP
+.UNINDENT
+.SH OPTIONS
+.INDENT 0.0
+.TP
+.B \fB\-4\fP
+Resolve to IPv4 addresses only.
+.TP
+.B \fB\-6\fP
+Resolve to IPv6 addresses only.
+.TP
+.B \fB\-\-advisory=<advisory>, \-\-advisories=<advisory>\fP
+Include packages corresponding to the advisory ID, Eg. FEDORA\-2201\-123.
+Applicable for the install, repoquery, updateinfo and upgrade commands.
+.TP
+.B \fB\-\-allowerasing\fP
+Allow erasing of installed packages to resolve dependencies. This option could be used as an alternative to the \fByum swap\fP command where packages to remove are not explicitly defined.
+.TP
+.B \fB\-\-assumeno\fP
+Automatically answer no for all questions.
+.TP
+.B \fB\-b, \-\-best\fP
+Try the best available package versions in transactions. Specifically during \fI\%dnf upgrade\fP, which by default skips over updates that can not be installed for dependency reasons, the switch forces DNF to only consider the latest packages. When running into packages with broken dependencies, DNF will fail giving a reason why the latest version can not be installed.
+.sp
+Note that the use of the newest available version is only guaranteed for
+the packages directly requested (e.g. as a command line arguments), and the
+solver may use older versions of dependencies to meet their requirements.
+.TP
+.B \fB\-\-bugfix\fP
+Include packages that fix a bugfix issue. Applicable for the install, repoquery, updateinfo and
+upgrade commands.
+.TP
+.B \fB\-\-bz=<bugzilla>, \-\-bzs=<bugzilla>\fP
+Include packages that fix a Bugzilla ID, Eg. 123123. Applicable for the install, repoquery,
+updateinfo and upgrade commands.
+.TP
+.B \fB\-C, \-\-cacheonly\fP
+Run entirely from system cache, don\(aqt update the cache and use it even in case it is expired.
+.sp
+DNF uses a separate cache for each user under which it executes. The cache for the root user is called the system cache. This switch allows a regular user read\-only access to the system cache, which usually is more fresh than the user\(aqs and thus he does not have to wait for metadata sync.
+.TP
+.B \fB\-\-color=<color>\fP
+Control whether color is used in terminal output. Valid values are \fBalways\fP, \fBnever\fP and \fBauto\fP (default).
+.TP
+.B \fB\-\-comment=<comment>\fP
+Add a comment to the transaction history.
+.TP
+.B \fB\-c <config file>, \-\-config=<config file>\fP
+Configuration file location.
+.TP
+.B \fB\-\-cve=<cves>, \-\-cves=<cves>\fP
+Include packages that fix a CVE (Common Vulnerabilities and Exposures) ID
+(\fI\%http://cve.mitre.org/about/\fP), Eg. CVE\-2201\-0123. Applicable for the install, repoquery, updateinfo,
+and upgrade commands.
+.TP
+.B \fB\-d <debug level>, \-\-debuglevel=<debug level>\fP
+Debugging output level. This is an integer value between 0 (no additional information strings) and 10 (shows all debugging information, even that not understandable to the user), default is 2. Deprecated, use \fB\-v\fP instead.
+.TP
+.B \fB\-\-debugsolver\fP
+Dump data aiding in dependency solver debugging into \fB\&./debugdata\fP\&.
+.UNINDENT
+.sp
+\fB\-\-disableexcludes=[all|main|<repoid>], \-\-disableexcludepkgs=[all|main|<repoid>]\fP
+.INDENT 0.0
+.INDENT 3.5
+Disable the configuration file excludes. Takes one of the following three options:
+.INDENT 0.0
+.IP \(bu 2
+\fBall\fP, disables all configuration file excludes
+.IP \(bu 2
+\fBmain\fP, disables excludes defined in the \fB[main]\fP section
+.IP \(bu 2
+\fBrepoid\fP, disables excludes defined for the given repository
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-disable, \-\-set\-disabled\fP
+Disable specified repositories (automatically saves). The option has to be used together with the
+\fBconfig\-manager\fP command (dnf\-plugins\-core).
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-disableplugin=<plugin names>\fP
+Disable the listed plugins specified by names or globs.
+.TP
+.B \fB\-\-disablerepo=<repoid>\fP
+Temporarily disable active repositories for the purpose of the current dnf command.
+Accepts an id, a comma\-separated list of ids, or a glob of ids. This option can be
+specified multiple times, but is mutually exclusive with \fB\-\-repo\fP\&.
+.TP
+.B \fB\-\-downloaddir=<path>, \-\-destdir=<path>\fP
+Redirect downloaded packages to provided directory. The option has to be used together with the \-\fI\%\-downloadonly\fP command line option, with the
+\fBdownload\fP, \fBmodulesync\fP or \fBreposync\fP commands (dnf\-plugins\-core) or with the \fBsystem\-upgrade\fP command
+(dnf\-plugins\-extras).
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-downloadonly\fP
+Download the resolved package set without performing any rpm transaction (install/upgrade/erase).
+.TP
+.B \fB\-e <error level>, \-\-errorlevel=<error level>\fP
+Error output level. This is an integer value between 0 (no error output) and
+10 (shows all error messages), default is 3. Deprecated, use \fB\-v\fP instead.
+.TP
+.B \fB\-\-enable, \-\-set\-enabled\fP
+Enable specified repositories (automatically saves). The option has to be used together with the
+\fBconfig\-manager\fP command (dnf\-plugins\-core).
+.TP
+.B \fB\-\-enableplugin=<plugin names>\fP
+Enable the listed plugins specified by names or globs.
+.TP
+.B \fB\-\-enablerepo=<repoid>\fP
+Temporarily enable additional repositories for the purpose of the current dnf command.
+Accepts an id, a comma\-separated list of ids, or a glob of ids. This option can be
+specified multiple times.
+.TP
+.B \fB\-\-enhancement\fP
+Include enhancement relevant packages. Applicable for the install, repoquery, updateinfo and
+upgrade commands.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-x <package\-file\-spec>, \-\-exclude=<package\-file\-spec>\fP
+Exclude packages specified by \fB<package\-file\-spec>\fP from the operation.
+.TP
+.B \fB\-\-excludepkgs=<package\-file\-spec>\fP
+Deprecated option. It was replaced by the \-\fI\%\-exclude\fP option.
+.TP
+.B \fB\-\-forcearch=<arch>\fP
+Force the use of an architecture. Any architecture can be specified.
+However, use of an architecture not supported natively by your CPU will
+require emulation of some kind. This is usually through QEMU. The behavior of \fB\-\-forcearch\fP
+can be configured by using the arch and ignorearch
+configuration options with values \fB<arch>\fP and \fBTrue\fP respectively.
+.TP
+.B \fB\-h, \-\-help, \-\-help\-cmd\fP
+Show the help.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-installroot=<path>\fP
+Specifies an alternative installroot, relative to where all packages will be
+installed. Think of this like doing \fBchroot <root> dnf\fP, except using
+\fB\-\-installroot\fP allows dnf to work before the chroot is created. It requires absolute path.
+.UNINDENT
+.INDENT 0.0
+.IP \(bu 2
+\fIcachedir\fP, \fIlog files\fP, \fIreleasever\fP, and \fIgpgkey\fP are taken from or
+stored in the installroot. \fIGpgkeys\fP are imported into the installroot from
+a path relative to the host which can be specified in the repository section
+of configuration files.
+.IP \(bu 2
+\fIconfiguration file\fP and reposdir are searched inside the installroot first. If
+they are not present, they are taken from the host system.
+Note:  When a path is specified within a command line argument
+(\fB\-\-config=<config file>\fP in case of \fIconfiguration file\fP and
+\fB\-\-setopt=reposdir=<reposdir>\fP for \fIreposdir\fP) then this path is always
+relative to the host with no exceptions.
+.IP \(bu 2
+\fIvars\fP are taken from the host system or installroot according to reposdir
+\&. When \fIreposdir\fP path is specified within a command line argument, vars are taken from the
+installroot. When varsdir paths are specified within a command line
+argument (\fB\-\-setopt=varsdir=<reposdir>\fP) then those path are always relative to the host with no
+exceptions.
+.IP \(bu 2
+The \fIpluginpath\fP and \fIpluginconfpath\fP are relative to the host.
+.UNINDENT
+.INDENT 0.0
+.INDENT 3.5
+Note: You may also want to use the command\-line option
+\fB\-\-releasever=<release>\fP when creating the installroot, otherwise the
+\fI$releasever\fP value is taken from the rpmdb within the installroot (and thus
+it is empty at the time of creation and the transaction will fail). If \fB\-\-releasever=/\fP is used, the
+releasever will be detected from the host (\fB/\fP) system. The new installroot path at the time of creation
+does not contain the \fIrepository\fP, \fIreleasever\fP and \fIdnf.conf\fP files.
+.sp
+On a modular system you may also want to use the
+\fB\-\-setopt=module_platform_id=<module_platform_name:stream>\fP command\-line option when creating the installroot,
+otherwise the module_platform_id value will be taken from the
+\fB/etc/os\-release\fP file within the installroot (and thus it will be empty at the time of creation, the modular
+dependency could be unsatisfied and modules content could be excluded).
+.sp
+Installroot examples:
+.INDENT 0.0
+.TP
+.B \fBdnf \-\-installroot=<installroot> \-\-releasever=<release> install system\-release\fP
+Permanently sets the \fBreleasever\fP of the system in the
+\fB<installroot>\fP directory to \fB<release>\fP\&.
+.TP
+.B \fBdnf \-\-installroot=<installroot> \-\-setopt=reposdir=<path> \-\-config /path/dnf.conf upgrade\fP
+Upgrades packages inside the installroot from a repository described by
+\fB\-\-setopt\fP using configuration from \fB/path/dnf.conf\fP\&.
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-newpackage\fP
+Include newpackage relevant packages. Applicable for the install, repoquery, updateinfo and
+upgrade commands.
+.TP
+.B \fB\-\-noautoremove\fP
+Disable removal of dependencies that are no longer used. It sets
+clean_requirements_on_remove configuration option to \fBFalse\fP\&.
+.TP
+.B \fB\-\-nobest\fP
+Set best option to \fBFalse\fP, so that transactions are not limited to best candidates only.
+.TP
+.B \fB\-\-nodocs\fP
+Do not install documentation. Sets the rpm flag \(aqRPMTRANS_FLAG_NODOCS\(aq.
+.TP
+.B \fB\-\-nogpgcheck\fP
+Skip checking GPG signatures on packages (if RPM policy allows).
+.TP
+.B \fB\-\-noplugins\fP
+Disable all plugins.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-obsoletes\fP
+This option has an effect on an install/update, it enables
+dnf\(aqs obsoletes processing logic. For more information see the
+obsoletes option.
+.sp
+This option also displays capabilities that the package obsoletes when used together with the \fI\%repoquery\fP command.
+.sp
+Configuration Option: obsoletes
+.TP
+.B \fB\-q, \-\-quiet\fP
+In combination with a non\-interactive command, shows just the relevant content. Suppresses messages notifying about the current state or actions of DNF.
+.TP
+.B \fB\-R <minutes>, \-\-randomwait=<minutes>\fP
+Maximum command wait time.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-refresh\fP
+Set metadata as expired before running the command.
+.TP
+.B \fB\-\-releasever=<release>\fP
+Configure DNF as if the distribution release was \fB<release>\fP\&. This can
+affect cache paths, values in configuration files and mirrorlist URLs.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-repofrompath <repo>,<path/url>\fP
+Specify a repository to add to the repositories for this query.
+This option can be used multiple times.
+.UNINDENT
+.INDENT 0.0
+.IP \(bu 2
+The repository label is specified by \fB<repo>\fP\&.
+.IP \(bu 2
+The path or url to the repository is specified by \fB<path/url>\fP\&.
+It is the same path as a baseurl and can be also enriched by the
+repo variables\&.
+.IP \(bu 2
+The configuration for the repository can be adjusted using \-\fI\%\-setopt\fP=<repo>.<option>=<value>.
+.IP \(bu 2
+If you want to view only packages from this repository, combine this
+with the \fB\-\-repo=<repo>\fP or \fB\-\-disablerepo="*"\fP switches.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-repo=<repoid>, \-\-repoid=<repoid>\fP
+Enable just specific repositories by an id or a glob. Can be used multiple
+times with accumulative effect. It is basically a shortcut for
+\fB\-\-disablerepo="*" \-\-enablerepo=<repoid>\fP and is mutually exclusive with
+the \fB\-\-disablerepo\fP option.
+.TP
+.B \fB\-\-rpmverbosity=<name>\fP
+RPM debug scriptlet output level. Sets the debug level to \fB<name>\fP for RPM scriptlets.
+For available levels, see the \fBrpmverbosity\fP configuration option.
+.TP
+.B \fB\-\-sec\-severity=<severity>, \-\-secseverity=<severity>\fP
+Includes packages that provide a fix for an issue of the specified severity.
+Applicable for the install, repoquery, updateinfo and upgrade commands.
+.TP
+.B \fB\-\-security\fP
+Includes packages that provide a fix for a security issue. Applicable for the
+upgrade command.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-setopt=<option>=<value>\fP
+Override a configuration option from the configuration file. To override configuration options for repositories, use
+\fBrepoid.option\fP for the \fB<option>\fP\&. Values for configuration options like \fBexcludepkgs\fP, \fBincludepkgs\fP,
+\fBinstallonlypkgs\fP and \fBtsflags\fP are appended to the original value, they do not override it. However, specifying
+an empty value (e.g. \fB\-\-setopt=tsflags=\fP) will clear the option.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-skip\-broken\fP
+Resolve depsolve problems by removing packages that are causing problems from the transaction.
+It is an alias for the strict configuration option with value \fBFalse\fP\&.
+Additionally, with the \fI\%enable\fP and
+\fI\%disable\fP module subcommands it allows one to perform an action even in case of
+broken modular dependencies.
+.TP
+.B \fB\-\-showduplicates\fP
+Show duplicate packages in repositories. Applicable for the list and search commands.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-v, \-\-verbose\fP
+Verbose operation, show debug messages.
+.TP
+.B \fB\-\-version\fP
+Show DNF version and exit.
+.TP
+.B \fB\-y, \-\-assumeyes\fP
+Automatically answer yes for all questions.
+.UNINDENT
+.sp
+List options are comma\-separated. Command\-line options override respective settings from configuration files.
+.SH COMMANDS
+.sp
+For an explanation of \fB<package\-spec>\fP, \fB<package\-file\-spec>\fP and \fB<package\-name\-spec>\fP see
+\fI\%Specifying Packages\fP\&.
+.sp
+For an explanation of \fB<provide\-spec>\fP see \fI\%Specifying Provides\fP\&.
+.sp
+For an explanation of \fB<group\-spec>\fP see \fI\%Specifying Groups\fP\&.
+.sp
+For an explanation of \fB<module\-spec>\fP see \fI\%Specifying Modules\fP\&.
+.sp
+For an explanation of \fB<transaction\-spec>\fP see \fI\%Specifying Transactions\fP\&.
+.SS Alias Command
+.nf
+Command: \fBalias\fP
+.fi
+.sp
+.sp
+Allows the user to define and manage a list of aliases (in the form \fB<name=value>\fP),
+which can be then used as dnf commands to abbreviate longer command sequences. For examples on using
+the alias command, see \fI\%Alias Examples\fP\&. For examples on the alias
+processing, see \fI\%Alias Processing Examples\fP\&.
+.sp
+To use an alias (name=value), the name must be placed as the first "command" (e.g. the first argument
+that is not an option). It is then replaced by its value and the resulting sequence is again searched
+for aliases. The alias processing stops when the first found command is not a name of any alias.
+.sp
+In case the processing would result in an infinite recursion, the original arguments are used instead.
+.sp
+Also, like in shell aliases, if the result starts with a \fB\e\fP, the alias processing will stop.
+.sp
+All aliases are defined in configuration files in the \fB/etc/dnf/aliases.d/\fP directory in the [aliases] section,
+and aliases created by the alias command are written to the \fBUSER.conf\fP file. In case of conflicts,
+the \fBUSER.conf\fP has the highest priority, and alphabetical ordering is used for the rest of the
+configuration files.
+.sp
+Optionally, there is the \fBenabled\fP option in the \fB[main]\fP section defaulting to True. This can be set for each
+file separately in the respective file, or globally for all aliases in the \fBALIASES.conf\fP file.
+.sp
+\fBdnf alias [options] [list] [<name>...]\fP
+.INDENT 0.0
+.INDENT 3.5
+List aliases with their final result. The \fB[<alias>...]\fP parameter further limits the result to only those aliases matching it.
+.UNINDENT
+.UNINDENT
+.sp
+\fBdnf alias [options] add <name=value>...\fP
+.INDENT 0.0
+.INDENT 3.5
+Create new aliases.
+.UNINDENT
+.UNINDENT
+.sp
+\fBdnf alias [options] delete <name>...\fP
+.INDENT 0.0
+.INDENT 3.5
+Delete aliases.
+.UNINDENT
+.UNINDENT
+.SS Alias Examples
+.INDENT 0.0
+.TP
+.B \fBdnf alias list\fP
+Lists all defined aliases.
+.TP
+.B \fBdnf alias add rm=remove\fP
+Adds a new command alias called \fBrm\fP which works the same as the \fBremove\fP command.
+.TP
+.B \fBdnf alias add upgrade="\eupgrade \-\-skip\-broken \-\-disableexcludes=all \-\-obsoletes"\fP
+Adds a new command alias called \fBupgrade\fP which works the same as the \fBupgrade\fP command,
+with additional options. Note that the original \fBupgrade\fP command is prefixed with a \fB\e\fP
+to prevent an infinite loop in alias processing.
+.UNINDENT
+.SS Alias Processing Examples
+.sp
+If there are defined aliases \fBin=install\fP and \fBFORCE="\-\-skip\-broken \-\-disableexcludes=all"\fP:
+.INDENT 0.0
+.IP \(bu 2
+\fBdnf FORCE in\fP will be replaced with \fBdnf \-\-skip\-broken \-\-disableexcludes=all install\fP
+.IP \(bu 2
+\fBdnf in FORCE\fP will be replaced with \fBdnf install FORCE\fP (which will fail)
+.UNINDENT
+.sp
+If there is defined alias \fBin=install\fP:
+.INDENT 0.0
+.IP \(bu 2
+\fBdnf in\fP will be replaced with \fBdnf install\fP
+.IP \(bu 2
+\fBdnf \-\-repo updates in\fP will be replaced with \fBdnf \-\-repo updates in\fP (which will fail)
+.UNINDENT
+.SS Autoremove Command
+.nf
+Command: \fBautoremove\fP
+Aliases for \fI\%explicit NEVRA matching\fP: \fBautoremove\-n\fP, \fBautoremove\-na\fP, \fBautoremove\-nevra\fP
+.fi
+.sp
+.sp
+\fBdnf [options] autoremove\fP
+.INDENT 0.0
+.INDENT 3.5
+Removes all "leaf" packages from the system that were originally installed as dependencies of user\-installed packages, but which are no longer required by any such package.
+.UNINDENT
+.UNINDENT
+.sp
+Packages listed in installonlypkgs are never automatically removed by
+this command.
+.sp
+\fBdnf [options] autoremove <spec>...\fP
+.INDENT 0.0
+.INDENT 3.5
+This is an alias for the \fI\%Remove Command\fP command with clean_requirements_on_remove set to
+\fBTrue\fP\&. It removes the specified packages from the system along with any packages depending on the
+packages being removed. Each \fB<spec>\fP can be either a \fB<package\-spec>\fP, which specifies a
+package directly, or a \fB@<group\-spec>\fP, which specifies an (environment) group which contains
+it. It also removes any dependencies that are no longer needed.
+.sp
+There are also a few specific autoremove commands \fBautoremove\-n\fP, \fBautoremove\-na\fP and
+\fBautoremove\-nevra\fP that allow the specification of an exact argument in the NEVRA
+(name\-epoch:version\-release.architecture) format.
+.UNINDENT
+.UNINDENT
+.sp
+This command by default does not force a sync of expired metadata. See also \fI\%Metadata Synchronization\fP\&.
+.SS Check Command
+.nf
+Command: \fBcheck\fP
+.fi
+.sp
+.sp
+\fBdnf [options] check [\-\-dependencies] [\-\-duplicates] [\-\-obsoleted] [\-\-provides]\fP
+.INDENT 0.0
+.INDENT 3.5
+Checks the local packagedb and produces information on any problems it
+finds. You can limit the checks to be performed by using the \fB\-\-dependencies\fP,
+\fB\-\-duplicates\fP, \fB\-\-obsoleted\fP and \fB\-\-provides\fP options (the default is to
+check everything).
+.UNINDENT
+.UNINDENT
+.SS Check\-Update Command
+.nf
+Command: \fBcheck\-update\fP
+Aliases: \fBcheck\-upgrade\fP
+.fi
+.sp
+.sp
+\fBdnf [options] check\-update [\-\-changelogs] [<package\-file\-spec>...]\fP
+.INDENT 0.0
+.INDENT 3.5
+Non\-interactively checks if updates of the specified packages are available. If no \fB<package\-file\-spec>\fP is given, checks whether any updates at all are available for your system. DNF exit code will be 100 when there are updates available and a list of the updates will be printed, 0 if not and 1 if an error occurs. If \fB\-\-changelogs\fP option is specified, also changelog delta of packages about to be updated is printed.
+.sp
+Please note that having a specific newer version available for an installed package (and reported by \fBcheck\-update\fP) does not imply that subsequent \fBdnf upgrade\fP will install it. The difference is that \fBdnf upgrade\fP has restrictions (like package dependencies being satisfied) to take into account.
+.sp
+The output is affected by the autocheck_running_kernel configuration option.
+.UNINDENT
+.UNINDENT
+.SS Clean Command
+.nf
+Command: \fBclean\fP
+.fi
+.sp
+.sp
+Performs cleanup of temporary files kept for repositories. This includes any
+such data left behind from disabled or removed repositories as well as for
+different distribution release versions.
+.INDENT 0.0
+.TP
+.B \fBdnf clean dbcache\fP
+Removes cache files generated from the repository metadata. This forces DNF
+to regenerate the cache files the next time it is run.
+.TP
+.B \fBdnf clean expire\-cache\fP
+Marks the repository metadata expired. DNF will re\-validate the cache for
+each repository the next time it is used.
+.TP
+.B \fBdnf clean metadata\fP
+Removes repository metadata. Those are the files which DNF uses to determine
+the remote availability of packages. Using this option will make DNF
+download all the metadata the next time it is run.
+.TP
+.B \fBdnf clean packages\fP
+Removes any cached packages from the system.
+.TP
+.B \fBdnf clean all\fP
+Does all of the above.
+.UNINDENT
+.SS Deplist Command
+.INDENT 0.0
+.TP
+.B \fBdnf [options] deplist [<select\-options>] [<query\-options>] [<package\-spec>]\fP
+Deprecated alias for \fI\%dnf repoquery \-\-deplist\fP\&.
+.UNINDENT
+.SS Distro\-Sync Command
+.nf
+Command: \fBdistro\-sync\fP
+Aliases: \fBdsync\fP
+Deprecated aliases: \fBdistrosync\fP, \fBdistribution\-synchronization\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf distro\-sync [<package\-spec>...]\fP
+As necessary upgrades, downgrades or keeps selected installed packages to match
+the latest version available from any enabled repository. If no package is given, all installed packages are considered.
+.sp
+See also \fI\%Configuration Files Replacement Policy\fP\&.
+.UNINDENT
+.SS Downgrade Command
+.nf
+Command: \fBdowngrade\fP
+Aliases: \fBdg\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] downgrade <package\-spec>...\fP
+Downgrades the specified packages to the highest installable package of all known lower versions
+if possible. When version is given and is lower than version of installed package then it
+downgrades to target version.
+.UNINDENT
+.SS Group Command
+.nf
+Command: \fBgroup\fP
+Aliases: \fBgrp\fP
+Deprecated aliases: \fBgroups\fP, \fBgrouplist\fP, \fBgroupinstall\fP, \fBgroupupdate\fP, \fBgroupremove\fP, \fBgrouperase\fP, \fBgroupinfo\fP
+.fi
+.sp
+.sp
+Groups are virtual collections of packages. DNF keeps track of groups that the user selected ("marked") installed and can manipulate the comprising packages with simple commands.
+.INDENT 0.0
+.TP
+.B \fBdnf [options] group [summary] <group\-spec>\fP
+Display overview of how many groups are installed and available. With a
+spec, limit the output to the matching groups. \fBsummary\fP is the default
+groups subcommand.
+.TP
+.B \fBdnf [options] group info <group\-spec>\fP
+Display package lists of a group. Shows which packages are installed or
+available from a repository when \fB\-v\fP is used.
+.TP
+.B \fBdnf [options] group install [\-\-with\-optional] <group\-spec>...\fP
+Mark the specified group installed and install packages it contains. Also
+include \fIoptional\fP packages of the group if \fB\-\-with\-optional\fP is
+specified. All \fImandatory\fP and \fIDefault\fP packages will be installed whenever possible.
+Conditional packages are installed if they meet their requirement.
+If the group is already (partially) installed, the command installs the missing packages from the group.
+Depending on the value of obsoletes configuration option group installation takes obsoletes into account.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdnf [options] group list <group\-spec>...\fP
+List all matching groups, either among installed or available groups. If
+nothing is specified, list all known groups. \fB\-\-installed\fP and \fB\-\-available\fP options narrow down the requested list.
+Records are ordered by the \fIdisplay_order\fP tag defined in comps.xml file.
+Provides a list of all hidden groups by using option \fB\-\-hidden\fP\&.
+Provides group IDs when the \fB\-v\fP or \fB\-\-ids\fP options are used.
+.TP
+.B \fBdnf [options] group remove <group\-spec>...\fP
+Mark the group removed and remove those packages in the group from the system which do not belong to another installed group and were not installed explicitly by the user.
+.TP
+.B \fBdnf [options] group upgrade <group\-spec>...\fP
+Upgrades the packages from the group and upgrades the group itself. The latter comprises of installing packages that were added to the group by the distribution and removing packages that got removed from the group as far as they were not installed explicitly by the user.
+.UNINDENT
+.sp
+Groups can also be marked installed or removed without physically manipulating any packages:
+.INDENT 0.0
+.TP
+.B \fBdnf [options] group mark install <group\-spec>...\fP
+Mark the specified group installed. No packages will be installed by this command, but the group is then considered installed.
+.TP
+.B \fBdnf [options] group mark remove <group\-spec>...\fP
+Mark the specified group removed. No packages will be removed by this command.
+.UNINDENT
+.sp
+See also \fI\%Configuration Files Replacement Policy\fP\&.
+.SS Help Command
+.nf
+Command: \fBhelp\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf help [<command>]\fP
+Displays the help text for all commands. If given a command name then only
+displays help for that particular command.
+.UNINDENT
+.SS History Command
+.nf
+Command: \fBhistory\fP
+Aliases: \fBhist\fP
+.fi
+.sp
+.sp
+The history command allows the user to view what has happened in past
+transactions and act according to this information (assuming the
+\fBhistory_record\fP configuration option is set).
+.INDENT 0.0
+.TP
+.B \fBdnf history [list] [\-\-reverse] [<spec>...]\fP
+The default history action is listing information about given transactions
+in a table. Each \fB<spec>\fP can be either a \fB<transaction\-spec>\fP, which
+specifies a transaction directly, or a \fB<transaction\-spec>..<transaction\-spec>\fP,
+which specifies a range of transactions, or a \fB<package\-name\-spec>\fP,
+which specifies a transaction by a package which it manipulated. When no
+transaction is specified, list all known transactions.
+.INDENT 7.0
+.TP
+.B \fB\-\-reverse\fP
+The order of \fBhistory list\fP output is printed in reverse order.
+.UNINDENT
+.TP
+.B \fBdnf history info [<spec>...]\fP
+Describe the given transactions. The meaning of \fB<spec>\fP is the same as
+in the \fI\%History List Command\fP\&. When no
+transaction is specified, describe what happened during the latest
+transaction.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdnf history redo <transaction\-spec>|<package\-file\-spec>\fP
+Repeat the specified transaction. Uses the last transaction (with the highest ID)
+if more than one transaction for given <package\-file\-spec> is found. If it is not possible
+to redo some operations due to the current state of RPMDB, it will not redo the transaction.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdnf history replay [\-\-ignore\-installed] [\-\-ignore\-extras] [\-\-skip\-unavailable] <filename>\fP
+Replay a transaction stored in file \fB<filename>\fP by \fI\%History Store
+Command\fP\&. The replay will perform the exact
+same operations on the packages as in the original transaction and will
+return with an error if case of any differences in installed packages or
+their versions. See also the Transaction JSON Format specification of the
+file format.
+.INDENT 7.0
+.TP
+.B \fB\-\-ignore\-installed\fP
+Don\(aqt check for the installed packages being in the same state as those
+recorded in the transaction. E.g. in case there is an upgrade
+\fBfoo\-1.0\fP \-> \fBfoo\-2.0\fP stored in the transaction, but there is
+\fBfoo\-1.1\fP installed on the target system.
+.TP
+.B \fB\-\-ignore\-extras\fP
+Don\(aqt check for extra packages pulled into the transaction on the
+target system. E.g. the target system may not have some dependency,
+which was installed on the source system. The replay errors out on this
+by default, as the transaction would not be the same.
+.TP
+.B \fB\-\-skip\-unavailable\fP
+In case some packages stored in the transaction are not available on
+the target system, skip them instead of erroring out.
+.UNINDENT
+.TP
+.B \fBdnf history rollback <transaction\-spec>|<package\-file\-spec>\fP
+Undo all transactions performed after the specified transaction. Uses the last transaction
+(with the highest ID) if more than one transaction for given <package\-file\-spec> is found.
+If it is not possible to undo some transactions due to the current state of RPMDB, it will not undo
+any transaction.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdnf history store [\-\-output <output\-file>] <transaction\-spec>\fP
+Store a transaction specified by \fB<transaction\-spec>\fP\&. The transaction
+can later be replayed by the \fI\%History Replay Command\fP\&.
+.sp
+Warning: The stored transaction format is considered unstable and may
+change at any time. It will work if the same version of dnf is used to
+store and replay (or between versions as long as it stays the same).
+.sp
+\fB\-o <output\-file>, \-\-output=<output\-file>\fP
+Store the serialized transaction into \fB<output\-file\fP\&. Default is \fBtransaction.json\fP\&.
+.TP
+.B \fBdnf history undo <transaction\-spec>|<package\-file\-spec>\fP
+Perform the opposite operation to all operations performed in the specified transaction.
+Uses the last transaction (with the highest ID) if more than one transaction for given
+<package\-file\-spec> is found. If it is not possible to undo some operations due to
+the current state of RPMDB, it will not undo the transaction.
+.TP
+.B \fBdnf history userinstalled\fP
+Show all installonly packages, packages installed outside of DNF and packages not
+installed as dependency. I.e. it lists packages that will stay on the system when
+\fI\%Autoremove Command\fP or \fI\%Remove Command\fP along with
+\fIclean_requirements_on_remove\fP configuration option set to True is executed. Note the same
+results can be accomplished with \fBdnf repoquery \-\-userinstalled\fP, and the repoquery
+command is more powerful in formatting of the output.
+.UNINDENT
+.sp
+This command by default does not force a sync of expired metadata, except for
+the redo, rollback, and undo subcommands.
+See also \fI\%Metadata Synchronization\fP
+and \fI\%Configuration Files Replacement Policy\fP\&.
+.SS Info Command
+.nf
+Command: \fBinfo\fP
+Aliases: \fBif\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] info [<package\-file\-spec>...]\fP
+Lists description and summary information about installed and available packages.
+.UNINDENT
+.sp
+The info command limits the displayed packages the same way as the \fI\%list command\fP\&.
+.sp
+This command by default does not force a sync of expired metadata. See also \fI\%Metadata Synchronization\fP\&.
+.SS Install Command
+.nf
+Command: \fBinstall\fP
+Aliases: \fBin\fP
+Aliases for \fI\%explicit NEVRA matching\fP: \fBinstall\-n\fP, \fBinstall\-na\fP, \fBinstall\-nevra\fP
+Deprecated aliases: \fBlocalinstall\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] install <spec>...\fP
+Makes sure that the given packages and their dependencies are installed
+on the system. Each \fB<spec>\fP can be either a \fI\%<package\-spec>\fP,
+or a @\fI\%<module\-spec>\fP, or a @\fI\%<group\-spec>\fP\&.
+See \fI\%Install Examples\fP\&.
+If a given package or provide cannot be (and is not already) installed,
+the exit code will be non\-zero.
+If the \fB<spec>\fP matches both a @\fI\%<module\-spec>\fP and
+a @\fI\%<group\-spec>\fP, only the module is installed.
+.sp
+When \fI\%<package\-spec>\fP to specify the exact version
+of the package is given, DNF will install the desired version, no matter which
+version of the package is already installed. The former version of the package
+will be removed in the case of non\-installonly package.
+.sp
+On the other hand if \fI\%<package\-spec>\fP specifies only a name,
+DNF also takes into account packages obsoleting it when picking which package to install.
+This behaviour is specific to the install command.
+Note that this can lead to seemingly unexpected results if a package has multiple versions and
+some older version is being obsoleted. It creates a split in the upgrade\-path and both ways
+are considered correct, the resulting package is picked simply by lexicographical order.
+.sp
+There are also a few specific install commands \fBinstall\-n\fP, \fBinstall\-na\fP and
+\fBinstall\-nevra\fP that allow the specification of an exact argument in the NEVRA format.
+.sp
+See also \fI\%Configuration Files Replacement Policy\fP\&.
+.UNINDENT
+.SS Install Examples
+.INDENT 0.0
+.TP
+.B \fBdnf install tito\fP
+Install the \fBtito\fP package (tito is the package name).
+.TP
+.B \fBdnf install ~/Downloads/tito\-0.6.2\-1.fc22.noarch.rpm\fP
+Install a local rpm file tito\-0.6.2\-1.fc22.noarch.rpm from the ~/Downloads/
+directory.
+.TP
+.B \fBdnf install tito\-0.5.6\-1.fc22\fP
+Install the package with a specific version. If the package is already installed it
+will automatically try to downgrade or upgrade to the specific version.
+.TP
+.B \fBdnf \-\-best install tito\fP
+Install the latest available version of the package. If the package is already installed it
+will try to automatically upgrade to the latest version. If the latest version
+of the package cannot be installed, the installation will fail.
+.TP
+.B \fBdnf install vim\fP
+DNF will automatically recognize that vim is not a package name, but
+will look up and install a package that provides vim with all the required
+dependencies. Note: Package name match has precedence over package provides
+match.
+.TP
+.B \fBdnf install https://kojipkgs.fedoraproject.org//packages/tito/0.6.0/1.fc22/noarch/tito\-0.6.0\-1.fc22.noarch.rpm\fP
+Install a package directly from a URL.
+.TP
+.B \fBdnf install \(aq@docker\(aq\fP
+Install all default profiles of module \(aqdocker\(aq and their RPMs. Module streams get enabled accordingly.
+.TP
+.B \fBdnf install \(aq@Web Server\(aq\fP
+Install the \(aqWeb Server\(aq environmental group.
+.TP
+.B \fBdnf install /usr/bin/rpmsign\fP
+Install a package that provides the /usr/bin/rpmsign file.
+.TP
+.B \fBdnf \-y install tito \-\-setopt=install_weak_deps=False\fP
+Install the \fBtito\fP package (tito is the package name) without weak deps. Weak deps are not required for
+core functionality of the package, but they enhance the original package (like extended
+documentation, plugins, additional functions, etc.).
+.TP
+.B \fBdnf install \-\-advisory=FEDORA\-2018\-b7b99fe852 \e*\fP
+Install all packages that belong to the "FEDORA\-2018\-b7b99fe852" advisory.
+.UNINDENT
+.SS List Command
+.nf
+Command: \fBlist\fP
+Aliases: \fBls\fP
+.fi
+.sp
+.sp
+Prints lists of packages depending on the packages\(aq relation to the
+system. A package is \fBinstalled\fP if it is present in the RPMDB, and it is \fBavailable\fP
+if it is not installed but is present in a repository that DNF knows about.
+.sp
+The list command also limits the displayed packages according to specific criteria,
+e.g. to only those that update an installed package (respecting the repository
+priority). The exclude option in the configuration file can influence the
+result, but if the \-\fI\%\-disableexcludes\fP command line
+option is used, it ensures that all installed packages will be listed.
+.INDENT 0.0
+.TP
+.B \fBdnf [options] list [\-\-all] [<package\-file\-spec>...]\fP
+Lists all packages, present in the RPMDB, in a repository or both.
+.TP
+.B \fBdnf [options] list \-\-installed [<package\-file\-spec>...]\fP
+Lists installed packages.
+.TP
+.B \fBdnf [options] list \-\-available [<package\-file\-spec>...]\fP
+Lists available packages.
+.TP
+.B \fBdnf [options] list \-\-extras [<package\-file\-spec>...]\fP
+Lists extras, that is packages installed on the system that are not
+available in any known repository.
+.TP
+.B \fBdnf [options] list \-\-obsoletes [<package\-file\-spec>...]\fP
+List packages installed on the system that are obsoleted by packages in
+any known repository.
+.TP
+.B \fBdnf [options] list \-\-recent [<package\-file\-spec>...]\fP
+List packages recently added into the repositories.
+.TP
+.B \fBdnf [options] list \-\-upgrades [<package\-file\-spec>...]\fP
+List upgrades available for the installed packages.
+.TP
+.B \fBdnf [options] list \-\-autoremove\fP
+List packages which will be removed by the \fBdnf autoremove\fP command.
+.UNINDENT
+.sp
+This command by default does not force a sync of expired metadata. See also \fI\%Metadata Synchronization\fP\&.
+.SS Makecache Command
+.nf
+Command: \fBmakecache\fP
+Aliases: \fBmc\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] makecache\fP
+Downloads and caches metadata for enabled repositories. Tries to
+avoid downloading whenever possible (e.g. when the local metadata hasn\(aqt
+expired yet or when the metadata timestamp hasn\(aqt changed).
+.TP
+.B \fBdnf [options] makecache \-\-timer\fP
+Like plain \fBmakecache\fP, but instructs DNF to be more resource\-aware,
+meaning it will not do anything if running on battery power and will terminate
+immediately if it\(aqs too soon after the last successful \fBmakecache\fP run
+(see \fBdnf.conf(5)\fP, metadata_timer_sync).
+.UNINDENT
+.SS Mark Command
+.nf
+Command: \fBmark\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf mark install <package\-spec>...\fP
+Marks the specified packages as installed by user. This can be useful if any package was installed as a dependency and is desired to stay on the system when \fI\%Autoremove Command\fP or \fI\%Remove Command\fP along with \fIclean_requirements_on_remove\fP configuration option set to \fBTrue\fP is executed.
+.TP
+.B \fBdnf mark remove <package\-spec>...\fP
+Unmarks the specified packages as installed by user. Whenever you as a user don\(aqt need a specific package you can mark it for removal. The package stays installed on the system but will be removed when \fI\%Autoremove Command\fP or \fI\%Remove Command\fP along with \fIclean_requirements_on_remove\fP configuration option set to \fBTrue\fP is executed. You should use this operation instead of \fI\%Remove Command\fP if you\(aqre not sure whether the package is a requirement of other user installed packages on the system.
+.TP
+.B \fBdnf mark group <package\-spec>...\fP
+Marks the specified packages as installed by group. This can be useful if any package was
+installed as a dependency or a user and is desired to be protected and handled as a group
+member like during group remove.
+.UNINDENT
+.SS Module Command
+.nf
+Command: \fBmodule\fP
+.fi
+.sp
+.sp
+Modularity overview is available at man page dnf.modularity(7)\&.
+Module subcommands take \fI\%<module\-spec>\fP\&... arguments that specify modules or profiles.
+.INDENT 0.0
+.TP
+.B \fBdnf [options] module install <module\-spec>...\fP
+Install module profiles, including their packages.
+In case no profile was provided, all default profiles get installed.
+Module streams get enabled accordingly.
+.sp
+This command cannot be used for switching module streams. Use the
+\fI\%dnf module switch\-to\fP command for that.
+.TP
+.B \fBdnf [options] module update <module\-spec>...\fP
+Update packages associated with an active module stream, optionally restricted to a profile.
+If the \fIprofile_name\fP is provided, only the packages referenced by that profile will be updated.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdnf [options] module switch\-to <module\-spec>...\fP
+Switch to or enable a module stream, change versions of installed packages to versions provided
+by the new stream, and remove packages from the old stream that are no longer available. It also
+updates installed profiles if they are available for the new stream. When a profile was
+provided, it installs that profile and does not update any already installed profiles.
+.sp
+This command can be used as a stronger version of the
+\fI\%dnf module enable\fP command, which not only enables modules,
+but also does a \fIdistrosync\fP to all modular packages in the enabled modules.
+.sp
+It can also be used as a stronger version of the
+\fI\%dnf module install\fP command, but it requires to specify
+profiles that are supposed to be installed, because \fIswitch\-to\fP command does not use \fIdefault
+profiles\fP\&. The \fIswitch\-to\fP command doesn\(aqt only install profiles, it also makes a \fIdistrosync\fP
+to all modular packages in the installed module.
+.TP
+.B \fBdnf [options] module remove <module\-spec>...\fP
+Remove installed module profiles, including packages that were installed with the
+\fI\%dnf module install\fP command. Will not remove packages
+required by other installed module profiles or by other user\-installed packages.
+In case no profile was provided, all installed profiles get removed.
+.TP
+.B \fBdnf [options] module remove \-\-all <module\-spec>...\fP
+Remove installed module profiles, including packages that were installed with the
+\fI\%dnf module install\fP command.
+With \-\-all option it additionally removes all packages whose names are provided by specified
+modules. Packages required by other installed module profiles and packages whose names are also
+provided by any other module are not removed.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdnf [options] module enable <module\-spec>...\fP
+Enable a module stream and make the stream RPMs available in the package set.
+.sp
+Modular dependencies are resolved, dependencies checked and also recursively enabled. In case
+of modular dependency issue the operation will be rejected. To perform the action anyway please use
+\-\fI\%\-skip\-broken\fP option.
+.sp
+This command cannot be used for switching module streams. Use the
+\fI\%dnf module switch\-to\fP command for that.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdnf [options] module disable <module\-name>...\fP
+Disable a module. All related module streams will become unavailable.
+Consequently, all installed profiles will be removed and the module RPMs
+will become unavailable in the package set. In case of modular
+dependency issue the operation will be rejected. To perform the action anyway please use \-\fI\%\-skip\-broken\fP option.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdnf [options] module reset <module\-name>...\fP
+Reset module state so it\(aqs no longer enabled or disabled.
+Consequently, all installed profiles will be removed and
+only RPMs from the default stream will be available in the package set.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdnf [options] module provides <package\-name\-spec>...\fP
+Lists all modular packages matching \fB<package\-name\-spec>\fP from all modules (including disabled), along with the modules and streams they belong to.
+.TP
+.B \fBdnf [options] module list [\-\-all] [module_name...]\fP
+Lists all module streams, their profiles and states (enabled, disabled, default).
+.TP
+.B \fBdnf [options] module list \-\-enabled [module_name...]\fP
+Lists module streams that are enabled.
+.TP
+.B \fBdnf [options] module list \-\-disabled [module_name...]\fP
+Lists module streams that are disabled.
+.TP
+.B \fBdnf [options] module list \-\-installed [module_name...]\fP
+List module streams with installed profiles.
+.TP
+.B \fBdnf [options] module info <module\-spec>...\fP
+Print detailed information about given module stream.
+.TP
+.B \fBdnf [options] module info \-\-profile <module\-spec>...\fP
+Print detailed information about given module profiles.
+.TP
+.B \fBdnf [options] module repoquery <module\-spec>...\fP
+List all available packages belonging to selected modules.
+.TP
+.B \fBdnf [options] module repoquery \-\-available <module\-spec>...\fP
+List all available packages belonging to selected modules.
+.TP
+.B \fBdnf [options] module repoquery \-\-installed <module\-spec>...\fP
+List all installed packages with same name like packages belonging to selected modules.
+.UNINDENT
+.SS Provides Command
+.nf
+Command: \fBprovides\fP
+Aliases: \fBprov\fP, \fBwhatprovides\fP, \fBwp\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] provides <provide\-spec>\fP
+Finds the packages providing the given \fB<provide\-spec>\fP\&. This is useful
+when one knows a filename and wants to find what package (installed or not)
+provides this file.
+The \fB<provide\-spec>\fP is gradually looked for at following locations:
+.INDENT 7.0
+.IP 1. 3
+The \fB<provide\-spec>\fP is matched with all file provides of any available package:
+.INDENT 3.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+$ dnf provides /usr/bin/gzip
+gzip\-1.9\-9.fc29.x86_64 : The GNU data compression program
+Matched from:
+Filename    : /usr/bin/gzip
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.IP 2. 3
+Then all provides of all available packages are searched:
+.INDENT 3.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+$ dnf provides "gzip(x86\-64)"
+gzip\-1.9\-9.fc29.x86_64 : The GNU data compression program
+Matched from:
+Provide     : gzip(x86\-64) = 1.9\-9.fc29
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.IP 3. 3
+DNF assumes that the \fB<provide\-spec>\fP is a system command, prepends it with \fB/usr/bin/\fP, \fB/usr/sbin/\fP prefixes (one at a time) and does the file provides search again. For legacy reasons (packages that didn\(aqt do UsrMove) also \fB/bin\fP and \fB/sbin\fP prefixes are being searched:
+.INDENT 3.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+$ dnf provides zless
+gzip\-1.9\-9.fc29.x86_64 : The GNU data compression program
+Matched from:
+Filename    : /usr/bin/zless
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.IP 4. 3
+If this last step also fails, DNF returns "Error: No Matches found".
+.UNINDENT
+.sp
+This command by default does not force a sync of expired metadata. See also \fI\%Metadata Synchronization\fP\&.
+.UNINDENT
+.SS Reinstall Command
+.nf
+Command: \fBreinstall\fP
+Aliases: \fBrei\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] reinstall <package\-spec>...\fP
+Installs the specified packages, fails if some of the packages are either
+not installed or not available (i.e. there is no repository where to
+download the same RPM).
+.UNINDENT
+.SS Remove Command
+.nf
+Command: \fBremove\fP
+Aliases: \fBrm\fP
+Aliases for \fI\%explicit NEVRA matching\fP: \fBremove\-n\fP, \fBremove\-na\fP, \fBremove\-nevra\fP
+Deprecated aliases: \fBerase\fP, \fBerase\-n\fP, \fBerase\-na\fP, \fBerase\-nevra\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] remove <package\-spec>...\fP
+Removes the specified packages from the system along with any packages depending on the packages being removed. Each \fB<spec>\fP can be either a \fB<package\-spec>\fP, which specifies a package directly, or a \fB@<group\-spec>\fP, which specifies an (environment) group which contains it. If \fBclean_requirements_on_remove\fP is enabled (the default), also removes any dependencies that are no longer needed.
+.TP
+.B \fBdnf [options] remove \-\-duplicates\fP
+Removes older versions of duplicate packages. To ensure the integrity of the system it
+reinstalls the newest package. In some cases the command cannot resolve conflicts. In such cases
+the \fI\%dnf shell\fP command with \fBremove \-\-duplicates\fP and \fBupgrade\fP
+dnf\-shell sub\-commands could help.
+.TP
+.B \fBdnf [options] remove \-\-oldinstallonly\fP
+Removes old installonly packages, keeping only latest versions and version of running kernel.
+.sp
+There are also a few specific remove commands \fBremove\-n\fP, \fBremove\-na\fP and \fBremove\-nevra\fP
+that allow the specification of an exact argument in the NEVRA format.
+.UNINDENT
+.SS Remove Examples
+.INDENT 0.0
+.TP
+.B \fBdnf remove acpi tito\fP
+Remove the \fBacpi\fP and \fBtito\fP packages.
+.TP
+.B \fBdnf remove $(dnf repoquery \-\-extras \-\-exclude=tito,acpi)\fP
+Remove packages not present in any repository, but don\(aqt remove the \fBtito\fP
+and \fBacpi\fP packages (they still might be removed if they depend on some of the removed packages).
+.UNINDENT
+.sp
+Remove older versions of duplicated packages (an equivalent of yum\(aqs \fIpackage\-cleanup \-\-cleandups\fP):
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf remove \-\-duplicates
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS Repoinfo Command
+.nf
+Command: \fBrepoinfo\fP
+.fi
+.sp
+.INDENT 0.0
+.INDENT 3.5
+An alias for the \fI\%repolist\fP command
+that provides more detailed information like \fBdnf repolist \-v\fP\&.
+.UNINDENT
+.UNINDENT
+.SS Repolist Command
+.nf
+Command: \fBrepolist\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] repolist [\-\-enabled|\-\-disabled|\-\-all]\fP
+Depending on the exact command lists enabled, disabled or all known
+repositories. Lists all enabled repositories by default. Provides more
+detailed information when \fB\-v\fP option is used.
+.UNINDENT
+.sp
+This command by default does not force a sync of expired metadata. See also \fI\%Metadata Synchronization\fP\&.
+.SS Repoquery Command
+.nf
+Command: \fBrepoquery\fP
+Aliases: \fBrq\fP
+Aliases for \fI\%explicit NEVRA matching\fP: \fBrepoquery\-n\fP, \fBrepoquery\-na\fP, \fBrepoquery\-nevra\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] repoquery [<select\-options>] [<query\-options>] [<package\-file\-spec>]\fP
+Searches available DNF repositories for selected packages and displays the requested information about them. It
+is an equivalent of \fBrpm \-q\fP for remote repositories.
+.TP
+.B \fBdnf [options] repoquery \-\-groupmember <package\-spec>...\fP
+List groups that contain <package\-spec>.
+.TP
+.B \fBdnf [options] repoquery \-\-querytags\fP
+Provides the list of tags recognized by the \-\fI\%\-queryformat\fP repoquery option.
+.sp
+There are also a few specific repoquery commands \fBrepoquery\-n\fP, \fBrepoquery\-na\fP and \fBrepoquery\-nevra\fP
+that allow the specification of an exact argument in the NEVRA format (does not affect arguments of options like \-\-whatprovides <arg>, ...).
+.UNINDENT
+.SS Select Options
+.sp
+Together with \fB<package\-file\-spec>\fP, control what packages are displayed in the output. If \fB<package\-file\-spec>\fP is given, limits the resulting set of
+packages to those matching the specification. All packages are considered if no \fB<package\-file\-spec>\fP is specified.
+.INDENT 0.0
+.TP
+.B \fB<package\-file\-spec>\fP
+Package specification in the NEVRA format (name[\-[epoch:]version[\-release]][.arch]), a package provide or a file provide. See \fI\%Specifying Packages\fP\&.
+.TP
+.B \fB\-a\fP, \fB\-\-all\fP
+Query all packages (for rpmquery compatibility, also a shorthand for repoquery \(aq*\(aq or repoquery
+without arguments).
+.TP
+.B \fB\-\-arch <arch>[,<arch>...], \-\-archlist <arch>[,<arch>...]\fP
+Limit the resulting set only to packages of selected architectures (default is all
+architectures). In some cases the result is affected by the basearch of the running system, therefore
+to run repoquery for an arch incompatible with your system use the \fB\-\-forcearch=<arch>\fP
+option to change the basearch.
+.TP
+.B \fB\-\-duplicates\fP
+Limit the resulting set to installed duplicate packages (i.e. more package versions
+for the same name and architecture). Installonly packages are excluded from this set.
+.TP
+.B \fB\-\-unneeded\fP
+Limit the resulting set to leaves packages that were installed as dependencies so they are no longer needed. This
+switch lists packages that are going to be removed after executing the \fBdnf autoremove\fP command.
+.TP
+.B \fB\-\-available\fP
+Limit the resulting set to available packages only (set by default).
+.TP
+.B \fB\-\-disable\-modular\-filtering\fP
+Disables filtering of modular packages, so that packages of inactive module streams are included in the result.
+.TP
+.B \fB\-\-extras\fP
+Limit the resulting set to packages that are not present in any of the available repositories.
+.TP
+.B \fB\-f <file>\fP, \fB\-\-file <file>\fP
+Limit the resulting set only to the package that owns \fB<file>\fP\&.
+.TP
+.B \fB\-\-installed\fP
+Limit the resulting set to installed packages only. The exclude option in the configuration file
+might influence the result, but if the command line option  \-\fI\%\-disableexcludes\fP is used, it ensures that all installed packages will be listed.
+.TP
+.B \fB\-\-installonly\fP
+Limit the resulting set to installed installonly packages.
+.TP
+.B \fB\-\-latest\-limit <number>\fP
+Limit the resulting set to <number> of latest packages for every package name and architecture.
+If <number> is negative, skip <number> of latest packages. For a negative <number> use the
+\fB\-\-latest\-limit=<number>\fP syntax.
+.TP
+.B \fB\-\-recent\fP
+Limit the resulting set to packages that were recently edited.
+.TP
+.B \fB\-\-repo <repoid>\fP
+Limit the resulting set only to packages from a repository identified by \fB<repoid>\fP\&.
+Can be used multiple times with accumulative effect.
+.TP
+.B \fB\-\-unsatisfied\fP
+Report unsatisfied dependencies among installed packages (i.e. missing requires and
+existing conflicts).
+.TP
+.B \fB\-\-upgrades\fP
+Limit the resulting set to packages that provide an upgrade for some already installed package.
+.TP
+.B \fB\-\-userinstalled\fP
+Limit the resulting set to packages installed by the user. The exclude option
+in the configuration file might influence the result, but if the command line option  \-\fI\%\-disableexcludes\fP is used, it ensures that all installed packages will be listed.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-whatdepends <capability>[,<capability>...]\fP
+Limit the resulting set only to packages that require, enhance, recommend, suggest or
+supplement any of \fB<capabilities>\fP\&.
+.TP
+.B \fB\-\-whatconflicts <capability>[,<capability>...]\fP
+Limit the resulting set only to packages that conflict with any of \fB<capabilities>\fP\&.
+.TP
+.B \fB\-\-whatenhances <capability>[,<capability>...]\fP
+Limit the resulting set only to packages that enhance any of \fB<capabilities>\fP\&. Use \-\fI\%\-whatdepends\fP if you want to list all depending packages.
+.TP
+.B \fB\-\-whatobsoletes <capability>[,<capability>...]\fP
+Limit the resulting set only to packages that obsolete any of \fB<capabilities>\fP\&.
+.TP
+.B \fB\-\-whatprovides <capability>[,<capability>...]\fP
+Limit the resulting set only to packages that provide any of \fB<capabilities>\fP\&.
+.TP
+.B \fB\-\-whatrecommends <capability>[,<capability>...]\fP
+Limit the resulting set only to packages that recommend any of \fB<capabilities>\fP\&. Use \-\fI\%\-whatdepends\fP if you want to list all depending packages.
+.TP
+.B \fB\-\-whatrequires <capability>[,<capability>...]\fP
+Limit the resulting set only to packages that require any of \fB<capabilities>\fP\&. Use \-\fI\%\-whatdepends\fP if you want to list all depending packages.
+.TP
+.B \fB\-\-whatsuggests <capability>[,<capability>...]\fP
+Limit the resulting set only to packages that suggest any of \fB<capabilities>\fP\&. Use \-\fI\%\-whatdepends\fP if you want to list all depending packages.
+.TP
+.B \fB\-\-whatsupplements <capability>[,<capability>...]\fP
+Limit the resulting set only to packages that supplement any of \fB<capabilities>\fP\&. Use \-\fI\%\-whatdepends\fP if you want to list all depending packages.
+.TP
+.B \fB\-\-alldeps\fP
+This option is stackable with \fB\-\-whatrequires\fP or \-\fI\%\-whatdepends\fP only. Additionally it adds all packages requiring
+the package features to the result set (used as default).
+.TP
+.B \fB\-\-exactdeps\fP
+This option is stackable with \fB\-\-whatrequires\fP or \-\fI\%\-whatdepends\fP only. Limit the resulting set only to packages
+that require \fB<capability>\fP specified by \-\-whatrequires.
+.TP
+.B \fB\-\-srpm\fP
+Operate on the corresponding source RPM.
+.UNINDENT
+.SS Query Options
+.sp
+Set what information is displayed about each package.
+.sp
+The following are mutually exclusive, i.e. at most one can be specified. If no query option is given, matching packages
+are displayed in the standard NEVRA notation.
+.INDENT 0.0
+.TP
+.B \fB\-i, \-\-info\fP
+Show detailed information about the package.
+.TP
+.B \fB\-l, \-\-list\fP
+Show the list of files in the package.
+.TP
+.B \fB\-s, \-\-source\fP
+Show the package source RPM name.
+.TP
+.B \fB\-\-changelogs\fP
+Print the package changelogs.
+.TP
+.B \fB\-\-conflicts\fP
+Display capabilities that the package conflicts with. Same as \fB\-\-qf "%{conflicts}\fP\&.
+.TP
+.B \fB\-\-depends\fP
+Display capabilities that the package depends on, enhances, recommends, suggests or
+supplements.
+.TP
+.B \fB\-\-enhances\fP
+Display capabilities enhanced by the package. Same as \fB\-\-qf "%{enhances}""\fP\&.
+.TP
+.B \fB\-\-location\fP
+Show a location where the package could be downloaded from.
+.TP
+.B \fB\-\-obsoletes\fP
+Display capabilities that the package obsoletes. Same as \fB\-\-qf "%{obsoletes}"\fP\&.
+.TP
+.B \fB\-\-provides\fP
+Display capabilities provided by the package. Same as \fB\-\-qf "%{provides}"\fP\&.
+.TP
+.B \fB\-\-recommends\fP
+Display capabilities recommended by the package. Same as \fB\-\-qf "%{recommends}"\fP\&.
+.TP
+.B \fB\-\-requires\fP
+Display capabilities that the package depends on. Same as \fB\-\-qf "%{requires}"\fP\&.
+.TP
+.B \fB\-\-requires\-pre\fP
+Display capabilities that the package depends on for running a \fB%pre\fP script.
+Same as \fB\-\-qf "%{requires\-pre}"\fP\&.
+.TP
+.B \fB\-\-suggests\fP
+Display capabilities suggested by the package. Same as \fB\-\-qf "%{suggests}"\fP\&.
+.TP
+.B \fB\-\-supplements\fP
+Display capabilities supplemented by the package. Same as \fB\-\-qf "%{supplements}"\fP\&.
+.TP
+.B \fB\-\-tree\fP
+Display a recursive tree of packages with capabilities specified by one of the following supplementary options:
+\fB\-\-whatrequires\fP, \fB\-\-requires\fP, \fB\-\-conflicts\fP, \fB\-\-enhances\fP, \fB\-\-suggests\fP, \fB\-\-provides\fP,
+\fB\-\-supplements\fP, \fB\-\-recommends\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-deplist\fP
+Produce a list of all direct dependencies and what packages provide those
+dependencies for the given packages. The result only shows the newest
+providers (which can be changed by using \-\-verbose).
+.TP
+.B \fB\-\-nvr\fP
+Show found packages in the name\-version\-release format. Same as
+\fB\-\-qf "%{name}\-%{version}\-%{release}"\fP\&.
+.TP
+.B \fB\-\-nevra\fP
+Show found packages in the name\-epoch:version\-release.architecture format. Same as
+\fB\-\-qf "%{name}\-%{epoch}:%{version}\-%{release}.%{arch}"\fP (default).
+.TP
+.B \fB\-\-envra\fP
+Show found packages in the epoch:name\-version\-release.architecture format. Same as
+\fB\-\-qf "%{epoch}:%{name}\-%{version}\-%{release}.%{arch}"\fP
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-qf <format>\fP, \fB\-\-queryformat <format>\fP
+Custom display format. \fB<format>\fP is the string to output for each matched package. Every occurrence of
+\fB%{<tag>}\fP within is replaced by the corresponding attribute of the package. The list of recognized tags can be displayed
+by running \fBdnf repoquery \-\-querytags\fP\&.
+.TP
+.B \fB\-\-recursive\fP
+Query packages recursively. Has to be used with \fB\-\-whatrequires <REQ>\fP
+(optionally with \fB\-\-alldeps\fP, but not with \fB\-\-exactdeps\fP) or with
+\fB\-\-requires <REQ> \-\-resolve\fP\&.
+.TP
+.B \fB\-\-resolve\fP
+resolve capabilities to originating package(s).
+.UNINDENT
+.SS Examples
+.sp
+Display NEVRAs of all available packages matching \fBlight*\fP:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery \(aqlight*\(aq
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Display NEVRAs of all available packages matching name \fBlight*\fP and architecture \fBnoarch\fP (accepts only arguments in the "<name>.<arch>" format):
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery\-na \(aqlight*.noarch\(aq
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Display requires of all lighttpd packages:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery \-\-requires lighttpd
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Display packages providing the requires of python packages:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery \-\-requires python \-\-resolve
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Display source rpm of ligttpd package:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery \-\-source lighttpd
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Display package name that owns the given file:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery \-\-file /etc/lighttpd/lighttpd.conf
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Display name, architecture and the containing repository of all lighttpd packages:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery \-\-queryformat \(aq%{name}.%{arch} : %{reponame}\(aq lighttpd
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Display all available packages providing "webserver":
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery \-\-whatprovides webserver
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Display all available packages providing "webserver" but only for "i686" architecture:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery \-\-whatprovides webserver \-\-arch i686
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Display duplicate packages:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery \-\-duplicates
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Display source packages that require a <provide> for a build:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery \-\-disablerepo="*" \-\-enablerepo="*\-source" \-\-arch=src \-\-whatrequires <provide>
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS Repository\-Packages Command
+.nf
+Command: \fBrepository\-packages\fP
+Deprecated aliases: \fBrepo\-pkgs\fP, \fBrepo\-packages\fP, \fBrepository\-pkgs\fP
+.fi
+.sp
+.sp
+The repository\-packages command allows the user to run commands on top of all packages in the repository named \fB<repoid>\fP\&. However, any dependency resolution takes into account packages from all enabled repositories. The \fB<package\-file\-spec>\fP and \fB<package\-spec>\fP specifications further limit the candidates to only those packages matching at least one of them.
+.sp
+The \fBinfo\fP subcommand lists description and summary information about packages depending on the packages\(aq relation to the repository. The \fBlist\fP subcommand just prints lists of those packages.
+.INDENT 0.0
+.TP
+.B \fBdnf [options] repository\-packages <repoid> check\-update [<package\-file\-spec>...]\fP
+Non\-interactively checks if updates of the specified packages in the repository are available. DNF exit code will be 100 when there are updates available and a list of the updates will be printed.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> info [\-\-all] [<package\-file\-spec>...]\fP
+List all related packages.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> info \-\-installed [<package\-file\-spec>...]\fP
+List packages installed from the repository.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> info \-\-available [<package\-file\-spec>...]\fP
+List packages available in the repository but not currently installed on the system.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> info \-\-extras [<package\-file\-specs>...]\fP
+List packages installed from the repository that are not available in any repository.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> info \-\-obsoletes [<package\-file\-spec>...]\fP
+List packages in the repository that obsolete packages installed on the system.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> info \-\-recent [<package\-file\-spec>...]\fP
+List packages recently added into the repository.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> info \-\-upgrades [<package\-file\-spec>...]\fP
+List packages in the repository that upgrade packages installed on the system.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> install [<package\-spec>...]\fP
+Install packages matching \fB<package\-spec>\fP from the repository. If \fB<package\-spec>\fP isn\(aqt specified at all, install all packages from the repository.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> list [\-\-all] [<package\-file\-spec>...]\fP
+List all related packages.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> list \-\-installed [<package\-file\-spec>...]\fP
+List packages installed from the repository.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> list \-\-available [<package\-file\-spec>...]\fP
+List packages available in the repository but not currently installed on the system.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> list \-\-extras [<package\-file\-spec>...]\fP
+List packages installed from the repository that are not available in any repository.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> list \-\-obsoletes [<package\-file\-spec>...]\fP
+List packages in the repository that obsolete packages installed on the system.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> list \-\-recent [<package\-file\-spec>...]\fP
+List packages recently added into the repository.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> list \-\-upgrades [<package\-file\-spec>...]\fP
+List packages in the repository that upgrade packages installed on the system.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> move\-to [<package\-spec>...]\fP
+Reinstall all those packages that are available in the repository.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> reinstall [<package\-spec>...]\fP
+Run the \fBreinstall\-old\fP subcommand. If it fails, run the \fBmove\-to\fP subcommand.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> reinstall\-old [<package\-spec>...]\fP
+Reinstall all those packages that were installed from the repository and simultaneously are available in the repository.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> remove [<package\-spec>...]\fP
+Remove all packages installed from the repository along with any packages depending on the packages being removed. If \fBclean_requirements_on_remove\fP is enabled (the default) also removes any dependencies that are no longer needed.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> remove\-or\-distro\-sync [<package\-spec>...]\fP
+Select all packages installed from the repository. Upgrade, downgrade or keep those of them that are available in another repository to match the latest version available there and remove the others along with any packages depending on the packages being removed. If \fBclean_requirements_on_remove\fP is enabled (the default) also removes any dependencies that are no longer needed.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> remove\-or\-reinstall [<package\-spec>...]\fP
+Select all packages installed from the repository. Reinstall those of them that are available in another repository and remove the others along with any packages depending on the packages being removed. If \fBclean_requirements_on_remove\fP is enabled (the default) also removes any dependencies that are no longer needed.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> upgrade [<package\-spec>...]\fP
+Update all packages to the highest resolvable version available in the repository.
+When versions are specified in the \fB<package\-spec>\fP, update to these versions.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> upgrade\-to [<package\-specs>...]\fP
+A deprecated alias for the upgrade subcommand.
+.UNINDENT
+.SS Search Command
+.nf
+Command: \fBsearch\fP
+Aliases: \fBse\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] search [\-\-all] <keywords>...\fP
+Search package metadata for keywords. Keywords are matched as case\-insensitive substrings, globbing is supported.
+By default lists packages that match all requested keys (AND operation). Keys are searched in package names and summaries.
+If the "\-\-all" option is used, lists packages that match at least one of the keys (an OR operation).
+In addition the keys are searched in the package descriptions and URLs.
+The result is sorted from the most relevant results to the least.
+.UNINDENT
+.sp
+This command by default does not force a sync of expired metadata. See also \fI\%Metadata Synchronization\fP\&.
+.SS Shell Command
+.nf
+Command: \fBshell\fP
+Aliases: \fBsh\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] shell [filename]\fP
+Open an interactive shell for conducting multiple commands during a single execution of DNF. These commands can be issued manually
+or passed to DNF from a file. The commands are much the same as the normal DNF command line options. There are a few additional
+commands documented below.
+.INDENT 7.0
+.TP
+.B \fBconfig [conf\-option] [value]\fP
+.INDENT 7.0
+.IP \(bu 2
+Set a configuration option to a requested value. If no value is given it prints the current value.
+.UNINDENT
+.TP
+.B \fBrepo [list|enable|disable] [repo\-id]\fP
+.INDENT 7.0
+.IP \(bu 2
+list: list repositories and their status
+.IP \(bu 2
+enable: enable repository
+.IP \(bu 2
+disable: disable repository
+.UNINDENT
+.TP
+.B \fBtransaction [list|reset|solve|run]\fP
+.INDENT 7.0
+.IP \(bu 2
+list: resolve and list the content of the transaction
+.IP \(bu 2
+reset: reset the transaction
+.IP \(bu 2
+run: resolve and run the transaction
+.UNINDENT
+.UNINDENT
+.sp
+Note that all local packages must be used in the first shell transaction subcommand (e.g.
+\fIinstall /tmp/nodejs\-1\-1.x86_64.rpm /tmp/acpi\-1\-1.noarch.rpm\fP) otherwise an error will occur.
+Any \fIdisable\fP, \fIenable\fP, and \fIreset\fP module operations (e.g. \fImodule enable nodejs\fP) must also
+be performed before any other shell transaction subcommand is used.
+.UNINDENT
+.SS Swap Command
+.nf
+Command: \fBswap\fP
+.fi
+.sp
+.sp
+\fBdnf [options] swap <remove\-spec> <install\-spec>\fP
+.INDENT 0.0
+.INDENT 3.5
+Remove spec and install spec in one transaction. Each \fB<spec>\fP can be either a
+\fI\%<package\-spec>\fP, which specifies a package directly, or a
+\fB@<group\-spec>\fP, which specifies an (environment) group which contains it. Automatic
+conflict solving is provided in DNF by the \-\-allowerasing option that provides the functionality of the swap
+command automatically.
+.UNINDENT
+.UNINDENT
+.SS Updateinfo Command
+.nf
+Command: \fBupdateinfo\fP
+Aliases: \fBupif\fP
+Deprecated aliases: \fBlist\-updateinfo\fP, \fBlist\-security\fP, \fBlist\-sec\fP, \fBinfo\-updateinfo\fP, \fBinfo\-security\fP, \fBinfo\-sec\fP, \fBsummary\-updateinfo\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] updateinfo [\-\-summary|\-\-list|\-\-info] [<availability>] [<spec>...]\fP
+Display information about update advisories.
+.sp
+Depending on the output type, DNF displays just counts of advisory types
+(omitted or \fB\-\-summary\fP), list of advisories (\fB\-\-list\fP) or detailed
+information (\fB\-\-info\fP). The \fB\-v\fP option extends the output. When
+used with \fB\-\-info\fP, the information is even more detailed. When used
+with \fB\-\-list\fP, an additional column with date of the last advisory update
+is added.
+.sp
+\fB<availability>\fP specifies whether advisories about newer versions of
+installed packages (omitted or \fB\-\-available\fP), advisories about equal and
+older versions of installed packages (\fB\-\-installed\fP), advisories about
+newer versions of those installed packages for which a newer version is
+available (\fB\-\-updates\fP) or advisories about any versions of installed
+packages (\fB\-\-all\fP) are taken into account. Most of the time, \fB\-\-available\fP
+and \fB\-\-updates\fP displays the same output. The outputs differ only in the
+cases when an advisory refers to a newer version but there is no enabled
+repository which contains any newer version.
+.sp
+Note, that \fB\-\-available\fP takes only the latest installed versions of
+packages into account. In case of the kernel packages (when multiple
+version could be installed simultaneously) also packages of the currently
+running version of kernel are added.
+.sp
+To print only advisories referencing a CVE or a bugzilla use \fB\-\-with\-cve\fP or
+\fB\-\-with\-bz\fP options. When these switches are used also the output
+of the \fB\-\-list\fP is altered \- the ID of the CVE or the bugzilla is printed
+instead of the one of the advisory.
+.sp
+If given and if neither ID, type (\fBbugfix\fP, \fBenhancement\fP,
+\fBsecurity\fP/\fBsec\fP) nor a package name of an advisory matches
+\fB<spec>\fP, the advisory is not taken into account. The matching is
+case\-sensitive and in the case of advisory IDs and package names, globbing
+is supported.
+.sp
+Output of the \fB\-\-summary\fP option is affected by the autocheck_running_kernel configuration option.
+.UNINDENT
+.SS Upgrade Command
+.nf
+Command: \fBupgrade\fP
+Aliases: \fBup\fP
+Deprecated aliases: \fBupdate\fP, \fBupgrade\-to\fP, \fBupdate\-to\fP, \fBlocalupdate\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] upgrade\fP
+Updates each package to the latest version that is both available and
+resolvable.
+.TP
+.B \fBdnf [options] upgrade <package\-spec>...\fP
+Updates each specified package to the latest available version. Updates
+dependencies as necessary. When versions are specified in the
+\fB<package\-spec>\fP, update to these versions.
+.TP
+.B \fBdnf [options] upgrade @<spec>...\fP
+Alias for the \fIdnf module update\fP command.
+.UNINDENT
+.sp
+If the main \fBobsoletes\fP configure option is true or the \fB\-\-obsoletes\fP flag
+is present, dnf will include package obsoletes in its calculations.
+For more information see obsoletes\&.
+.sp
+See also \fI\%Configuration Files Replacement Policy\fP\&.
+.SS Upgrade\-Minimal Command
+.nf
+Command: \fBupgrade\-minimal\fP
+Aliases: \fBup\-min\fP
+Deprecated aliases: \fBupdate\-minimal\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] upgrade\-minimal\fP
+Updates each package to the latest available version that provides a bugfix, enhancement
+or a fix for a security issue (security).
+.TP
+.B \fBdnf [options] upgrade\-minimal <package\-spec>...\fP
+Updates each specified package to the latest available version that provides
+a bugfix, enhancement or a fix for security issue (security). Updates
+dependencies as necessary.
+.UNINDENT
+.SH SPECIFYING PACKAGES
+.sp
+Many commands take a \fB<package\-spec>\fP parameter that selects a package for
+the operation. The \fB<package\-spec>\fP argument is matched against package
+NEVRAs, provides and file provides.
+.sp
+\fB<package\-file\-spec>\fP is similar to \fB<package\-spec>\fP, except provides
+matching is not performed. Therefore, \fB<package\-file\-spec>\fP is matched only
+against NEVRAs and file provides.
+.sp
+\fB<package\-name\-spec>\fP is matched against NEVRAs only.
+.SS Globs
+.sp
+Package specification supports the same glob pattern matching that shell does,
+in all three above mentioned packages it matches against (NEVRAs, provides and
+file provides).
+.sp
+The following patterns are supported:
+.INDENT 0.0
+.TP
+.B \fB*\fP
+Matches any number of characters.
+.TP
+.B \fB?\fP
+Matches any single character.
+.TP
+.B \fB[]\fP
+Matches any one of the enclosed characters. A pair of characters separated
+by a hyphen denotes a range expression; any character that falls between
+those two characters, inclusive, is matched. If the first character
+following the \fB[\fP is a \fB!\fP or a \fB^\fP then any character not enclosed
+is matched.
+.UNINDENT
+.sp
+Note: Curly brackets (\fB{}\fP) are not supported. You can still use them in
+shells that support them and let the shell do the expansion, but if quoted or
+escaped, dnf will not expand them.
+.SS NEVRA Matching
+.sp
+When matching against NEVRAs, partial matching is supported. DNF tries to match
+the spec against the following list of NEVRA forms (in decreasing order of
+priority):
+.INDENT 0.0
+.IP \(bu 2
+\fBname\-[epoch:]version\-release.arch\fP
+.IP \(bu 2
+\fBname.arch\fP
+.IP \(bu 2
+\fBname\fP
+.IP \(bu 2
+\fBname\-[epoch:]version\-release\fP
+.IP \(bu 2
+\fBname\-[epoch:]version\fP
+.UNINDENT
+.sp
+Note that \fBname\fP can in general contain dashes (e.g. \fBpackage\-with\-dashes\fP).
+.sp
+The first form that matches any packages is used and the remaining forms are
+not tried. If none of the forms match any packages, an attempt is made to match
+the \fB<package\-spec>\fP against full package NEVRAs. This is only relevant
+if globs are present in the \fB<package\-spec>\fP\&.
+.sp
+\fB<package\-spec>\fP matches NEVRAs the same way \fB<package\-name\-spec>\fP does,
+but in case matching NEVRAs fails, it attempts to match against provides and
+file provides of packages as well.
+.sp
+You can specify globs as part of any of the five NEVRA components. You can also
+specify a glob pattern to match over multiple NEVRA components (in other words,
+to match across the NEVRA separators). In that case, however, you need to write
+the spec to match against full package NEVRAs, as it is not possible to split
+such spec into NEVRA forms.
+.SS Specifying NEVRA Matching Explicitly
+.sp
+Some commands (\fBautoremove\fP, \fBinstall\fP, \fBremove\fP and \fBrepoquery\fP) also
+have aliases with suffixes \fB\-n\fP, \fB\-na\fP and \fB\-nevra\fP that allow to
+explicitly specify how to parse the arguments:
+.INDENT 0.0
+.IP \(bu 2
+Command \fBinstall\-n\fP only matches against \fBname\fP\&.
+.IP \(bu 2
+Command \fBinstall\-na\fP only matches against \fBname.arch\fP\&.
+.IP \(bu 2
+Command \fBinstall\-nevra\fP only matches against \fBname\-[epoch:]version\-release.arch\fP\&.
+.UNINDENT
+.SH SPECIFYING PROVIDES
+.sp
+\fB<provide\-spec>\fP in command descriptions means the command operates on
+packages providing the given spec. This can either be an explicit provide, an
+implicit provide (i.e. name of the package) or a file provide. The selection is
+case\-sensitive and globbing is supported.
+.SS Specifying File Provides
+.sp
+If a spec starts with either \fB/\fP or \fB*/\fP, it is considered as a potential file provide.
+.SH SPECIFYING GROUPS
+.sp
+\fB<group\-spec>\fP allows one to select (environment) groups a particular operation should work
+on. It is a case insensitive string (supporting globbing characters) that is
+matched against a group\(aqs ID, canonical name and name translated into the
+current LC_MESSAGES locale (if possible).
+.SH SPECIFYING MODULES
+.sp
+\fB<module\-spec>\fP allows one to select modules or profiles a particular operation should work
+on.
+.sp
+It is in the form of \fBNAME:STREAM:VERSION:CONTEXT:ARCH/PROFILE\fP and supported partial forms are the following:
+.INDENT 0.0
+.IP \(bu 2
+\fBNAME\fP
+.IP \(bu 2
+\fBNAME:STREAM\fP
+.IP \(bu 2
+\fBNAME:STREAM:VERSION\fP
+.IP \(bu 2
+\fBNAME:STREAM:VERSION:CONTEXT\fP
+.IP \(bu 2
+all above combinations with \fB::ARCH\fP (e.g. \fBNAME::ARCH\fP)
+.IP \(bu 2
+\fBNAME:STREAM:VERSION:CONTEXT:ARCH\fP
+.IP \(bu 2
+all above combinations with \fB/PROFILE\fP (e.g. \fBNAME/PROFILE\fP)
+.UNINDENT
+.sp
+In case stream is not specified, the enabled or the default stream is used, in this order. In case profile is not specified, the system default profile or the \(aqdefault\(aq profile is used.
+.SH SPECIFYING TRANSACTIONS
+.sp
+\fB<transaction\-spec>\fP can be in one of several forms. If it is an integer, it
+specifies a transaction ID. Specifying \fBlast\fP is the same as specifying the ID
+of the most recent transaction. The last form is \fBlast\-<offset>\fP, where
+\fB<offset>\fP is a positive integer. It specifies offset\-th transaction preceding
+the most recent transaction.
+.SH PACKAGE FILTERING
+.sp
+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.
+.SS Exclude Filtering
+.sp
+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 \-\fI\%\-disableexcludes\fP
+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 \-\fI\%\-disableplugin\fP command line option.
+.sp
+To disable all excludes for e.g. the install command you can use the following combination
+of command line options:
+.sp
+\fBdnf \-\-disableexcludes=all \-\-disableplugin="*" install bash\fP
+.SS Modular Filtering
+.sp
+Please see the modularity documentation for details on how Modular
+Filtering works.
+.sp
+With modularity, only RPM packages from \fBactive\fP module streams are included in the available
+package set. RPM packages from \fBinactive\fP module streams, as well as non\-modular packages with
+the same name or provides as a package from an \fBactive\fP module stream, are filtered out. Modular
+filtering is not applied to packages added from the command line, installed packages, or packages
+from repositories with \fBmodule_hotfixes=true\fP in their \fB\&.repo\fP file.
+.sp
+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
+\fBmodule_hotfixes=true\fP in the \fB\&.repo\fP file or use \fB\-\-setopt=<repo_id>.module_hotfixes=true\fP\&.
+.sp
+To discover the module which contains an excluded package use
+\fI\%dnf module provides\fP\&.
+.SH METADATA SYNCHRONIZATION
+.sp
+Correct operation of DNF depends on having access to up\-to\-date data from all enabled repositories but contacting remote mirrors on every operation considerably slows it down and costs bandwidth for both the client and the repository provider. The metadata_expire (see \fBdnf.conf(5)\fP) repository configuration option is used by DNF to determine whether a particular local copy of repository data is due to be re\-synced. It is crucial that the repository providers set the option well, namely to a value where it is guaranteed that if particular metadata was available in time \fBT\fP on the server, then all packages it references will still be available for download from the server in time \fBT + metadata_expire\fP\&.
+.sp
+To further reduce the bandwidth load, some of the commands where having up\-to\-date metadata is not critical (e.g. the \fBlist\fP command) do not look at whether a repository is expired and whenever any version of it is locally available to the user\(aqs account, it will be used. For non\-root use, see also the \fB\-\-cacheonly\fP switch. Note that in all situations the user can force synchronization of all enabled repositories with the \fB\-\-refresh\fP switch.
+.SH CONFIGURATION FILES REPLACEMENT POLICY
+.sp
+The updated packages could replace the old modified configuration files
+with the new ones or keep the older files. Neither of the files are actually replaced.
+To the conflicting ones RPM gives additional suffix to the origin name. Which file
+should maintain the true name after transaction is not controlled by package manager
+but is specified by each package itself, following packaging guideline.
+.SH FILES
+.INDENT 0.0
+.TP
+.B \fBCache Files\fP
+/var/cache/dnf
+.TP
+.B \fBMain Configuration\fP
+/etc/dnf/dnf.conf
+.TP
+.B \fBRepository\fP
+/etc/yum.repos.d/
+.UNINDENT
+.SH SEE ALSO
+.INDENT 0.0
+.IP \(bu 2
+\fBdnf.conf(5)\fP, DNF Configuration Reference
+.IP \(bu 2
+\fBdnf\-PLUGIN(8)\fP for documentation on DNF plugins.
+.IP \(bu 2
+\fBdnf.modularity(7)\fP, Modularity overview\&.
+.IP \(bu 2
+\fBdnf\-transaction\-json(5)\fP, Stored Transaction JSON Format Specification\&.
+.IP \(bu 2
+\fI\%DNF\fP project homepage (\fI\%https://github.com/rpm\-software\-management/dnf/\fP)
+.IP \(bu 2
+How to report a bug (\fI\%https://github.com/rpm\-software\-management/dnf/wiki/Bug\-Reporting\fP)
+.IP \(bu 2
+\fI\%YUM\fP project homepage (\fI\%http://yum.baseurl.org/\fP)
+.UNINDENT
+.SH AUTHOR
+See AUTHORS in DNF source distribution.
+.SH COPYRIGHT
+2012-2022, Red Hat, Licensed under GPLv2+
+.\" Generated by docutils manpage writer.
+.
diff --git a/dnf.conf.5 b/dnf.conf.5
new file mode 100644
index 0000000..214d6d0
--- /dev/null
+++ b/dnf.conf.5
@@ -0,0 +1,1312 @@
+.\" Man page generated from reStructuredText.
+.
+.
+.nr rst2man-indent-level 0
+.
+.de1 rstReportMargin
+\\$1 \\n[an-margin]
+level \\n[rst2man-indent-level]
+level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
+-
+\\n[rst2man-indent0]
+\\n[rst2man-indent1]
+\\n[rst2man-indent2]
+..
+.de1 INDENT
+.\" .rstReportMargin pre:
+. RS \\$1
+. nr rst2man-indent\\n[rst2man-indent-level] \\n[an-margin]
+. nr rst2man-indent-level +1
+.\" .rstReportMargin post:
+..
+.de UNINDENT
+. RE
+.\" indent \\n[an-margin]
+.\" old: \\n[rst2man-indent\\n[rst2man-indent-level]]
+.nr rst2man-indent-level -1
+.\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
+.in \\n[rst2man-indent\\n[rst2man-indent-level]]u
+..
+.TH "DNF.CONF" "5" "Apr 29, 2022" "4.12.0" "DNF"
+.SH NAME
+dnf.conf \- DNF Configuration Reference
+.SH DESCRIPTION
+.sp
+\fI\%DNF\fP by default uses the global configuration file at \fB/etc/dnf/dnf.conf\fP and
+all *.repo files found under \fB/etc/yum.repos.d\fP\&. The latter is typically used
+for repository configuration and takes precedence over global configuration.
+.sp
+The configuration file has INI format consisting of section declaration and
+\fBname=value\fP options below each on separate line. There are two types of sections
+in the configuration files: main and repository. Main section defines all global
+configuration options and should be only one.
+.sp
+The repository sections define the configuration for each (remote or local)
+repository. The section name of the repository in brackets serve as repo ID reference
+and should be unique across configuration files. The allowed characters of repo ID
+string are lower and upper case alphabetic letters, digits, \fB\-\fP, \fB_\fP, \fB\&.\fP
+and \fB:\fP\&. The minimal repository configuration file should aside from repo ID
+consists of \fI\%baseurl\fP, \fI\%metalink\fP
+or \fI\%mirrorlist\fP option definition.
+.SH DISTRIBUTION-SPECIFIC CONFIGURATION
+.sp
+Configuration options, namely \fI\%best\fP and
+\fI\%skip_if_unavailable\fP, can be set in the DNF
+configuration file by your distribution to override the DNF defaults.
+.SH [MAIN] OPTIONS
+.INDENT 0.0
+.TP
+.B \fBallow_vendor_change\fP
+\fI\%boolean\fP
+.sp
+If disabled dnf will stick to vendor when upgrading or downgrading rpms.
+Default is \fBTrue\fP
+.sp
+\fBWARNING:\fP
+.INDENT 7.0
+.INDENT 3.5
+This option is currently not supported for \fIdowngrade\fP and \fIdistro\-sync\fP commands
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBarch\fP
+\fI\%string\fP
+.sp
+The architecture used for installing packages. By default this is auto\-detected. Often used
+together with \fI\%ignorearch\fP option.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBassumeno\fP
+\fI\%boolean\fP
+.sp
+If enabled dnf will assume \fBNo\fP where it would normally prompt for
+confirmation from user input. Default is \fBFalse\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBassumeyes\fP
+\fI\%boolean\fP
+.sp
+If enabled dnf will assume \fBYes\fP where it would normally prompt for
+confirmation from user input (see also \fI\%defaultyes\fP). Default is \fBFalse\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBautocheck_running_kernel\fP
+\fI\%boolean\fP
+.sp
+Automatic check whether there is installed newer kernel module with security update than currently running kernel. Default is \fBTrue\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBbasearch\fP
+\fI\%string\fP
+.sp
+The base architecture used for installing packages. By default this is auto\-detected.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBbest\fP
+\fI\%boolean\fP
+.sp
+\fBTrue\fP instructs the solver to either use a package with the highest available
+version or fail. On \fBFalse\fP, do not fail if the latest version cannot be
+installed and go with the lower version. The default is \fBFalse\fP\&.  Note
+this option in particular \fI\%can be set in your configuration file by
+your distribution\fP\&. Also note that the
+use of the highest available version is only guaranteed for the packages
+directly requested and not for their dependencies.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBcachedir\fP
+\fI\%string\fP
+.sp
+Path to a directory used by various DNF subsystems for storing cache data.
+Has a reasonable root\-writable default depending on the distribution. DNF
+needs to be able to create files and directories at this location.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBcacheonly\fP
+\fI\%boolean\fP
+.sp
+If set to \fBTrue\fP DNF will run entirely from system cache, will not update
+the cache and will use it even in case it is expired. Default is \fBFalse\fP\&.
+.sp
+API Notes: Must be set before repository objects are created. Plugins must set
+this in the pre_config hook. Later changes are ignored.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBcheck_config_file_age\fP
+\fI\%boolean\fP
+.sp
+Specifies whether dnf should automatically expire metadata of repos, which are older than
+their corresponding configuration file (usually the dnf.conf file and the foo.repo file).
+Default is \fBTrue\fP (perform the check). Expire of metadata is also affected by metadata age.
+See also \fI\%metadata_expire\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBclean_requirements_on_remove\fP
+\fI\%boolean\fP
+.sp
+Remove dependencies that are no longer used during \fBdnf remove\fP\&. A package
+only qualifies for removal via \fBclean_requirements_on_remove\fP if it was
+installed through DNF but not on explicit user request, i.e. it was
+pulled in as a dependency. The default is True.
+(\fI\%installonlypkgs\fP are never automatically removed.)
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBconfig_file_path\fP
+\fI\%string\fP
+.sp
+Path to the default main configuration file. Default is \fB/etc/dnf/dnf.conf\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdebuglevel\fP
+\fI\%integer\fP
+.sp
+Debug messages output level, in the range 0 to 10. The higher the number the
+more debug output is put to stdout. Default is 2.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdebug_solver\fP
+\fI\%boolean\fP
+.sp
+Controls whether the libsolv debug files should be created when solving the
+transaction. The debug files are created in the \fI\&./debugdata\fP directory.
+Default is \fBFalse\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdefaultyes\fP
+\fI\%boolean\fP
+.sp
+If enabled the default answer to user confirmation prompts will be \fBYes\fP\&. Not
+to be confused with \fI\%assumeyes\fP which will not prompt at all. Default is \fBFalse\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdiskspacecheck\fP
+\fI\%boolean\fP
+.sp
+Controls whether rpm should check available disk space during the transaction.
+Default is \fBTrue\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBerrorlevel\fP
+\fI\%integer\fP
+.sp
+Error messages output level, in the range 0 to 10. The higher the number the
+more error output is put to stderr. Default is 3. This is deprecated in DNF
+and overwritten by \-\-verbose commandline
+option.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBexclude_from_weak\fP
+\fI\%list\fP
+.sp
+Prevent installing packages as weak dependencies (recommends or supplements). The packages can be specified
+by a name or a glob and separated by a comma. Defaults to \fB[]\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBexclude_from_weak_autodetect\fP
+\fI\%boolean\fP
+.sp
+If enabled, dnf will autodetect unmet weak dependencies (recommends or supplements) of packages installed on the
+system. Providers of these weak dependencies will not be installed by dnf as weak dependencies any more (they will
+still be installed if pulled in as a regular dependency). Defaults to \fBtrue\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBexit_on_lock\fP
+\fI\%boolean\fP
+.sp
+Should the dnf client exit immediately when something else has the lock. Default is \fBFalse\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBgpgkey_dns_verification\fP
+\fI\%boolean\fP
+.sp
+Should the dnf attempt to automatically verify GPG verification keys using the DNS
+system. This option requires the unbound python module (python3\-unbound) to
+be installed on the client system. This system has two main features. The first
+one is to check if any of the already installed keys have been revoked. Automatic
+removal of the key is not yet available, so it is up to the user, to remove
+revoked keys from the system. The second feature is automatic verification
+of new keys when a repository is added to the system. In interactive mode, the
+result is written to the output as a suggestion to the user. In
+non\-interactive mode (i.e. when \-y is used), this system will automatically
+accept keys that are available in the DNS and are correctly signed using
+DNSSEC. It will also accept keys that do not exist in the DNS system and
+their NON\-existence is cryptographically proven using DNSSEC. This is mainly to
+preserve backward compatibility.
+Default is \fBFalse\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBgroup_package_types\fP
+\fI\%list\fP
+.sp
+List of the following: optional, default, mandatory. Tells dnf which type of packages in groups will
+be installed when \(aqgroupinstall\(aq is called. Default is: \fBdefault, mandatory\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBignorearch\fP
+\fI\%boolean\fP
+.sp
+If set to \fBTrue\fP, RPM will allow attempts to install packages incompatible with the CPU\(aqs
+architecture. Defaults to \fBFalse\fP\&. Often used together with
+\fI\%arch\fP option.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBinstallonlypkgs\fP
+\fI\%list\fP
+.sp
+List of provide names of packages that should only ever be installed, never
+upgraded. Kernels in particular fall into this category.
+These packages are never removed by \fBdnf autoremove\fP even if they were
+installed as dependencies (see
+\fI\%clean_requirements_on_remove\fP
+for auto removal details).
+This option append the list values to the default installonlypkgs list used
+by DNF. The number of kept package versions is regulated
+by \fI\%installonly_limit\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBinstallonly_limit\fP
+\fI\%integer\fP
+.sp
+Number of \fI\%installonly packages\fP allowed to be installed
+concurrently. Defaults to 3. The minimal number of installonly packages is 2. Value 0 means
+unlimited number of installonly packages. Value 1 is explicitly not allowed since it
+complicates kernel upgrades due to protection of the running kernel from removal.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBinstallroot\fP
+\fI\%string\fP
+.sp
+The root of the filesystem for all packaging operations. It requires an absolute path. See also \fI\%\-\-installroot commandline option\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBinstall_weak_deps\fP
+\fI\%boolean\fP
+.sp
+When this option is set to True and a new package is about to be
+installed, all packages linked by weak dependency relation (Recommends or Supplements flags) with this package will be pulled into the transaction.
+Default is \fBTrue\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBkeepcache\fP
+\fI\%boolean\fP
+.sp
+Keeps downloaded packages in the cache when set to True. Even if it is set to False and packages have not been
+installed they will still persist until next successful transaction. The default
+is \fBFalse\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBlogdir\fP
+\fI\%string\fP
+.sp
+Directory where the log files will be stored. Default is \fB/var/log\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBlogfilelevel\fP
+\fI\%integer\fP
+.sp
+Log file messages output level, in the range 0 to 10. The higher the number the
+more debug output is put to logs. Default is 9.
+.sp
+This option controls dnf.log, dnf.librepo.log and hawkey.log. Although dnf.librepo.log
+and hawkey.log are affected only by setting the logfilelevel to 10.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBlog_compress\fP
+\fI\%boolean\fP
+.sp
+When set to \fBTrue\fP, log files are compressed when they are rotated. Default is \fBFalse\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBlog_rotate\fP
+\fI\%integer\fP
+.sp
+Log files are rotated \fBlog_rotate\fP times before being removed. If \fBlog_rotate\fP
+is \fB0\fP, the rotation is not performed.
+Default is \fB4\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBlog_size\fP
+storage size
+.sp
+Log  files are rotated when they grow bigger than log_size bytes. If
+log_size is 0, the rotation is not performed. The default is 1 MB. Valid
+units are \(aqk\(aq, \(aqM\(aq, \(aqG\(aq.
+.sp
+The size applies for individual log files, not the sum of all log files.
+See also \fI\%log_rotate\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBmetadata_timer_sync\fP
+time in seconds
+.sp
+The minimal period between two consecutive \fBmakecache timer\fP runs. The
+command will stop immediately if it\(aqs less than this time period since its
+last run. Does not affect simple \fBmakecache\fP run. Use \fB0\fP to completely
+disable automatic metadata synchronizing. The default corresponds to three
+hours. The value is rounded to the next commenced hour.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBmodule_obsoletes\fP
+\fI\%boolean\fP
+.sp
+This option controls whether dnf should apply modular obsoletes when possible. Default is \fBFalse\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBmodule_platform_id\fP
+\fI\%string\fP
+.sp
+Set this to $name:$stream to override PLATFORM_ID detected from \fB/etc/os\-release\fP\&.
+It is necessary to perform a system upgrade and switch to a new platform.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBmodule_stream_switch\fP
+\fI\%boolean\fP
+.sp
+This option controls whether it\(aqs possible to switch enabled streams of a module. Default is \fBFalse\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBmultilib_policy\fP
+\fI\%string\fP
+.sp
+Controls how multilib packages are treated during install operations. Can either be \fB"best"\fP (the default) for
+the depsolver to prefer packages which best match the system\(aqs architecture, or \fB"all"\fP to install packages for
+all available architectures.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBobsoletes\fP
+\fI\%boolean\fP
+.sp
+This option only has affect during an install/update. It enables
+dnf\(aqs obsoletes processing logic, which means it makes dnf check whether
+any dependencies of given package are no longer required and removes them.
+Useful when doing distribution level upgrades.
+Default is \(aqtrue\(aq.
+.sp
+Command\-line option: \-\-obsoletes
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBpersistdir\fP
+\fI\%string\fP
+.sp
+Directory where DNF stores its persistent data between runs. Default is \fB"/var/lib/dnf"\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBpluginconfpath\fP
+\fI\%list\fP
+.sp
+List of directories that are searched for plugin configurations to load. All
+configuration files found in these directories, that are named same as a
+plugin, are parsed. The default path is \fB/etc/dnf/plugins\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBpluginpath\fP
+\fI\%list\fP
+.sp
+List of directories that are searched for plugins to load. Plugins found in \fIany of the directories\fP in this configuration option are used. The default contains a Python version\-specific path.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBplugins\fP
+\fI\%boolean\fP
+.sp
+Controls whether the plugins are enabled. Default is \fBTrue\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBprotected_packages\fP
+\fI\%list\fP
+.sp
+List of packages that DNF should never completely remove. They are protected via Obsoletes as well as user/plugin removals.
+.sp
+The default is: \fBdnf\fP, \fBglob:/etc/yum/protected.d/*.conf\fP and \fBglob:/etc/dnf/protected.d/*.conf\fP\&. So any packages which should be protected can do so by including a file in \fB/etc/dnf/protected.d\fP with their package name in it.
+.sp
+DNF will protect also the package corresponding to the running version of the kernel. See also \fI\%protect_running_kernel\fP option.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBprotect_running_kernel\fP
+\fI\%boolean\fP
+.sp
+Controls whether the package corresponding to the running version of kernel is protected from removal. Default is \fBTrue\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBreleasever\fP
+\fI\%string\fP
+.sp
+Used for substitution of \fB$releasever\fP in the repository configuration.
+See also \fI\%repo variables\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBreposdir\fP
+\fI\%list\fP
+.sp
+DNF searches for repository configuration files in the paths specified by
+\fBreposdir\fP\&. The behavior of \fBreposdir\fP could differ when it is used
+along with \-\fI\%\-installroot\fP option.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBrpmverbosity\fP
+\fI\%string\fP
+.sp
+RPM debug scriptlet output level. One of: \fBcritical\fP, \fBemergency\fP,
+\fBerror\fP, \fBwarn\fP, \fBinfo\fP or \fBdebug\fP\&. Default is \fBinfo\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBstrict\fP
+\fI\%boolean\fP
+.sp
+If disabled, all unavailable packages or packages with broken dependencies given to DNF command will be skipped without raising the error causing the whole operation to fail. Currently works for install command only. The default is True.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBtsflags\fP
+\fI\%list\fP
+.sp
+List of strings adding extra flags for the RPM transaction.
+.TS
+center;
+|l|l|.
+_
+T{
+tsflag value
+T}	T{
+RPM Transaction Flag
+T}
+_
+T{
+noscripts
+T}	T{
+RPMTRANS_FLAG_NOSCRIPTS
+T}
+_
+T{
+test
+T}	T{
+RPMTRANS_FLAG_TEST
+T}
+_
+T{
+notriggers
+T}	T{
+RPMTRANS_FLAG_NOTRIGGERS
+T}
+_
+T{
+nodocs
+T}	T{
+RPMTRANS_FLAG_NODOCS
+T}
+_
+T{
+justdb
+T}	T{
+RPMTRANS_FLAG_JUSTDB
+T}
+_
+T{
+nocontexts
+T}	T{
+RPMTRANS_FLAG_NOCONTEXTS
+T}
+_
+T{
+nocaps
+T}	T{
+RPMTRANS_FLAG_NOCAPS
+T}
+_
+T{
+nocrypto
+T}	T{
+RPMTRANS_FLAG_NOFILEDIGEST
+T}
+_
+.TE
+.sp
+The \fBnocrypto\fP option will also set the \fB_RPMVSF_NOSIGNATURES\fP and
+\fB_RPMVSF_NODIGESTS\fP VS flags. The \fBtest\fP option provides a transaction check
+without performing the transaction. It includes downloading of packages, gpg keys check
+(including permanent import of additional keys if necessary), and rpm check to prevent
+file conflicts.
+The \fBnocaps\fP is supported with rpm\-4.14 or later. When \fBnocaps\fP is used but rpm
+doesn\(aqt support it, DNF only reports it as an invalid tsflag.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBupgrade_group_objects_upgrade\fP
+\fI\%boolean\fP
+.sp
+Set this to False to disable the automatic running of \fBgroup upgrade\fP when running the \fBupgrade\fP command. Default is \fBTrue\fP (perform the operation).
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBvarsdir\fP
+\fI\%list\fP
+.sp
+List of directories where variables definition files are looked for. Defaults to
+\fB"/etc/dnf/vars", "/etc/yum/vars"\fP\&. See \fI\%variable files\fP
+in Configuration reference.
+.TP
+.B \fBzchunk\fP
+\fI\%boolean\fP
+.sp
+Enables or disables the use of repository metadata compressed using the zchunk format (if available). Default is \fBTrue\fP\&.
+.UNINDENT
+.SH [MAIN] OPTIONS - COLORS
+.INDENT 0.0
+.TP
+.B \fBcolor\fP
+\fI\%string\fP
+.sp
+Controls if DNF uses colored output on the command line.
+Possible values: "auto", "never", "always". Default is "auto".
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBcolor_list_available_downgrade\fP
+\fI\%color\fP
+.sp
+Color of available packages that are older than installed packages.
+The option is used during list operations. Default is magenta.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBcolor_list_available_install\fP
+\fI\%color\fP
+.sp
+Color of packages that are available for installation and none of their versions in installed.
+The option is used during list operations. Default is bold,cyan.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBcolor_list_available_reinstall\fP
+\fI\%color\fP
+.sp
+Color of available packages that are identical to installed versions and are available for reinstalls. Default is bold,underline,green.
+The option is used during list operations.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBcolor_list_available_upgrade\fP
+\fI\%color\fP
+.sp
+Color of available packages that are newer than installed packages. Default is bold,blue.
+The option is used during list operations.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBcolor_list_installed_extra\fP
+\fI\%color\fP
+.sp
+Color of installed packages that do not have any version among available packages.
+The option is used during list operations. Default is bold,red.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBcolor_list_installed_newer\fP
+\fI\%color\fP
+.sp
+Color of installed packages that are newer than any version among available packages.
+The option is used during list operations. Default is bold,yellow.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBcolor_list_installed_older\fP
+\fI\%color\fP
+.sp
+Color of installed packages that are older than any version among available packages.
+The option is used during list operations. Default is yellow.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBcolor_list_installed_reinstall\fP
+\fI\%color\fP
+.sp
+Color of installed packages that are among available packages and can be reinstalled.
+The option is used during list operations. Default is cyan.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBcolor_search_match\fP
+\fI\%color\fP
+.sp
+Color of patterns matched in search output. Default is bold,magenta.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBcolor_update_installed\fP
+\fI\%color\fP
+.sp
+Color of removed packages. Default is red.
+This option is used during displaying transactions.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBcolor_update_local\fP
+\fI\%color\fP
+.sp
+Color of local packages that are installed from the @commandline repository.
+This option is used during displaying transactions. Default is green.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBcolor_update_remote\fP
+\fI\%color\fP
+.sp
+Color of packages that are installed/upgraded/downgraded from remote repositories.
+This option is used during displaying transactions. Default is bold,green.
+.UNINDENT
+.SH REPO OPTIONS
+.INDENT 0.0
+.TP
+.B \fBbaseurl\fP
+\fI\%list\fP
+.sp
+List of URLs for the repository. Defaults to \fB[]\fP\&.
+.sp
+URLs are tried in the listed order (equivalent to yum\(aqs "failovermethod=priority" behaviour).
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBcost\fP
+\fI\%integer\fP
+.sp
+The relative cost of accessing this repository, defaulting to 1000. This
+value is compared when the priorities of two repositories are the same. The
+repository with \fIthe lowest cost\fP is picked. It is useful to make the
+library prefer on\-disk repositories to remote ones.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBenabled\fP
+\fI\%boolean\fP
+.sp
+Include this repository as a package source. The default is True.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBgpgkey\fP
+\fI\%list\fP of strings
+.sp
+URLs of a GPG key files that can be used for signing metadata and packages of this repository, empty by default. If a file can not be verified using the already imported keys, import of keys from this option is attempted and the keys are then used for verification.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBmetalink\fP
+\fI\%string\fP
+.sp
+URL of a metalink for the repository. Defaults to \fBNone\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBmirrorlist\fP
+\fI\%string\fP
+.sp
+URL of a mirrorlist for the repository. Defaults to \fBNone\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBmodule_hotfixes\fP
+\fI\%boolean\fP
+.sp
+Set this to True to disable module RPM filtering and make all RPMs from the repository available. The default is False.
+This allows user to create a repository with cherry\-picked hotfixes that are included in a package set on a modular system.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBname\fP
+\fI\%string\fP
+.sp
+A human\-readable name of the repository. Defaults to the ID of the repository.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBpriority\fP
+\fI\%integer\fP
+.sp
+The priority value of this repository, default is 99. If there is more than one candidate package for a particular operation, the one from a repo with \fIthe lowest priority value\fP is picked, possibly despite being less convenient otherwise (e.g. by being a lower version).
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBtype\fP
+\fI\%string\fP
+.sp
+Type of repository metadata. Supported values are: \fBrpm\-md\fP\&.
+Aliases for \fBrpm\-md\fP: \fBrpm\fP, \fBrepomd\fP, \fBrpmmd\fP, \fByum\fP, \fBYUM\fP\&.
+.UNINDENT
+.SH REPO VARIABLES
+.sp
+Right side of every repo option can be enriched by the following variables:
+.sp
+\fB$arch\fP
+.INDENT 0.0
+.INDENT 3.5
+Refers to the system’s CPU architecture e.g, aarch64, i586, i686 and x86_64.
+.UNINDENT
+.UNINDENT
+.sp
+\fB$basearch\fP
+.INDENT 0.0
+.INDENT 3.5
+Refers to the base architecture of the system. For example, i686 and i586 machines
+both have a base architecture of i386, and AMD64 and Intel64 machines have a base architecture of x86_64.
+.UNINDENT
+.UNINDENT
+.sp
+\fB$releasever\fP
+.INDENT 0.0
+.INDENT 3.5
+Refers to the release version of operating system which DNF derives from information available in RPMDB.
+.UNINDENT
+.UNINDENT
+.sp
+In addition to these hard coded variables, user\-defined ones can also be used. They can be defined either via \fI\%variable files\fP, or by using special environmental variables. The names of these variables must be prefixed with DNF_VAR_ and they can only consist of alphanumeric characters and underscores:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+$ DNF_VAR_MY_VARIABLE=value
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+To use such variable in your repository configuration remove the prefix. E.g.:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+[myrepo]
+baseurl=https://example.site/pub/fedora/$MY_VARIABLE/releases/$releasever
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Note that it is not possible to override the \fBarch\fP and \fBbasearch\fP variables using either variable files or environmental variables.
+.sp
+Although users are encouraged to use named variables, the numbered environmental variables \fBDNF0\fP \- \fBDNF9\fP are still supported:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+$ DNF1=value
+
+[myrepo]
+baseurl=https://example.site/pub/fedora/$DNF1/releases/$releasever
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SH OPTIONS FOR BOTH [MAIN] AND REPO
+.sp
+Some options can be applied in either the main section, per repository, or in a
+combination. The value provided in the main section is used for all repositories
+as the default value, which repositories can then override in their
+configuration.
+.INDENT 0.0
+.TP
+.B \fBbandwidth\fP
+storage size
+.sp
+Total bandwidth available for downloading. Meaningful when used with the \fI\%throttle option\fP\&. Storage size is in bytes by default but can be specified with a unit of storage. Valid units are \(aqk\(aq, \(aqM\(aq, \(aqG\(aq.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBcountme\fP
+\fI\%boolean\fP
+.sp
+Determines whether a special flag should be added to a single, randomly
+chosen metalink/mirrorlist query each week.
+This allows the repository owner to estimate the number of systems
+consuming it, by counting such queries over a week\(aqs time, which is much
+more accurate than just counting unique IP addresses (which is subject to
+both overcounting and undercounting due to short DHCP leases and NAT,
+respectively).
+.sp
+The flag is a simple "countme=N" parameter appended to the metalink and
+mirrorlist URL, where N is an integer representing the "longevity" bucket
+this system belongs to.
+The following 4 buckets are defined, based on how many full weeks have
+passed since the beginning of the week when this system was installed: 1 =
+first week, 2 = first month (2\-4 weeks), 3 = six months (5\-24 weeks) and 4
+= more than six months (> 24 weeks).
+This information is meant to help distinguish short\-lived installs from
+long\-term ones, and to gather other statistics about system lifecycle.
+.sp
+Default is False.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdeltarpm\fP
+\fI\%boolean\fP
+.sp
+When enabled, DNF will save bandwidth by downloading much smaller delta RPM
+files, rebuilding them to RPM locally. However, this is quite CPU and I/O
+intensive. Default is True.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdeltarpm_percentage\fP
+\fI\%integer\fP
+.sp
+When the relative size of delta vs pkg is larger than this, delta is not used.  Default value is 75
+(Deltas must be at least 25% smaller than the pkg).  Use \fI0\fP to turn off delta rpm processing. Local repositories (with
+\fI\%file://\fP baseurl) have delta rpms turned off by default.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBenablegroups\fP
+\fI\%boolean\fP
+.sp
+Determines whether DNF will allow the use of package groups for this repository. Default is True (package groups are allowed).
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBexcludepkgs\fP
+\fI\%list\fP
+.sp
+Exclude packages of this repository, specified by a name or a glob and
+separated by a comma, from all operations.
+Can be disabled using \fB\-\-disableexcludes\fP command line switch.
+Defaults to \fB[]\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBfastestmirror\fP
+\fI\%boolean\fP
+.sp
+If enabled a metric is used to find the fastest available mirror. This overrides the order provided by the mirrorlist/metalink file itself. This file is often dynamically generated by the server to provide the best download speeds and enabling fastestmirror overrides this. The default is False.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBgpgcheck\fP
+\fI\%boolean\fP
+.sp
+Whether to perform GPG signature check on packages found in this repository.
+The default is False.
+.sp
+This option can only be used to strengthen the active RPM security policy set with the \fB%_pkgverify_level\fP macro (see the \fB/usr/lib/rpm/macros\fP file for details).
+That means, if the macro is set to \(aqsignature\(aq or \(aqall\(aq and this option is False, it will be overridden to True during DNF runtime, and a warning will be printed.
+To squelch the warning, make sure this option is True for every enabled repository, and also enable \fI\%localpkg_gpgcheck\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBincludepkgs\fP
+\fI\%list\fP
+.sp
+Include packages of this repository, specified by a name or a glob and separated by a comma, in all operations.
+Inverse of \fI\%excludepkgs\fP, DNF will exclude any package in the repository that doesn\(aqt match this list. This works in conjunction with \fBexcludepkgs\fP and doesn\(aqt override it, so if you \(aqexcludepkgs=*.i386\(aq and \(aqincludepkgs=python*\(aq then only packages starting with python that do not have an i386 arch will be seen by DNF in this repo.
+Can be disabled using \fB\-\-disableexcludes\fP command line switch.
+Defaults to \fB[]\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBip_resolve\fP
+IP address type
+.sp
+Determines how DNF resolves host names. Set this to \(aq4\(aq/\(aqIPv4\(aq or \(aq6\(aq/\(aqIPv6\(aq to resolve to IPv4 or IPv6 addresses only. By default, DNF resolves to either addresses.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBlocalpkg_gpgcheck\fP
+\fI\%boolean\fP
+.sp
+Whether to perform a GPG signature check on local packages (packages in a file, not in a repository).
+The default is False.
+This option is subject to the active RPM security policy (see \fI\%gpgcheck\fP for more details).
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBmax_parallel_downloads\fP
+\fI\%integer\fP
+.sp
+Maximum number of simultaneous package downloads. Defaults to 3. Maximum of 20.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBmetadata_expire\fP
+time in seconds
+.sp
+The period after which the remote repository is checked for metadata update and in the positive
+case the local metadata cache is updated. The default corresponds to 48 hours. Set this to
+\fB\-1\fP or \fBnever\fP to make the repo never considered expired. Expire of metadata can be also
+triggered by change of timestamp of configuration files (\fBdnf.conf\fP, \fB<repo>.repo\fP). See
+also \fI\%check_config_file_age\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBminrate\fP
+storage size
+.sp
+This sets the low speed threshold in bytes per second. If the server is sending data at the same or slower speed than this value for at least \fI\%timeout option\fP seconds, DNF aborts the connection. The default is 1000. Valid units are \(aqk\(aq, \(aqM\(aq, \(aqG\(aq.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBpassword\fP
+\fI\%string\fP
+.sp
+The password to use for connecting to a repository with basic HTTP authentication. Empty by default.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBproxy\fP
+\fI\%string\fP
+.sp
+URL of a proxy server to connect through. Set to an empty string in the repository configuration to disable proxy setting inherited from the main section. The expected format of this option is \fB<scheme>://<ip\-or\-hostname>[:port]\fP\&.
+(For backward compatibility, \(aq_none_\(aq can be used instead of the empty string.)
+.sp
+Note: The curl environment variables (such as \fBhttp_proxy\fP) are effective if this option is unset (or \(aq_none_\(aq is set in the repository configuration). See the \fBcurl\fP man page for details.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBproxy_username\fP
+\fI\%string\fP
+.sp
+The username to use for connecting to the proxy server. Empty by default.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBproxy_password\fP
+\fI\%string\fP
+.sp
+The password to use for connecting to the proxy server. Empty by default.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBproxy_auth_method\fP
+\fI\%string\fP
+.sp
+The authentication method used by the proxy server. Valid values are
+.TS
+center;
+|l|l|.
+_
+T{
+method
+T}	T{
+meaning
+T}
+_
+T{
+basic
+T}	T{
+HTTP Basic authentication
+T}
+_
+T{
+digest
+T}	T{
+HTTP Digest authentication
+T}
+_
+T{
+negotiate
+T}	T{
+HTTP Negotiate (SPNEGO) authentication
+T}
+_
+T{
+ntlm
+T}	T{
+HTTP NTLM authentication
+T}
+_
+T{
+digest_ie
+T}	T{
+HTTP Digest authentication with an IE flavor
+T}
+_
+T{
+ntlm_wb
+T}	T{
+NTLM delegating to winbind helper
+T}
+_
+T{
+none
+T}	T{
+None auth method
+T}
+_
+T{
+any
+T}	T{
+All suitable methods
+T}
+_
+.TE
+.sp
+Defaults to \fBany\fP
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBproxy_sslcacert\fP
+\fI\%string\fP
+.sp
+Path to the file containing the certificate authorities to verify proxy SSL certificates.
+Empty by default \- uses system default.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBproxy_sslverify\fP
+\fI\%boolean\fP
+.sp
+When enabled, proxy SSL certificates are verified. If the client can not be authenticated, connecting fails and the repository is not used any further. If \fBFalse\fP, SSL connections can be used, but certificates are not verified. Default is \fBTrue\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBproxy_sslclientcert\fP
+\fI\%string\fP
+.sp
+Path to the SSL client certificate used to connect to proxy server.
+Empty by default.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBproxy_sslclientkey\fP
+\fI\%string\fP
+.sp
+Path to the SSL client key used to connect to proxy server.
+Empty by default.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBrepo_gpgcheck\fP
+\fI\%boolean\fP
+.sp
+Whether to perform GPG signature check on this repository\(aqs metadata. The default is False.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBretries\fP
+\fI\%integer\fP
+.sp
+Set the number of total retries for downloading packages. The number is
+accumulative, so e.g. for \fIretries=10\fP, dnf will fail after any package
+download fails for eleventh time. Setting this to \fI0\fP makes dnf try
+forever. Default is \fI10\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBskip_if_unavailable\fP
+\fI\%boolean\fP
+.sp
+If enabled, DNF will continue running and disable the repository that couldn\(aqt be synchronized
+for any reason. This option doesn\(aqt affect skipping of unavailable packages after dependency
+resolution. To check inaccessibility of repository use it in combination with
+refresh command line option\&. The default is \fBFalse\fP\&.
+Note this option in particular \fI\%can be set in your configuration file
+by your distribution\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBsslcacert\fP
+\fI\%string\fP
+.sp
+Path to the file containing the certificate authorities to verify SSL certificates.
+Empty by default \- uses system default.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBsslverify\fP
+\fI\%boolean\fP
+.sp
+When enabled, remote SSL certificates are verified. If the client can not be authenticated, connecting fails and the repository is not used any further. If \fBFalse\fP, SSL connections can be used, but certificates are not verified. Default is \fBTrue\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBsslverifystatus\fP
+\fI\%boolean\fP
+.sp
+When enabled, revocation status of the server certificate is verified using the "Certificate Status Request" TLS extension (aka. OCSP stapling). Default is \fBFalse\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBsslclientcert\fP
+\fI\%string\fP
+.sp
+Path to the SSL client certificate used to connect to remote sites.
+Empty by default.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBsslclientkey\fP
+\fI\%string\fP
+.sp
+Path to the SSL client key used to connect to remote sites.
+Empty by default.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBthrottle\fP
+storage size
+.sp
+Limits the downloading speed. It might be an absolute value or a percentage, relative to the value of the \fI\%bandwidth option\fP option. \fB0\fP means no throttling (the default). The absolute value is in bytes by default but can be specified with a unit of storage. Valid units are \(aqk\(aq, \(aqM\(aq, \(aqG\(aq.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBtimeout\fP
+time in seconds
+.sp
+Number of seconds to wait for a connection before timing out. Used in combination with \fI\%minrate option\fP option. Defaults to 30 seconds.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBusername\fP
+\fI\%string\fP
+.sp
+The username to use for connecting to repo with basic HTTP authentication. Empty by default.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBuser_agent\fP
+\fI\%string\fP
+.sp
+The User\-Agent string to include in HTTP requests sent by DNF.
+Defaults to
+.INDENT 7.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+libdnf (NAME VERSION_ID; VARIANT_ID; OS.BASEARCH)
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+where NAME, VERSION_ID and VARIANT_ID are OS identifiers read from the
+\fBos\-release(5)\fP file, and OS and BASEARCH are the canonical OS
+name and base architecture, respectively.
+Example:
+.INDENT 7.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+libdnf (Fedora 31; server; Linux.x86_64)
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.SH TYPES OF OPTIONS
+.INDENT 0.0
+.TP
+.B \fBboolean\fP
+This is a data type with only two possible values.
+.sp
+One of following options can be used: 1, 0, True, False, yes, no
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBinteger\fP
+It is a whole number that can be written without a fractional component.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBlist\fP
+It is an option that could represent one or more strings separated by space or comma characters.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBstring\fP
+It is a sequence of symbols or digits without any whitespace character.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBcolor\fP
+A string describing color and modifiers separated with a comma, for example "red,bold".
+.INDENT 7.0
+.IP \(bu 2
+Colors: black, blue, cyan, green, magenta, red, white, yellow
+.IP \(bu 2
+Modifiers: bold, blink, dim, normal, reverse, underline
+.UNINDENT
+.UNINDENT
+.SH FILES
+.INDENT 0.0
+.TP
+.B \fBCache Files\fP
+/var/cache/dnf
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBMain Configuration File\fP
+/etc/dnf/dnf.conf
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBRepository\fP
+/etc/yum.repos.d/
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBVariables\fP
+Any properly named file in /etc/dnf/vars is turned into a variable named after the filename (or
+overrides any of the above variables but those set from commandline). Filenames may contain only
+alphanumeric characters and underscores and be in lowercase.
+Variables are also read from /etc/yum/vars for YUM compatibility reasons.
+.UNINDENT
+.SH SEE ALSO
+.INDENT 0.0
+.IP \(bu 2
+\fBdnf(8)\fP, DNF Command Reference
+.UNINDENT
+.SH AUTHOR
+See AUTHORS in DNF source distribution.
+.SH COPYRIGHT
+2012-2022, Red Hat, Licensed under GPLv2+
+.\" Generated by docutils manpage writer.
+.
diff --git a/dnf.modularity.7 b/dnf.modularity.7
new file mode 100644
index 0000000..818659b
--- /dev/null
+++ b/dnf.modularity.7
@@ -0,0 +1,125 @@
+.\" Man page generated from reStructuredText.
+.
+.
+.nr rst2man-indent-level 0
+.
+.de1 rstReportMargin
+\\$1 \\n[an-margin]
+level \\n[rst2man-indent-level]
+level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
+-
+\\n[rst2man-indent0]
+\\n[rst2man-indent1]
+\\n[rst2man-indent2]
+..
+.de1 INDENT
+.\" .rstReportMargin pre:
+. RS \\$1
+. nr rst2man-indent\\n[rst2man-indent-level] \\n[an-margin]
+. nr rst2man-indent-level +1
+.\" .rstReportMargin post:
+..
+.de UNINDENT
+. RE
+.\" indent \\n[an-margin]
+.\" old: \\n[rst2man-indent\\n[rst2man-indent-level]]
+.nr rst2man-indent-level -1
+.\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
+.in \\n[rst2man-indent\\n[rst2man-indent-level]]u
+..
+.TH "DNF.MODULARITY" "7" "Apr 29, 2022" "4.12.0" "DNF"
+.SH NAME
+dnf.modularity \- Modularity in DNF
+.sp
+Modularity is new way of building, organizing and delivering packages.
+For more details see: \fI\%https://docs.pagure.org/modularity/\fP
+.SH DEFINITIONS
+.INDENT 0.0
+.TP
+.B modulemd
+Every repository can contain \fBmodules\fP metadata with modulemd documents.
+These documents hold metadata about modules such as \fBName\fP, \fBStream\fP or list of packages.
+.TP
+.B (non\-modular) package
+Package that doesn\(aqt belong to a module.
+.TP
+.B modular package
+Package that belongs to a module. It is listed in modulemd under the \fBartifacts\fP section.
+Modular packages can be also identified by having \fB%{modularitylabel}\fP RPM header set.
+.TP
+.B (module) stream
+Stream is a collection of packages, a virtual repository. It is identified with
+\fBName\fP and \fBStream\fP from modulemd separated with colon, for example "postgresql:9.6".
+.sp
+Module streams can be \fBactive\fP or \fBinactive\fP\&. \fBactive\fP means the RPM
+packages from this stream are included in the set of available packages.
+Packages from \fBinactive\fP streams are filtered out.  Streams are
+\fBactive\fP either if marked as \fBdefault\fP or if they are explicitly
+\fBenabled\fP by a user action. Streams that satisfy dependencies of
+\fBdefault\fP or \fBenabled\fP streams are also considered \fBactive\fP\&.  Only
+one stream of a particular module can be \fBactive\fP at a given point in
+time.
+.UNINDENT
+.SH PACKAGE FILTERING
+.sp
+Without modules, packages with the highest version are used by default.
+.sp
+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\-modular 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\-modular binary
+packages to be filtered out.
+.SS Demodularized rpms
+.sp
+Contains names of RPMs excluded from package filtering for particular module stream. When defined in the latest active
+module, non\-modular RPMs with the same name or provide which were previously filtered out will reappear.
+.SH HOTFIX REPOSITORIES
+.sp
+In special cases, a user wants to cherry\-pick 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 or rejected from getting on the system by
+Fail\-safe mechanisms.
+To make the system use packages from a repository regardless of their modularity,
+specify \fBmodule_hotfixes=true\fP in the .repo file. This protects the repository from package filtering.
+.sp
+Please note the hotfix packages do not override module packages, they only become
+part of available package set. It\(aqs the package \fBEpoch\fP, \fBVersion\fP and \fBRelease\fP
+what determines if the package is the latest.
+.SH FAIL-SAFE MECHANISMS
+.SS Repositories with module metadata are unavailable
+.sp
+When a repository with module metadata is unavailable, package filtering must keep working.
+Non\-modular RPMs must remain unavailable and must never get on the system.
+.sp
+This happens when:
+.INDENT 0.0
+.IP \(bu 2
+user disables a repository via \fB\-\-disablerepo\fP or uses \fB\-\-repoid\fP
+.IP \(bu 2
+user removes a .repo file from disk
+.IP \(bu 2
+repository is not available and has \fBskip_if_unavailable=true\fP
+.UNINDENT
+.sp
+DNF keeps copies of the latest modulemd for every active stream
+and uses them if there\(aqs no modulemd available for the stream.
+This keeps package filtering working correctly.
+.sp
+The copies are made any time a transaction is resolved and started.
+That includes RPM transactions as well as any \fBdnf module <enable|disable|reset>\fP operations.
+.sp
+When the fail\-safe data is used, dnf show such modules as part of @modulefailsafe repository.
+.SS Orphaned modular packages
+.sp
+All packages that are built as a part of a module have \fB%{modularitylabel}\fP RPM header set.
+If such package becomes part of RPM transaction and cannot be associated with any available
+modulemd, DNF prevents from getting it on the system (package is available, but cannot be
+installed, upgraded, etc.). Packages from Hotfix repositories or Commandline repository are not
+affected by Fail\-safe mechanisms.
+.SH AUTHOR
+See AUTHORS in DNF source distribution.
+.SH COPYRIGHT
+2012-2022, Red Hat, Licensed under GPLv2+
+.\" Generated by docutils manpage writer.
+.
diff --git a/dnf.spec b/dnf.spec
new file mode 100644
index 0000000..0193fed
--- /dev/null
+++ b/dnf.spec
@@ -0,0 +1,289 @@
+%global min_libdnf_version 0.66.0
+
+Summary:        Package manager based on libdnf and libsolv. Replaces YUM.
+Name:           dnf
+Version:        4.16.2
+Release:        5%{?dist}
+License:        GPLv2+
+URL:            https://github.com/rpm-software-management/dnf
+Source0:        https://github.com/rpm-software-management/dnf/archive/%{version}/%{version}.tar.gz
+Source1:        dnf-automatic.8
+Source2:        dnf-transaction-json.5
+Source3:        dnf.8
+Source4:        dnf.conf.5
+Source5:        dnf.modularity.7
+Source6:        yum-aliases.1
+Source7:        yum-shell.8
+Source8:        yum.8
+Source9:        yum.conf.5
+Source10:       yum2dnf.8
+Patch5000:      5000-default-zchunk-false.patch
+Patch0001:      0001-Fix-bash-completion-due-to-sqlite-changes.patch
+Patch0002:      0002-Protect-dnf.patch
+BuildRequires:  cmake gettext systemd bash-completion
+Requires:       python3-%{name} = %{version}-%{release}
+Recommends:     (python3-dbus if NetworkManager) (sqlite if bash-completion)
+Provides:       dnf-command(alias)
+Provides:       dnf-command(autoremove)
+Provides:       dnf-command(check-update)
+Provides:       dnf-command(clean)
+Provides:       dnf-command(distro-sync)
+Provides:       dnf-command(downgrade)
+Provides:       dnf-command(group)
+Provides:       dnf-command(history)
+Provides:       dnf-command(info)
+Provides:       dnf-command(install)
+Provides:       dnf-command(list)
+Provides:       dnf-command(makecache)
+Provides:       dnf-command(mark)
+Provides:       dnf-command(provides)
+Provides:       dnf-command(reinstall)
+Provides:       dnf-command(remove)
+Provides:       dnf-command(repolist)
+Provides:       dnf-command(repoquery)
+Provides:       dnf-command(repository-packages)
+Provides:       dnf-command(search)
+Provides:       dnf-command(updateinfo)
+Provides:       dnf-command(upgrade)
+Provides:       dnf-command(upgrade-to)
+BuildArch:      noarch
+
+%description
+Dandified YUM (DNF) is the next upcoming major version of YUM. It does package 
+management using RPM, libsolv and hawkey libraries. For metadata handling and 
+package downloads it utilizes librepo. To process and effectively handle the 
+comps data it uses libcomps.
+
+%package data
+Summary:        Common data and configuration files for DNF
+Provides:       %{name}-conf = %{version}-%{release}
+
+%description data
+Common data and configuration files for DNF
+
+%package -n yum
+Summary:        Package manager
+Requires:       %{name} = %{version}-%{release}
+Provides:       %{name}-yum = %{version}-%{release}
+
+%description -n yum
+Utility that allows users to manage packages on their systems. \
+It supports RPMs, modules and comps groups & environments.
+
+%package -n python3-%{name}
+Summary:        Python 3 interface to DNF
+BuildRequires:  python3-devel python3-hawkey >= %{min_libdnf_version} python3-libdnf >= %{min_libdnf_version} python3-libcomps python3-libdnf
+BuildRequires:  libmodulemd python3-gpg python3-rpm
+Requires:       %{name}-data = %{version}-%{release} python3-hawkey >= %{min_libdnf_version} python3-libdnf >= %{min_libdnf_version}
+Requires:       libmodulemd python3-gpg python3-libcomps python3-libdnf python3-rpm
+Provides:       python%{python3_version}-%{name} = %{version}-%{release}
+Provides:       python-%{name} = %{version}-%{release}
+Recommends:     python3-unbound rpm-plugin-systemd-inhibit
+
+%description -n python3-%{name}
+Python 3 interface to DNF.
+
+%package automatic
+Summary:        Package manager - automated upgrades
+BuildRequires:  systemd
+Requires:       %{name} = %{version}-%{release}
+Requires(post): systemd 
+Requires(preun): systemd 
+Requires(postun): systemd
+
+%description automatic
+Systemd units that can periodically download package upgrades and apply them.
+
+%prep
+%autosetup -p1
+mkdir build
+
+%build
+pushd build
+  %cmake .. -DPYTHON_DESIRED:FILEPATH=%{__python3} -DDNF_VERSION=%{version} -DWITH_MAN=0
+  pushd %{_vpath_builddir}
+    %make_build
+  popd
+popd
+
+%install
+pushd build/%{_vpath_builddir}
+  %make_install
+popd
+
+%find_lang %{name}
+mkdir -p %{buildroot}%{_sysconfdir}/%{name}
+pushd %{buildroot}%{_sysconfdir}/%{name}
+  for folder in vars aliases.d plugins modules.d modules.defaults.d
+  do
+    mkdir -p $folder
+  done
+popd
+mkdir -p %{buildroot}%{python3_sitelib}/%{name}-plugins/__pycache__/
+mkdir -p %{buildroot}%{_localstatedir}/log/
+mkdir -p %{buildroot}%{_var}/cache/dnf/
+touch %{buildroot}%{_localstatedir}/log/%{name}.log
+mv %{buildroot}%{_bindir}/dnf-automatic-3 %{buildroot}%{_bindir}/dnf-automatic
+ln -sr %{buildroot}%{_bindir}/dnf-3 %{buildroot}%{_bindir}/dnf
+ln -sr  %{buildroot}%{_bindir}/dnf-3 %{buildroot}%{_bindir}/yum
+rm -vf %{buildroot}%{_bindir}/dnf-automatic-*
+mv -f %{buildroot}%{_sysconfdir}/%{name}/%{name}-strict.conf %{buildroot}%{_sysconfdir}/%{name}/%{name}.conf
+ln -sr  %{buildroot}%{_sysconfdir}/%{name}/%{name}.conf %{buildroot}%{_sysconfdir}/yum.conf
+mkdir -p %{buildroot}%{_sysconfdir}/yum
+ln -sr  %{buildroot}%{_sysconfdir}/%{name}/plugins %{buildroot}%{_sysconfdir}/yum/pluginconf.d
+ln -sr  %{buildroot}%{_sysconfdir}/%{name}/protected.d %{buildroot}%{_sysconfdir}/yum/protected.d
+ln -sr  %{buildroot}%{_sysconfdir}/%{name}/vars %{buildroot}%{_sysconfdir}/yum/vars
+
+mkdir -p %{buildroot}%{_mandir}/man1
+mkdir -p %{buildroot}%{_mandir}/man5
+mkdir -p %{buildroot}%{_mandir}/man7
+mkdir -p %{buildroot}%{_mandir}/man8
+
+gzip -c %{SOURCE1} > %{buildroot}%{_mandir}/man8/dnf-automatic.8.gz
+gzip -c %{SOURCE2} > %{buildroot}%{_mandir}/man5/dnf-transaction-json.5.gz
+gzip -c %{SOURCE3} > %{buildroot}%{_mandir}/man8/dnf.8.gz
+gzip -c %{SOURCE4} > %{buildroot}%{_mandir}/man5/dnf.conf.5.gz
+gzip -c %{SOURCE5} > %{buildroot}%{_mandir}/man7/dnf.modularity.7.gz
+gzip -c %{SOURCE6} > %{buildroot}%{_mandir}/man1/yum-aliases.1.gz
+gzip -c %{SOURCE7} > %{buildroot}%{_mandir}/man8/yum-shell.8.gz
+gzip -c %{SOURCE8} > %{buildroot}%{_mandir}/man8/yum.8.gz
+gzip -c %{SOURCE9} > %{buildroot}%{_mandir}/man5/yum.conf.5.gz
+gzip -c %{SOURCE10} > %{buildroot}%{_mandir}/man8/yum2dnf.8.gz
+
+%check
+pushd build/%{_vpath_builddir}
+  ctest -VV
+popd
+
+%post
+%systemd_post dnf-makecache.timer
+
+%preun
+%systemd_preun dnf-makecache.timer
+
+%postun
+%systemd_postun_with_restart dnf-makecache.timer
+
+%post automatic
+%systemd_post dnf-automatic.timer dnf-automatic-notifyonly.timer dnf-automatic-download.timer dnf-automatic-install.timer
+
+%preun automatic
+%systemd_preun dnf-automatic.timer dnf-automatic-notifyonly.timer dnf-automatic-download.timer dnf-automatic-install.timer
+
+%postun automatic
+%systemd_postun_with_restart dnf-automatic.timer dnf-automatic-notifyonly.timer dnf-automatic-download.timer dnf-automatic-install.timer
+
+%files -f %{name}.lang
+%{_bindir}/%{name}
+%dir %{_datadir}/bash-completion
+%dir %{_datadir}/bash-completion/completions
+%{_datadir}/bash-completion/completions/%{name}
+%{_mandir}/man8/%{name}.8*
+%{_mandir}/man8/yum2dnf.8*
+%{_mandir}/man7/dnf.modularity.7*
+%{_mandir}/man5/dnf-transaction-json.5*
+%{_unitdir}/%{name}-makecache.service
+%{_unitdir}/%{name}-makecache.timer
+%{_var}/cache/%{name}/
+
+%files data
+%license COPYING PACKAGE-LICENSING
+%doc AUTHORS README.rst
+%dir %{_sysconfdir}/%{name}
+%dir %{_sysconfdir}/%{name}/modules.d
+%dir %{_sysconfdir}/%{name}/modules.defaults.d
+%dir %{_sysconfdir}/%{name}/plugins
+%dir %{_sysconfdir}/%{name}/protected.d
+%dir %{_sysconfdir}/%{name}/vars
+%dir %{_sysconfdir}/%{name}/aliases.d
+%exclude %{_sysconfdir}/%{name}/aliases.d/zypper.conf
+%config(noreplace) %{_sysconfdir}/%{name}/%{name}.conf
+%config(noreplace) %{_sysconfdir}/%{name}/protected.d/python3-%{name}.conf
+%config(noreplace) %{_sysconfdir}/logrotate.d/%{name}
+%config %{_sysconfdir}/%{name}/protected.d/%{name}.conf
+%ghost %attr(644,-,-) %{_localstatedir}/log/hawkey.log
+%ghost %attr(644,-,-) %{_localstatedir}/log/%{name}.log
+%ghost %attr(644,-,-) %{_localstatedir}/log/%{name}.librepo.log
+%ghost %attr(644,-,-) %{_localstatedir}/log/%{name}.rpm.log
+%ghost %attr(644,-,-) %{_localstatedir}/log/%{name}.plugin.log
+%ghost %attr(755,-,-) %dir %{_sharedstatedir}/%{name}
+%ghost %attr(644,-,-) %{_sharedstatedir}/%{name}/groups.json
+%ghost %attr(755,-,-) %dir %{_sharedstatedir}/%{name}/yumdb
+%ghost %attr(755,-,-) %dir %{_sharedstatedir}/%{name}/history
+%{_mandir}/man5/%{name}.conf.5*
+%{_tmpfilesdir}/%{name}.conf
+%exclude %{_sysconfdir}/libreport/events.d/collect_dnf.conf
+
+%files -n yum
+%{_bindir}/yum
+%{_sysconfdir}/yum.conf
+%{_sysconfdir}/yum/pluginconf.d
+%{_sysconfdir}/yum/protected.d
+%{_sysconfdir}/yum/vars
+%{_mandir}/man8/yum.8*
+%{_mandir}/man5/yum.conf.5.*
+%{_mandir}/man8/yum-shell.8*
+%{_mandir}/man1/yum-aliases.1*
+%config %{_sysconfdir}/%{name}/protected.d/yum.conf
+
+%files -n python3-%{name}
+%{_bindir}/%{name}-3
+%exclude %{python3_sitelib}/%{name}/automatic
+%{python3_sitelib}/%{name}/
+%dir %{python3_sitelib}/%{name}-plugins
+%dir %{python3_sitelib}/%{name}-plugins/__pycache__
+
+%files automatic
+%{_bindir}/%{name}-automatic
+%config(noreplace) %{_sysconfdir}/%{name}/automatic.conf
+%{_mandir}/man8/%{name}-automatic.8*
+%{_unitdir}/%{name}-automatic.service
+%{_unitdir}/%{name}-automatic.timer
+%{_unitdir}/%{name}-automatic-notifyonly.service
+%{_unitdir}/%{name}-automatic-notifyonly.timer
+%{_unitdir}/%{name}-automatic-download.service
+%{_unitdir}/%{name}-automatic-download.timer
+%{_unitdir}/%{name}-automatic-install.service
+%{_unitdir}/%{name}-automatic-install.timer
+%{python3_sitelib}/%{name}/automatic/
+
+%changelog
+* Thu Oct 17 2024 bbrucezhang <bbrucezhang@tencent.com> - 4.16.2-5
+- [Type] bugfix
+- [DESC] Protect dnf
+
+* Thu Sep 26 2024 OpenCloudOS Release Engineering <releng@opencloudos.tech> - 4.16.2-4
+- Rebuilt for clarifying the packages requirement in BaseOS and AppStream
+
+* Fri Aug 16 2024 OpenCloudOS Release Engineering <releng@opencloudos.tech> - 4.16.2-3
+- Rebuilt for loongarch release
+
+* Wed Jan 17 2024 Ze Zhang <bbrucezhang@tencent.com> - 4.16.2-2
+- Fix bash completion due to sqlite changes
+
+* Wed Jan 17 2024 Ze Zhang <bbrucezhang@tencent.com> - 4.16.2-1
+- Update to 4.16.2
+
+* Tue Sep 19 2023 OpenCloudOS Release Engineering <releng@opencloudos.tech> - 4.15.1-4
+- Rebuilt for python 3.11
+
+* Fri Sep 08 2023 OpenCloudOS Release Engineering <releng@opencloudos.tech> - 4.15.1-3
+- Rebuilt for OpenCloudOS Stream 23.09
+
+* Wed Aug 23 2023 cunshunxia <cunshunxia@tencent.com> - 4.15.1-2
+- Rebuilt for libdnf 0.70.2
+
+* Tue Aug 15 2023 Xiaojie Chen <jackxjchen@tencent.com> - 4.15.1-1
+- Upgrade to upstream version 4.15.1
+
+* Tue Jul 11 2023 Yi Lin <nilusyi@tencent.com> - 4.14.0-1
+- upgrade to 4.14
+
+* Fri Apr 28 2023 OpenCloudOS Release Engineering <releng@opencloudos.tech> - 4.12.0-3
+- Rebuilt for OpenCloudOS Stream 23.05
+
+* Fri Mar 31 2023 OpenCloudOS Release Engineering <releng@opencloudos.tech> - 4.12.0-2
+- Rebuilt for OpenCloudOS Stream 23
+
+* Fri Apr 29 2022 Xun Zhong <victorzhong@tencent.com> - 4.12.0-1
+- Initial build
diff --git a/hello.py b/hello.py
deleted file mode 100644
index 6df61b5..0000000
--- a/hello.py
+++ /dev/null
@@ -1,3 +0,0 @@
-#!/usr/bin/env python3
-
-print("Hola")
diff --git a/sources b/sources
new file mode 100644
index 0000000..2dc197e
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+SHA512 (4.16.2.tar.gz) = 2a4cad1594c6f6f51958a7cb04632d3d4dee9df99cd29c68fa937b505fe348531cf3b1e89722563a20970dc1a301f7d2171976d92d6d702d761faa8c5af99313
diff --git a/yum-aliases.1 b/yum-aliases.1
new file mode 100644
index 0000000..a7e6250
--- /dev/null
+++ b/yum-aliases.1
@@ -0,0 +1,2123 @@
+.\" Man page generated from reStructuredText.
+.
+.
+.nr rst2man-indent-level 0
+.
+.de1 rstReportMargin
+\\$1 \\n[an-margin]
+level \\n[rst2man-indent-level]
+level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
+-
+\\n[rst2man-indent0]
+\\n[rst2man-indent1]
+\\n[rst2man-indent2]
+..
+.de1 INDENT
+.\" .rstReportMargin pre:
+. RS \\$1
+. nr rst2man-indent\\n[rst2man-indent-level] \\n[an-margin]
+. nr rst2man-indent-level +1
+.\" .rstReportMargin post:
+..
+.de UNINDENT
+. RE
+.\" indent \\n[an-margin]
+.\" old: \\n[rst2man-indent\\n[rst2man-indent-level]]
+.nr rst2man-indent-level -1
+.\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
+.in \\n[rst2man-indent\\n[rst2man-indent-level]]u
+..
+.TH "YUM-ALIASES" "1" "Apr 29, 2022" "4.12.0" "DNF"
+.SH NAME
+yum-aliases \- redirecting to DNF Command Reference
+.SH SYNOPSIS
+.sp
+\fBdnf [options] <command> [<args>...]\fP
+.SH DESCRIPTION
+.sp
+\fI\%DNF\fP is the next upcoming major version of \fI\%YUM\fP, a package manager for RPM\-based Linux
+distributions. It roughly maintains CLI compatibility with YUM and defines a strict API for
+extensions and plugins.
+.sp
+Plugins can modify or extend features of DNF or provide additional CLI commands on top of those
+mentioned below. If you know the name of such a command (including commands mentioned below), you
+may find/install the package which provides it using the appropriate virtual provide in the form of
+\fBdnf\-command(<alias>)\fP, where \fB<alias>\fP is the name of the command; e.g.\(ga\(gadnf install
+\(aqdnf\-command(versionlock)\(aq\(ga\(ga installs a \fBversionlock\fP plugin. This approach also applies to
+specifying dependencies of packages that require a particular DNF command.
+.sp
+Return values:
+.INDENT 0.0
+.IP \(bu 2
+\fB0\fP  : Operation was successful.
+.IP \(bu 2
+\fB1\fP  : An error occurred, which was handled by dnf.
+.IP \(bu 2
+\fB3\fP  : An unknown unhandled error occurred during operation.
+.IP \(bu 2
+\fB100\fP: See \fI\%check\-update\fP
+.IP \(bu 2
+\fB200\fP: There was a problem with acquiring or releasing of locks.
+.UNINDENT
+.sp
+Available commands:
+.INDENT 0.0
+.IP \(bu 2
+\fI\%alias\fP
+.IP \(bu 2
+\fI\%autoremove\fP
+.IP \(bu 2
+\fI\%check\fP
+.IP \(bu 2
+\fI\%check\-update\fP
+.IP \(bu 2
+\fI\%clean\fP
+.IP \(bu 2
+\fI\%deplist\fP
+.IP \(bu 2
+\fI\%distro\-sync\fP
+.IP \(bu 2
+\fI\%downgrade\fP
+.IP \(bu 2
+\fI\%group\fP
+.IP \(bu 2
+\fI\%help\fP
+.IP \(bu 2
+\fI\%history\fP
+.IP \(bu 2
+\fI\%info\fP
+.IP \(bu 2
+\fI\%install\fP
+.IP \(bu 2
+\fI\%list\fP
+.IP \(bu 2
+\fI\%makecache\fP
+.IP \(bu 2
+\fI\%mark\fP
+.IP \(bu 2
+\fI\%module\fP
+.IP \(bu 2
+\fI\%provides\fP
+.IP \(bu 2
+\fI\%reinstall\fP
+.IP \(bu 2
+\fI\%remove\fP
+.IP \(bu 2
+\fI\%repoinfo\fP
+.IP \(bu 2
+\fI\%repolist\fP
+.IP \(bu 2
+\fI\%repoquery\fP
+.IP \(bu 2
+\fI\%repository\-packages\fP
+.IP \(bu 2
+\fI\%search\fP
+.IP \(bu 2
+\fI\%shell\fP
+.IP \(bu 2
+\fI\%swap\fP
+.IP \(bu 2
+\fI\%updateinfo\fP
+.IP \(bu 2
+\fI\%upgrade\fP
+.IP \(bu 2
+\fI\%upgrade\-minimal\fP
+.UNINDENT
+.sp
+Additional information:
+.INDENT 0.0
+.IP \(bu 2
+\fI\%Options\fP
+.IP \(bu 2
+\fI\%Specifying Packages\fP
+.IP \(bu 2
+\fI\%Specifying Provides\fP
+.IP \(bu 2
+\fI\%Specifying File Provides\fP
+.IP \(bu 2
+\fI\%Specifying Groups\fP
+.IP \(bu 2
+\fI\%Specifying Transactions\fP
+.IP \(bu 2
+\fI\%Metadata Synchronization\fP
+.IP \(bu 2
+\fI\%Configuration Files Replacement Policy\fP
+.IP \(bu 2
+\fI\%Files\fP
+.IP \(bu 2
+\fI\%See Also\fP
+.UNINDENT
+.SH OPTIONS
+.INDENT 0.0
+.TP
+.B \fB\-4\fP
+Resolve to IPv4 addresses only.
+.TP
+.B \fB\-6\fP
+Resolve to IPv6 addresses only.
+.TP
+.B \fB\-\-advisory=<advisory>, \-\-advisories=<advisory>\fP
+Include packages corresponding to the advisory ID, Eg. FEDORA\-2201\-123.
+Applicable for the install, repoquery, updateinfo and upgrade commands.
+.TP
+.B \fB\-\-allowerasing\fP
+Allow erasing of installed packages to resolve dependencies. This option could be used as an alternative to the \fByum swap\fP command where packages to remove are not explicitly defined.
+.TP
+.B \fB\-\-assumeno\fP
+Automatically answer no for all questions.
+.TP
+.B \fB\-b, \-\-best\fP
+Try the best available package versions in transactions. Specifically during \fI\%dnf upgrade\fP, which by default skips over updates that can not be installed for dependency reasons, the switch forces DNF to only consider the latest packages. When running into packages with broken dependencies, DNF will fail giving a reason why the latest version can not be installed.
+.sp
+Note that the use of the newest available version is only guaranteed for
+the packages directly requested (e.g. as a command line arguments), and the
+solver may use older versions of dependencies to meet their requirements.
+.TP
+.B \fB\-\-bugfix\fP
+Include packages that fix a bugfix issue. Applicable for the install, repoquery, updateinfo and
+upgrade commands.
+.TP
+.B \fB\-\-bz=<bugzilla>, \-\-bzs=<bugzilla>\fP
+Include packages that fix a Bugzilla ID, Eg. 123123. Applicable for the install, repoquery,
+updateinfo and upgrade commands.
+.TP
+.B \fB\-C, \-\-cacheonly\fP
+Run entirely from system cache, don\(aqt update the cache and use it even in case it is expired.
+.sp
+DNF uses a separate cache for each user under which it executes. The cache for the root user is called the system cache. This switch allows a regular user read\-only access to the system cache, which usually is more fresh than the user\(aqs and thus he does not have to wait for metadata sync.
+.TP
+.B \fB\-\-color=<color>\fP
+Control whether color is used in terminal output. Valid values are \fBalways\fP, \fBnever\fP and \fBauto\fP (default).
+.TP
+.B \fB\-\-comment=<comment>\fP
+Add a comment to the transaction history.
+.TP
+.B \fB\-c <config file>, \-\-config=<config file>\fP
+Configuration file location.
+.TP
+.B \fB\-\-cve=<cves>, \-\-cves=<cves>\fP
+Include packages that fix a CVE (Common Vulnerabilities and Exposures) ID
+(\fI\%http://cve.mitre.org/about/\fP), Eg. CVE\-2201\-0123. Applicable for the install, repoquery, updateinfo,
+and upgrade commands.
+.TP
+.B \fB\-d <debug level>, \-\-debuglevel=<debug level>\fP
+Debugging output level. This is an integer value between 0 (no additional information strings) and 10 (shows all debugging information, even that not understandable to the user), default is 2. Deprecated, use \fB\-v\fP instead.
+.TP
+.B \fB\-\-debugsolver\fP
+Dump data aiding in dependency solver debugging into \fB\&./debugdata\fP\&.
+.UNINDENT
+.sp
+\fB\-\-disableexcludes=[all|main|<repoid>], \-\-disableexcludepkgs=[all|main|<repoid>]\fP
+.INDENT 0.0
+.INDENT 3.5
+Disable the configuration file excludes. Takes one of the following three options:
+.INDENT 0.0
+.IP \(bu 2
+\fBall\fP, disables all configuration file excludes
+.IP \(bu 2
+\fBmain\fP, disables excludes defined in the \fB[main]\fP section
+.IP \(bu 2
+\fBrepoid\fP, disables excludes defined for the given repository
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-disable, \-\-set\-disabled\fP
+Disable specified repositories (automatically saves). The option has to be used together with the
+\fBconfig\-manager\fP command (dnf\-plugins\-core).
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-disableplugin=<plugin names>\fP
+Disable the listed plugins specified by names or globs.
+.TP
+.B \fB\-\-disablerepo=<repoid>\fP
+Temporarily disable active repositories for the purpose of the current dnf command.
+Accepts an id, a comma\-separated list of ids, or a glob of ids. This option can be
+specified multiple times, but is mutually exclusive with \fB\-\-repo\fP\&.
+.TP
+.B \fB\-\-downloaddir=<path>, \-\-destdir=<path>\fP
+Redirect downloaded packages to provided directory. The option has to be used together with the \-\fI\%\-downloadonly\fP command line option, with the
+\fBdownload\fP, \fBmodulesync\fP or \fBreposync\fP commands (dnf\-plugins\-core) or with the \fBsystem\-upgrade\fP command
+(dnf\-plugins\-extras).
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-downloadonly\fP
+Download the resolved package set without performing any rpm transaction (install/upgrade/erase).
+.TP
+.B \fB\-e <error level>, \-\-errorlevel=<error level>\fP
+Error output level. This is an integer value between 0 (no error output) and
+10 (shows all error messages), default is 3. Deprecated, use \fB\-v\fP instead.
+.TP
+.B \fB\-\-enable, \-\-set\-enabled\fP
+Enable specified repositories (automatically saves). The option has to be used together with the
+\fBconfig\-manager\fP command (dnf\-plugins\-core).
+.TP
+.B \fB\-\-enableplugin=<plugin names>\fP
+Enable the listed plugins specified by names or globs.
+.TP
+.B \fB\-\-enablerepo=<repoid>\fP
+Temporarily enable additional repositories for the purpose of the current dnf command.
+Accepts an id, a comma\-separated list of ids, or a glob of ids. This option can be
+specified multiple times.
+.TP
+.B \fB\-\-enhancement\fP
+Include enhancement relevant packages. Applicable for the install, repoquery, updateinfo and
+upgrade commands.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-x <package\-file\-spec>, \-\-exclude=<package\-file\-spec>\fP
+Exclude packages specified by \fB<package\-file\-spec>\fP from the operation.
+.TP
+.B \fB\-\-excludepkgs=<package\-file\-spec>\fP
+Deprecated option. It was replaced by the \-\fI\%\-exclude\fP option.
+.TP
+.B \fB\-\-forcearch=<arch>\fP
+Force the use of an architecture. Any architecture can be specified.
+However, use of an architecture not supported natively by your CPU will
+require emulation of some kind. This is usually through QEMU. The behavior of \fB\-\-forcearch\fP
+can be configured by using the arch and ignorearch
+configuration options with values \fB<arch>\fP and \fBTrue\fP respectively.
+.TP
+.B \fB\-h, \-\-help, \-\-help\-cmd\fP
+Show the help.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-installroot=<path>\fP
+Specifies an alternative installroot, relative to where all packages will be
+installed. Think of this like doing \fBchroot <root> dnf\fP, except using
+\fB\-\-installroot\fP allows dnf to work before the chroot is created. It requires absolute path.
+.UNINDENT
+.INDENT 0.0
+.IP \(bu 2
+\fIcachedir\fP, \fIlog files\fP, \fIreleasever\fP, and \fIgpgkey\fP are taken from or
+stored in the installroot. \fIGpgkeys\fP are imported into the installroot from
+a path relative to the host which can be specified in the repository section
+of configuration files.
+.IP \(bu 2
+\fIconfiguration file\fP and reposdir are searched inside the installroot first. If
+they are not present, they are taken from the host system.
+Note:  When a path is specified within a command line argument
+(\fB\-\-config=<config file>\fP in case of \fIconfiguration file\fP and
+\fB\-\-setopt=reposdir=<reposdir>\fP for \fIreposdir\fP) then this path is always
+relative to the host with no exceptions.
+.IP \(bu 2
+\fIvars\fP are taken from the host system or installroot according to reposdir
+\&. When \fIreposdir\fP path is specified within a command line argument, vars are taken from the
+installroot. When varsdir paths are specified within a command line
+argument (\fB\-\-setopt=varsdir=<reposdir>\fP) then those path are always relative to the host with no
+exceptions.
+.IP \(bu 2
+The \fIpluginpath\fP and \fIpluginconfpath\fP are relative to the host.
+.UNINDENT
+.INDENT 0.0
+.INDENT 3.5
+Note: You may also want to use the command\-line option
+\fB\-\-releasever=<release>\fP when creating the installroot, otherwise the
+\fI$releasever\fP value is taken from the rpmdb within the installroot (and thus
+it is empty at the time of creation and the transaction will fail). If \fB\-\-releasever=/\fP is used, the
+releasever will be detected from the host (\fB/\fP) system. The new installroot path at the time of creation
+does not contain the \fIrepository\fP, \fIreleasever\fP and \fIdnf.conf\fP files.
+.sp
+On a modular system you may also want to use the
+\fB\-\-setopt=module_platform_id=<module_platform_name:stream>\fP command\-line option when creating the installroot,
+otherwise the module_platform_id value will be taken from the
+\fB/etc/os\-release\fP file within the installroot (and thus it will be empty at the time of creation, the modular
+dependency could be unsatisfied and modules content could be excluded).
+.sp
+Installroot examples:
+.INDENT 0.0
+.TP
+.B \fBdnf \-\-installroot=<installroot> \-\-releasever=<release> install system\-release\fP
+Permanently sets the \fBreleasever\fP of the system in the
+\fB<installroot>\fP directory to \fB<release>\fP\&.
+.TP
+.B \fBdnf \-\-installroot=<installroot> \-\-setopt=reposdir=<path> \-\-config /path/dnf.conf upgrade\fP
+Upgrades packages inside the installroot from a repository described by
+\fB\-\-setopt\fP using configuration from \fB/path/dnf.conf\fP\&.
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-newpackage\fP
+Include newpackage relevant packages. Applicable for the install, repoquery, updateinfo and
+upgrade commands.
+.TP
+.B \fB\-\-noautoremove\fP
+Disable removal of dependencies that are no longer used. It sets
+clean_requirements_on_remove configuration option to \fBFalse\fP\&.
+.TP
+.B \fB\-\-nobest\fP
+Set best option to \fBFalse\fP, so that transactions are not limited to best candidates only.
+.TP
+.B \fB\-\-nodocs\fP
+Do not install documentation. Sets the rpm flag \(aqRPMTRANS_FLAG_NODOCS\(aq.
+.TP
+.B \fB\-\-nogpgcheck\fP
+Skip checking GPG signatures on packages (if RPM policy allows).
+.TP
+.B \fB\-\-noplugins\fP
+Disable all plugins.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-obsoletes\fP
+This option has an effect on an install/update, it enables
+dnf\(aqs obsoletes processing logic. For more information see the
+obsoletes option.
+.sp
+This option also displays capabilities that the package obsoletes when used together with the \fI\%repoquery\fP command.
+.sp
+Configuration Option: obsoletes
+.TP
+.B \fB\-q, \-\-quiet\fP
+In combination with a non\-interactive command, shows just the relevant content. Suppresses messages notifying about the current state or actions of DNF.
+.TP
+.B \fB\-R <minutes>, \-\-randomwait=<minutes>\fP
+Maximum command wait time.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-refresh\fP
+Set metadata as expired before running the command.
+.TP
+.B \fB\-\-releasever=<release>\fP
+Configure DNF as if the distribution release was \fB<release>\fP\&. This can
+affect cache paths, values in configuration files and mirrorlist URLs.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-repofrompath <repo>,<path/url>\fP
+Specify a repository to add to the repositories for this query.
+This option can be used multiple times.
+.UNINDENT
+.INDENT 0.0
+.IP \(bu 2
+The repository label is specified by \fB<repo>\fP\&.
+.IP \(bu 2
+The path or url to the repository is specified by \fB<path/url>\fP\&.
+It is the same path as a baseurl and can be also enriched by the
+repo variables\&.
+.IP \(bu 2
+The configuration for the repository can be adjusted using \-\fI\%\-setopt\fP=<repo>.<option>=<value>.
+.IP \(bu 2
+If you want to view only packages from this repository, combine this
+with the \fB\-\-repo=<repo>\fP or \fB\-\-disablerepo="*"\fP switches.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-repo=<repoid>, \-\-repoid=<repoid>\fP
+Enable just specific repositories by an id or a glob. Can be used multiple
+times with accumulative effect. It is basically a shortcut for
+\fB\-\-disablerepo="*" \-\-enablerepo=<repoid>\fP and is mutually exclusive with
+the \fB\-\-disablerepo\fP option.
+.TP
+.B \fB\-\-rpmverbosity=<name>\fP
+RPM debug scriptlet output level. Sets the debug level to \fB<name>\fP for RPM scriptlets.
+For available levels, see the \fBrpmverbosity\fP configuration option.
+.TP
+.B \fB\-\-sec\-severity=<severity>, \-\-secseverity=<severity>\fP
+Includes packages that provide a fix for an issue of the specified severity.
+Applicable for the install, repoquery, updateinfo and upgrade commands.
+.TP
+.B \fB\-\-security\fP
+Includes packages that provide a fix for a security issue. Applicable for the
+upgrade command.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-setopt=<option>=<value>\fP
+Override a configuration option from the configuration file. To override configuration options for repositories, use
+\fBrepoid.option\fP for the \fB<option>\fP\&. Values for configuration options like \fBexcludepkgs\fP, \fBincludepkgs\fP,
+\fBinstallonlypkgs\fP and \fBtsflags\fP are appended to the original value, they do not override it. However, specifying
+an empty value (e.g. \fB\-\-setopt=tsflags=\fP) will clear the option.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-skip\-broken\fP
+Resolve depsolve problems by removing packages that are causing problems from the transaction.
+It is an alias for the strict configuration option with value \fBFalse\fP\&.
+Additionally, with the \fI\%enable\fP and
+\fI\%disable\fP module subcommands it allows one to perform an action even in case of
+broken modular dependencies.
+.TP
+.B \fB\-\-showduplicates\fP
+Show duplicate packages in repositories. Applicable for the list and search commands.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-v, \-\-verbose\fP
+Verbose operation, show debug messages.
+.TP
+.B \fB\-\-version\fP
+Show DNF version and exit.
+.TP
+.B \fB\-y, \-\-assumeyes\fP
+Automatically answer yes for all questions.
+.UNINDENT
+.sp
+List options are comma\-separated. Command\-line options override respective settings from configuration files.
+.SH COMMANDS
+.sp
+For an explanation of \fB<package\-spec>\fP, \fB<package\-file\-spec>\fP and \fB<package\-name\-spec>\fP see
+\fI\%Specifying Packages\fP\&.
+.sp
+For an explanation of \fB<provide\-spec>\fP see \fI\%Specifying Provides\fP\&.
+.sp
+For an explanation of \fB<group\-spec>\fP see \fI\%Specifying Groups\fP\&.
+.sp
+For an explanation of \fB<module\-spec>\fP see \fI\%Specifying Modules\fP\&.
+.sp
+For an explanation of \fB<transaction\-spec>\fP see \fI\%Specifying Transactions\fP\&.
+.SS Alias Command
+.nf
+Command: \fBalias\fP
+.fi
+.sp
+.sp
+Allows the user to define and manage a list of aliases (in the form \fB<name=value>\fP),
+which can be then used as dnf commands to abbreviate longer command sequences. For examples on using
+the alias command, see \fI\%Alias Examples\fP\&. For examples on the alias
+processing, see \fI\%Alias Processing Examples\fP\&.
+.sp
+To use an alias (name=value), the name must be placed as the first "command" (e.g. the first argument
+that is not an option). It is then replaced by its value and the resulting sequence is again searched
+for aliases. The alias processing stops when the first found command is not a name of any alias.
+.sp
+In case the processing would result in an infinite recursion, the original arguments are used instead.
+.sp
+Also, like in shell aliases, if the result starts with a \fB\e\fP, the alias processing will stop.
+.sp
+All aliases are defined in configuration files in the \fB/etc/dnf/aliases.d/\fP directory in the [aliases] section,
+and aliases created by the alias command are written to the \fBUSER.conf\fP file. In case of conflicts,
+the \fBUSER.conf\fP has the highest priority, and alphabetical ordering is used for the rest of the
+configuration files.
+.sp
+Optionally, there is the \fBenabled\fP option in the \fB[main]\fP section defaulting to True. This can be set for each
+file separately in the respective file, or globally for all aliases in the \fBALIASES.conf\fP file.
+.sp
+\fBdnf alias [options] [list] [<name>...]\fP
+.INDENT 0.0
+.INDENT 3.5
+List aliases with their final result. The \fB[<alias>...]\fP parameter further limits the result to only those aliases matching it.
+.UNINDENT
+.UNINDENT
+.sp
+\fBdnf alias [options] add <name=value>...\fP
+.INDENT 0.0
+.INDENT 3.5
+Create new aliases.
+.UNINDENT
+.UNINDENT
+.sp
+\fBdnf alias [options] delete <name>...\fP
+.INDENT 0.0
+.INDENT 3.5
+Delete aliases.
+.UNINDENT
+.UNINDENT
+.SS Alias Examples
+.INDENT 0.0
+.TP
+.B \fBdnf alias list\fP
+Lists all defined aliases.
+.TP
+.B \fBdnf alias add rm=remove\fP
+Adds a new command alias called \fBrm\fP which works the same as the \fBremove\fP command.
+.TP
+.B \fBdnf alias add upgrade="\eupgrade \-\-skip\-broken \-\-disableexcludes=all \-\-obsoletes"\fP
+Adds a new command alias called \fBupgrade\fP which works the same as the \fBupgrade\fP command,
+with additional options. Note that the original \fBupgrade\fP command is prefixed with a \fB\e\fP
+to prevent an infinite loop in alias processing.
+.UNINDENT
+.SS Alias Processing Examples
+.sp
+If there are defined aliases \fBin=install\fP and \fBFORCE="\-\-skip\-broken \-\-disableexcludes=all"\fP:
+.INDENT 0.0
+.IP \(bu 2
+\fBdnf FORCE in\fP will be replaced with \fBdnf \-\-skip\-broken \-\-disableexcludes=all install\fP
+.IP \(bu 2
+\fBdnf in FORCE\fP will be replaced with \fBdnf install FORCE\fP (which will fail)
+.UNINDENT
+.sp
+If there is defined alias \fBin=install\fP:
+.INDENT 0.0
+.IP \(bu 2
+\fBdnf in\fP will be replaced with \fBdnf install\fP
+.IP \(bu 2
+\fBdnf \-\-repo updates in\fP will be replaced with \fBdnf \-\-repo updates in\fP (which will fail)
+.UNINDENT
+.SS Autoremove Command
+.nf
+Command: \fBautoremove\fP
+Aliases for \fI\%explicit NEVRA matching\fP: \fBautoremove\-n\fP, \fBautoremove\-na\fP, \fBautoremove\-nevra\fP
+.fi
+.sp
+.sp
+\fBdnf [options] autoremove\fP
+.INDENT 0.0
+.INDENT 3.5
+Removes all "leaf" packages from the system that were originally installed as dependencies of user\-installed packages, but which are no longer required by any such package.
+.UNINDENT
+.UNINDENT
+.sp
+Packages listed in installonlypkgs are never automatically removed by
+this command.
+.sp
+\fBdnf [options] autoremove <spec>...\fP
+.INDENT 0.0
+.INDENT 3.5
+This is an alias for the \fI\%Remove Command\fP command with clean_requirements_on_remove set to
+\fBTrue\fP\&. It removes the specified packages from the system along with any packages depending on the
+packages being removed. Each \fB<spec>\fP can be either a \fB<package\-spec>\fP, which specifies a
+package directly, or a \fB@<group\-spec>\fP, which specifies an (environment) group which contains
+it. It also removes any dependencies that are no longer needed.
+.sp
+There are also a few specific autoremove commands \fBautoremove\-n\fP, \fBautoremove\-na\fP and
+\fBautoremove\-nevra\fP that allow the specification of an exact argument in the NEVRA
+(name\-epoch:version\-release.architecture) format.
+.UNINDENT
+.UNINDENT
+.sp
+This command by default does not force a sync of expired metadata. See also \fI\%Metadata Synchronization\fP\&.
+.SS Check Command
+.nf
+Command: \fBcheck\fP
+.fi
+.sp
+.sp
+\fBdnf [options] check [\-\-dependencies] [\-\-duplicates] [\-\-obsoleted] [\-\-provides]\fP
+.INDENT 0.0
+.INDENT 3.5
+Checks the local packagedb and produces information on any problems it
+finds. You can limit the checks to be performed by using the \fB\-\-dependencies\fP,
+\fB\-\-duplicates\fP, \fB\-\-obsoleted\fP and \fB\-\-provides\fP options (the default is to
+check everything).
+.UNINDENT
+.UNINDENT
+.SS Check\-Update Command
+.nf
+Command: \fBcheck\-update\fP
+Aliases: \fBcheck\-upgrade\fP
+.fi
+.sp
+.sp
+\fBdnf [options] check\-update [\-\-changelogs] [<package\-file\-spec>...]\fP
+.INDENT 0.0
+.INDENT 3.5
+Non\-interactively checks if updates of the specified packages are available. If no \fB<package\-file\-spec>\fP is given, checks whether any updates at all are available for your system. DNF exit code will be 100 when there are updates available and a list of the updates will be printed, 0 if not and 1 if an error occurs. If \fB\-\-changelogs\fP option is specified, also changelog delta of packages about to be updated is printed.
+.sp
+Please note that having a specific newer version available for an installed package (and reported by \fBcheck\-update\fP) does not imply that subsequent \fBdnf upgrade\fP will install it. The difference is that \fBdnf upgrade\fP has restrictions (like package dependencies being satisfied) to take into account.
+.sp
+The output is affected by the autocheck_running_kernel configuration option.
+.UNINDENT
+.UNINDENT
+.SS Clean Command
+.nf
+Command: \fBclean\fP
+.fi
+.sp
+.sp
+Performs cleanup of temporary files kept for repositories. This includes any
+such data left behind from disabled or removed repositories as well as for
+different distribution release versions.
+.INDENT 0.0
+.TP
+.B \fBdnf clean dbcache\fP
+Removes cache files generated from the repository metadata. This forces DNF
+to regenerate the cache files the next time it is run.
+.TP
+.B \fBdnf clean expire\-cache\fP
+Marks the repository metadata expired. DNF will re\-validate the cache for
+each repository the next time it is used.
+.TP
+.B \fBdnf clean metadata\fP
+Removes repository metadata. Those are the files which DNF uses to determine
+the remote availability of packages. Using this option will make DNF
+download all the metadata the next time it is run.
+.TP
+.B \fBdnf clean packages\fP
+Removes any cached packages from the system.
+.TP
+.B \fBdnf clean all\fP
+Does all of the above.
+.UNINDENT
+.SS Deplist Command
+.INDENT 0.0
+.TP
+.B \fBdnf [options] deplist [<select\-options>] [<query\-options>] [<package\-spec>]\fP
+Deprecated alias for \fI\%dnf repoquery \-\-deplist\fP\&.
+.UNINDENT
+.SS Distro\-Sync Command
+.nf
+Command: \fBdistro\-sync\fP
+Aliases: \fBdsync\fP
+Deprecated aliases: \fBdistrosync\fP, \fBdistribution\-synchronization\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf distro\-sync [<package\-spec>...]\fP
+As necessary upgrades, downgrades or keeps selected installed packages to match
+the latest version available from any enabled repository. If no package is given, all installed packages are considered.
+.sp
+See also \fI\%Configuration Files Replacement Policy\fP\&.
+.UNINDENT
+.SS Downgrade Command
+.nf
+Command: \fBdowngrade\fP
+Aliases: \fBdg\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] downgrade <package\-spec>...\fP
+Downgrades the specified packages to the highest installable package of all known lower versions
+if possible. When version is given and is lower than version of installed package then it
+downgrades to target version.
+.UNINDENT
+.SS Group Command
+.nf
+Command: \fBgroup\fP
+Aliases: \fBgrp\fP
+Deprecated aliases: \fBgroups\fP, \fBgrouplist\fP, \fBgroupinstall\fP, \fBgroupupdate\fP, \fBgroupremove\fP, \fBgrouperase\fP, \fBgroupinfo\fP
+.fi
+.sp
+.sp
+Groups are virtual collections of packages. DNF keeps track of groups that the user selected ("marked") installed and can manipulate the comprising packages with simple commands.
+.INDENT 0.0
+.TP
+.B \fBdnf [options] group [summary] <group\-spec>\fP
+Display overview of how many groups are installed and available. With a
+spec, limit the output to the matching groups. \fBsummary\fP is the default
+groups subcommand.
+.TP
+.B \fBdnf [options] group info <group\-spec>\fP
+Display package lists of a group. Shows which packages are installed or
+available from a repository when \fB\-v\fP is used.
+.TP
+.B \fBdnf [options] group install [\-\-with\-optional] <group\-spec>...\fP
+Mark the specified group installed and install packages it contains. Also
+include \fIoptional\fP packages of the group if \fB\-\-with\-optional\fP is
+specified. All \fImandatory\fP and \fIDefault\fP packages will be installed whenever possible.
+Conditional packages are installed if they meet their requirement.
+If the group is already (partially) installed, the command installs the missing packages from the group.
+Depending on the value of obsoletes configuration option group installation takes obsoletes into account.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdnf [options] group list <group\-spec>...\fP
+List all matching groups, either among installed or available groups. If
+nothing is specified, list all known groups. \fB\-\-installed\fP and \fB\-\-available\fP options narrow down the requested list.
+Records are ordered by the \fIdisplay_order\fP tag defined in comps.xml file.
+Provides a list of all hidden groups by using option \fB\-\-hidden\fP\&.
+Provides group IDs when the \fB\-v\fP or \fB\-\-ids\fP options are used.
+.TP
+.B \fBdnf [options] group remove <group\-spec>...\fP
+Mark the group removed and remove those packages in the group from the system which do not belong to another installed group and were not installed explicitly by the user.
+.TP
+.B \fBdnf [options] group upgrade <group\-spec>...\fP
+Upgrades the packages from the group and upgrades the group itself. The latter comprises of installing packages that were added to the group by the distribution and removing packages that got removed from the group as far as they were not installed explicitly by the user.
+.UNINDENT
+.sp
+Groups can also be marked installed or removed without physically manipulating any packages:
+.INDENT 0.0
+.TP
+.B \fBdnf [options] group mark install <group\-spec>...\fP
+Mark the specified group installed. No packages will be installed by this command, but the group is then considered installed.
+.TP
+.B \fBdnf [options] group mark remove <group\-spec>...\fP
+Mark the specified group removed. No packages will be removed by this command.
+.UNINDENT
+.sp
+See also \fI\%Configuration Files Replacement Policy\fP\&.
+.SS Help Command
+.nf
+Command: \fBhelp\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf help [<command>]\fP
+Displays the help text for all commands. If given a command name then only
+displays help for that particular command.
+.UNINDENT
+.SS History Command
+.nf
+Command: \fBhistory\fP
+Aliases: \fBhist\fP
+.fi
+.sp
+.sp
+The history command allows the user to view what has happened in past
+transactions and act according to this information (assuming the
+\fBhistory_record\fP configuration option is set).
+.INDENT 0.0
+.TP
+.B \fBdnf history [list] [\-\-reverse] [<spec>...]\fP
+The default history action is listing information about given transactions
+in a table. Each \fB<spec>\fP can be either a \fB<transaction\-spec>\fP, which
+specifies a transaction directly, or a \fB<transaction\-spec>..<transaction\-spec>\fP,
+which specifies a range of transactions, or a \fB<package\-name\-spec>\fP,
+which specifies a transaction by a package which it manipulated. When no
+transaction is specified, list all known transactions.
+.INDENT 7.0
+.TP
+.B \fB\-\-reverse\fP
+The order of \fBhistory list\fP output is printed in reverse order.
+.UNINDENT
+.TP
+.B \fBdnf history info [<spec>...]\fP
+Describe the given transactions. The meaning of \fB<spec>\fP is the same as
+in the \fI\%History List Command\fP\&. When no
+transaction is specified, describe what happened during the latest
+transaction.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdnf history redo <transaction\-spec>|<package\-file\-spec>\fP
+Repeat the specified transaction. Uses the last transaction (with the highest ID)
+if more than one transaction for given <package\-file\-spec> is found. If it is not possible
+to redo some operations due to the current state of RPMDB, it will not redo the transaction.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdnf history replay [\-\-ignore\-installed] [\-\-ignore\-extras] [\-\-skip\-unavailable] <filename>\fP
+Replay a transaction stored in file \fB<filename>\fP by \fI\%History Store
+Command\fP\&. The replay will perform the exact
+same operations on the packages as in the original transaction and will
+return with an error if case of any differences in installed packages or
+their versions. See also the Transaction JSON Format specification of the
+file format.
+.INDENT 7.0
+.TP
+.B \fB\-\-ignore\-installed\fP
+Don\(aqt check for the installed packages being in the same state as those
+recorded in the transaction. E.g. in case there is an upgrade
+\fBfoo\-1.0\fP \-> \fBfoo\-2.0\fP stored in the transaction, but there is
+\fBfoo\-1.1\fP installed on the target system.
+.TP
+.B \fB\-\-ignore\-extras\fP
+Don\(aqt check for extra packages pulled into the transaction on the
+target system. E.g. the target system may not have some dependency,
+which was installed on the source system. The replay errors out on this
+by default, as the transaction would not be the same.
+.TP
+.B \fB\-\-skip\-unavailable\fP
+In case some packages stored in the transaction are not available on
+the target system, skip them instead of erroring out.
+.UNINDENT
+.TP
+.B \fBdnf history rollback <transaction\-spec>|<package\-file\-spec>\fP
+Undo all transactions performed after the specified transaction. Uses the last transaction
+(with the highest ID) if more than one transaction for given <package\-file\-spec> is found.
+If it is not possible to undo some transactions due to the current state of RPMDB, it will not undo
+any transaction.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdnf history store [\-\-output <output\-file>] <transaction\-spec>\fP
+Store a transaction specified by \fB<transaction\-spec>\fP\&. The transaction
+can later be replayed by the \fI\%History Replay Command\fP\&.
+.sp
+Warning: The stored transaction format is considered unstable and may
+change at any time. It will work if the same version of dnf is used to
+store and replay (or between versions as long as it stays the same).
+.sp
+\fB\-o <output\-file>, \-\-output=<output\-file>\fP
+Store the serialized transaction into \fB<output\-file\fP\&. Default is \fBtransaction.json\fP\&.
+.TP
+.B \fBdnf history undo <transaction\-spec>|<package\-file\-spec>\fP
+Perform the opposite operation to all operations performed in the specified transaction.
+Uses the last transaction (with the highest ID) if more than one transaction for given
+<package\-file\-spec> is found. If it is not possible to undo some operations due to
+the current state of RPMDB, it will not undo the transaction.
+.TP
+.B \fBdnf history userinstalled\fP
+Show all installonly packages, packages installed outside of DNF and packages not
+installed as dependency. I.e. it lists packages that will stay on the system when
+\fI\%Autoremove Command\fP or \fI\%Remove Command\fP along with
+\fIclean_requirements_on_remove\fP configuration option set to True is executed. Note the same
+results can be accomplished with \fBdnf repoquery \-\-userinstalled\fP, and the repoquery
+command is more powerful in formatting of the output.
+.UNINDENT
+.sp
+This command by default does not force a sync of expired metadata, except for
+the redo, rollback, and undo subcommands.
+See also \fI\%Metadata Synchronization\fP
+and \fI\%Configuration Files Replacement Policy\fP\&.
+.SS Info Command
+.nf
+Command: \fBinfo\fP
+Aliases: \fBif\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] info [<package\-file\-spec>...]\fP
+Lists description and summary information about installed and available packages.
+.UNINDENT
+.sp
+The info command limits the displayed packages the same way as the \fI\%list command\fP\&.
+.sp
+This command by default does not force a sync of expired metadata. See also \fI\%Metadata Synchronization\fP\&.
+.SS Install Command
+.nf
+Command: \fBinstall\fP
+Aliases: \fBin\fP
+Aliases for \fI\%explicit NEVRA matching\fP: \fBinstall\-n\fP, \fBinstall\-na\fP, \fBinstall\-nevra\fP
+Deprecated aliases: \fBlocalinstall\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] install <spec>...\fP
+Makes sure that the given packages and their dependencies are installed
+on the system. Each \fB<spec>\fP can be either a \fI\%<package\-spec>\fP,
+or a @\fI\%<module\-spec>\fP, or a @\fI\%<group\-spec>\fP\&.
+See \fI\%Install Examples\fP\&.
+If a given package or provide cannot be (and is not already) installed,
+the exit code will be non\-zero.
+If the \fB<spec>\fP matches both a @\fI\%<module\-spec>\fP and
+a @\fI\%<group\-spec>\fP, only the module is installed.
+.sp
+When \fI\%<package\-spec>\fP to specify the exact version
+of the package is given, DNF will install the desired version, no matter which
+version of the package is already installed. The former version of the package
+will be removed in the case of non\-installonly package.
+.sp
+On the other hand if \fI\%<package\-spec>\fP specifies only a name,
+DNF also takes into account packages obsoleting it when picking which package to install.
+This behaviour is specific to the install command.
+Note that this can lead to seemingly unexpected results if a package has multiple versions and
+some older version is being obsoleted. It creates a split in the upgrade\-path and both ways
+are considered correct, the resulting package is picked simply by lexicographical order.
+.sp
+There are also a few specific install commands \fBinstall\-n\fP, \fBinstall\-na\fP and
+\fBinstall\-nevra\fP that allow the specification of an exact argument in the NEVRA format.
+.sp
+See also \fI\%Configuration Files Replacement Policy\fP\&.
+.UNINDENT
+.SS Install Examples
+.INDENT 0.0
+.TP
+.B \fBdnf install tito\fP
+Install the \fBtito\fP package (tito is the package name).
+.TP
+.B \fBdnf install ~/Downloads/tito\-0.6.2\-1.fc22.noarch.rpm\fP
+Install a local rpm file tito\-0.6.2\-1.fc22.noarch.rpm from the ~/Downloads/
+directory.
+.TP
+.B \fBdnf install tito\-0.5.6\-1.fc22\fP
+Install the package with a specific version. If the package is already installed it
+will automatically try to downgrade or upgrade to the specific version.
+.TP
+.B \fBdnf \-\-best install tito\fP
+Install the latest available version of the package. If the package is already installed it
+will try to automatically upgrade to the latest version. If the latest version
+of the package cannot be installed, the installation will fail.
+.TP
+.B \fBdnf install vim\fP
+DNF will automatically recognize that vim is not a package name, but
+will look up and install a package that provides vim with all the required
+dependencies. Note: Package name match has precedence over package provides
+match.
+.TP
+.B \fBdnf install https://kojipkgs.fedoraproject.org//packages/tito/0.6.0/1.fc22/noarch/tito\-0.6.0\-1.fc22.noarch.rpm\fP
+Install a package directly from a URL.
+.TP
+.B \fBdnf install \(aq@docker\(aq\fP
+Install all default profiles of module \(aqdocker\(aq and their RPMs. Module streams get enabled accordingly.
+.TP
+.B \fBdnf install \(aq@Web Server\(aq\fP
+Install the \(aqWeb Server\(aq environmental group.
+.TP
+.B \fBdnf install /usr/bin/rpmsign\fP
+Install a package that provides the /usr/bin/rpmsign file.
+.TP
+.B \fBdnf \-y install tito \-\-setopt=install_weak_deps=False\fP
+Install the \fBtito\fP package (tito is the package name) without weak deps. Weak deps are not required for
+core functionality of the package, but they enhance the original package (like extended
+documentation, plugins, additional functions, etc.).
+.TP
+.B \fBdnf install \-\-advisory=FEDORA\-2018\-b7b99fe852 \e*\fP
+Install all packages that belong to the "FEDORA\-2018\-b7b99fe852" advisory.
+.UNINDENT
+.SS List Command
+.nf
+Command: \fBlist\fP
+Aliases: \fBls\fP
+.fi
+.sp
+.sp
+Prints lists of packages depending on the packages\(aq relation to the
+system. A package is \fBinstalled\fP if it is present in the RPMDB, and it is \fBavailable\fP
+if it is not installed but is present in a repository that DNF knows about.
+.sp
+The list command also limits the displayed packages according to specific criteria,
+e.g. to only those that update an installed package (respecting the repository
+priority). The exclude option in the configuration file can influence the
+result, but if the \-\fI\%\-disableexcludes\fP command line
+option is used, it ensures that all installed packages will be listed.
+.INDENT 0.0
+.TP
+.B \fBdnf [options] list [\-\-all] [<package\-file\-spec>...]\fP
+Lists all packages, present in the RPMDB, in a repository or both.
+.TP
+.B \fBdnf [options] list \-\-installed [<package\-file\-spec>...]\fP
+Lists installed packages.
+.TP
+.B \fBdnf [options] list \-\-available [<package\-file\-spec>...]\fP
+Lists available packages.
+.TP
+.B \fBdnf [options] list \-\-extras [<package\-file\-spec>...]\fP
+Lists extras, that is packages installed on the system that are not
+available in any known repository.
+.TP
+.B \fBdnf [options] list \-\-obsoletes [<package\-file\-spec>...]\fP
+List packages installed on the system that are obsoleted by packages in
+any known repository.
+.TP
+.B \fBdnf [options] list \-\-recent [<package\-file\-spec>...]\fP
+List packages recently added into the repositories.
+.TP
+.B \fBdnf [options] list \-\-upgrades [<package\-file\-spec>...]\fP
+List upgrades available for the installed packages.
+.TP
+.B \fBdnf [options] list \-\-autoremove\fP
+List packages which will be removed by the \fBdnf autoremove\fP command.
+.UNINDENT
+.sp
+This command by default does not force a sync of expired metadata. See also \fI\%Metadata Synchronization\fP\&.
+.SS Makecache Command
+.nf
+Command: \fBmakecache\fP
+Aliases: \fBmc\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] makecache\fP
+Downloads and caches metadata for enabled repositories. Tries to
+avoid downloading whenever possible (e.g. when the local metadata hasn\(aqt
+expired yet or when the metadata timestamp hasn\(aqt changed).
+.TP
+.B \fBdnf [options] makecache \-\-timer\fP
+Like plain \fBmakecache\fP, but instructs DNF to be more resource\-aware,
+meaning it will not do anything if running on battery power and will terminate
+immediately if it\(aqs too soon after the last successful \fBmakecache\fP run
+(see \fBdnf.conf(5)\fP, metadata_timer_sync).
+.UNINDENT
+.SS Mark Command
+.nf
+Command: \fBmark\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf mark install <package\-spec>...\fP
+Marks the specified packages as installed by user. This can be useful if any package was installed as a dependency and is desired to stay on the system when \fI\%Autoremove Command\fP or \fI\%Remove Command\fP along with \fIclean_requirements_on_remove\fP configuration option set to \fBTrue\fP is executed.
+.TP
+.B \fBdnf mark remove <package\-spec>...\fP
+Unmarks the specified packages as installed by user. Whenever you as a user don\(aqt need a specific package you can mark it for removal. The package stays installed on the system but will be removed when \fI\%Autoremove Command\fP or \fI\%Remove Command\fP along with \fIclean_requirements_on_remove\fP configuration option set to \fBTrue\fP is executed. You should use this operation instead of \fI\%Remove Command\fP if you\(aqre not sure whether the package is a requirement of other user installed packages on the system.
+.TP
+.B \fBdnf mark group <package\-spec>...\fP
+Marks the specified packages as installed by group. This can be useful if any package was
+installed as a dependency or a user and is desired to be protected and handled as a group
+member like during group remove.
+.UNINDENT
+.SS Module Command
+.nf
+Command: \fBmodule\fP
+.fi
+.sp
+.sp
+Modularity overview is available at man page dnf.modularity(7)\&.
+Module subcommands take \fI\%<module\-spec>\fP\&... arguments that specify modules or profiles.
+.INDENT 0.0
+.TP
+.B \fBdnf [options] module install <module\-spec>...\fP
+Install module profiles, including their packages.
+In case no profile was provided, all default profiles get installed.
+Module streams get enabled accordingly.
+.sp
+This command cannot be used for switching module streams. Use the
+\fI\%dnf module switch\-to\fP command for that.
+.TP
+.B \fBdnf [options] module update <module\-spec>...\fP
+Update packages associated with an active module stream, optionally restricted to a profile.
+If the \fIprofile_name\fP is provided, only the packages referenced by that profile will be updated.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdnf [options] module switch\-to <module\-spec>...\fP
+Switch to or enable a module stream, change versions of installed packages to versions provided
+by the new stream, and remove packages from the old stream that are no longer available. It also
+updates installed profiles if they are available for the new stream. When a profile was
+provided, it installs that profile and does not update any already installed profiles.
+.sp
+This command can be used as a stronger version of the
+\fI\%dnf module enable\fP command, which not only enables modules,
+but also does a \fIdistrosync\fP to all modular packages in the enabled modules.
+.sp
+It can also be used as a stronger version of the
+\fI\%dnf module install\fP command, but it requires to specify
+profiles that are supposed to be installed, because \fIswitch\-to\fP command does not use \fIdefault
+profiles\fP\&. The \fIswitch\-to\fP command doesn\(aqt only install profiles, it also makes a \fIdistrosync\fP
+to all modular packages in the installed module.
+.TP
+.B \fBdnf [options] module remove <module\-spec>...\fP
+Remove installed module profiles, including packages that were installed with the
+\fI\%dnf module install\fP command. Will not remove packages
+required by other installed module profiles or by other user\-installed packages.
+In case no profile was provided, all installed profiles get removed.
+.TP
+.B \fBdnf [options] module remove \-\-all <module\-spec>...\fP
+Remove installed module profiles, including packages that were installed with the
+\fI\%dnf module install\fP command.
+With \-\-all option it additionally removes all packages whose names are provided by specified
+modules. Packages required by other installed module profiles and packages whose names are also
+provided by any other module are not removed.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdnf [options] module enable <module\-spec>...\fP
+Enable a module stream and make the stream RPMs available in the package set.
+.sp
+Modular dependencies are resolved, dependencies checked and also recursively enabled. In case
+of modular dependency issue the operation will be rejected. To perform the action anyway please use
+\-\fI\%\-skip\-broken\fP option.
+.sp
+This command cannot be used for switching module streams. Use the
+\fI\%dnf module switch\-to\fP command for that.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdnf [options] module disable <module\-name>...\fP
+Disable a module. All related module streams will become unavailable.
+Consequently, all installed profiles will be removed and the module RPMs
+will become unavailable in the package set. In case of modular
+dependency issue the operation will be rejected. To perform the action anyway please use \-\fI\%\-skip\-broken\fP option.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdnf [options] module reset <module\-name>...\fP
+Reset module state so it\(aqs no longer enabled or disabled.
+Consequently, all installed profiles will be removed and
+only RPMs from the default stream will be available in the package set.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdnf [options] module provides <package\-name\-spec>...\fP
+Lists all modular packages matching \fB<package\-name\-spec>\fP from all modules (including disabled), along with the modules and streams they belong to.
+.TP
+.B \fBdnf [options] module list [\-\-all] [module_name...]\fP
+Lists all module streams, their profiles and states (enabled, disabled, default).
+.TP
+.B \fBdnf [options] module list \-\-enabled [module_name...]\fP
+Lists module streams that are enabled.
+.TP
+.B \fBdnf [options] module list \-\-disabled [module_name...]\fP
+Lists module streams that are disabled.
+.TP
+.B \fBdnf [options] module list \-\-installed [module_name...]\fP
+List module streams with installed profiles.
+.TP
+.B \fBdnf [options] module info <module\-spec>...\fP
+Print detailed information about given module stream.
+.TP
+.B \fBdnf [options] module info \-\-profile <module\-spec>...\fP
+Print detailed information about given module profiles.
+.TP
+.B \fBdnf [options] module repoquery <module\-spec>...\fP
+List all available packages belonging to selected modules.
+.TP
+.B \fBdnf [options] module repoquery \-\-available <module\-spec>...\fP
+List all available packages belonging to selected modules.
+.TP
+.B \fBdnf [options] module repoquery \-\-installed <module\-spec>...\fP
+List all installed packages with same name like packages belonging to selected modules.
+.UNINDENT
+.SS Provides Command
+.nf
+Command: \fBprovides\fP
+Aliases: \fBprov\fP, \fBwhatprovides\fP, \fBwp\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] provides <provide\-spec>\fP
+Finds the packages providing the given \fB<provide\-spec>\fP\&. This is useful
+when one knows a filename and wants to find what package (installed or not)
+provides this file.
+The \fB<provide\-spec>\fP is gradually looked for at following locations:
+.INDENT 7.0
+.IP 1. 3
+The \fB<provide\-spec>\fP is matched with all file provides of any available package:
+.INDENT 3.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+$ dnf provides /usr/bin/gzip
+gzip\-1.9\-9.fc29.x86_64 : The GNU data compression program
+Matched from:
+Filename    : /usr/bin/gzip
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.IP 2. 3
+Then all provides of all available packages are searched:
+.INDENT 3.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+$ dnf provides "gzip(x86\-64)"
+gzip\-1.9\-9.fc29.x86_64 : The GNU data compression program
+Matched from:
+Provide     : gzip(x86\-64) = 1.9\-9.fc29
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.IP 3. 3
+DNF assumes that the \fB<provide\-spec>\fP is a system command, prepends it with \fB/usr/bin/\fP, \fB/usr/sbin/\fP prefixes (one at a time) and does the file provides search again. For legacy reasons (packages that didn\(aqt do UsrMove) also \fB/bin\fP and \fB/sbin\fP prefixes are being searched:
+.INDENT 3.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+$ dnf provides zless
+gzip\-1.9\-9.fc29.x86_64 : The GNU data compression program
+Matched from:
+Filename    : /usr/bin/zless
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.IP 4. 3
+If this last step also fails, DNF returns "Error: No Matches found".
+.UNINDENT
+.sp
+This command by default does not force a sync of expired metadata. See also \fI\%Metadata Synchronization\fP\&.
+.UNINDENT
+.SS Reinstall Command
+.nf
+Command: \fBreinstall\fP
+Aliases: \fBrei\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] reinstall <package\-spec>...\fP
+Installs the specified packages, fails if some of the packages are either
+not installed or not available (i.e. there is no repository where to
+download the same RPM).
+.UNINDENT
+.SS Remove Command
+.nf
+Command: \fBremove\fP
+Aliases: \fBrm\fP
+Aliases for \fI\%explicit NEVRA matching\fP: \fBremove\-n\fP, \fBremove\-na\fP, \fBremove\-nevra\fP
+Deprecated aliases: \fBerase\fP, \fBerase\-n\fP, \fBerase\-na\fP, \fBerase\-nevra\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] remove <package\-spec>...\fP
+Removes the specified packages from the system along with any packages depending on the packages being removed. Each \fB<spec>\fP can be either a \fB<package\-spec>\fP, which specifies a package directly, or a \fB@<group\-spec>\fP, which specifies an (environment) group which contains it. If \fBclean_requirements_on_remove\fP is enabled (the default), also removes any dependencies that are no longer needed.
+.TP
+.B \fBdnf [options] remove \-\-duplicates\fP
+Removes older versions of duplicate packages. To ensure the integrity of the system it
+reinstalls the newest package. In some cases the command cannot resolve conflicts. In such cases
+the \fI\%dnf shell\fP command with \fBremove \-\-duplicates\fP and \fBupgrade\fP
+dnf\-shell sub\-commands could help.
+.TP
+.B \fBdnf [options] remove \-\-oldinstallonly\fP
+Removes old installonly packages, keeping only latest versions and version of running kernel.
+.sp
+There are also a few specific remove commands \fBremove\-n\fP, \fBremove\-na\fP and \fBremove\-nevra\fP
+that allow the specification of an exact argument in the NEVRA format.
+.UNINDENT
+.SS Remove Examples
+.INDENT 0.0
+.TP
+.B \fBdnf remove acpi tito\fP
+Remove the \fBacpi\fP and \fBtito\fP packages.
+.TP
+.B \fBdnf remove $(dnf repoquery \-\-extras \-\-exclude=tito,acpi)\fP
+Remove packages not present in any repository, but don\(aqt remove the \fBtito\fP
+and \fBacpi\fP packages (they still might be removed if they depend on some of the removed packages).
+.UNINDENT
+.sp
+Remove older versions of duplicated packages (an equivalent of yum\(aqs \fIpackage\-cleanup \-\-cleandups\fP):
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf remove \-\-duplicates
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS Repoinfo Command
+.nf
+Command: \fBrepoinfo\fP
+.fi
+.sp
+.INDENT 0.0
+.INDENT 3.5
+An alias for the \fI\%repolist\fP command
+that provides more detailed information like \fBdnf repolist \-v\fP\&.
+.UNINDENT
+.UNINDENT
+.SS Repolist Command
+.nf
+Command: \fBrepolist\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] repolist [\-\-enabled|\-\-disabled|\-\-all]\fP
+Depending on the exact command lists enabled, disabled or all known
+repositories. Lists all enabled repositories by default. Provides more
+detailed information when \fB\-v\fP option is used.
+.UNINDENT
+.sp
+This command by default does not force a sync of expired metadata. See also \fI\%Metadata Synchronization\fP\&.
+.SS Repoquery Command
+.nf
+Command: \fBrepoquery\fP
+Aliases: \fBrq\fP
+Aliases for \fI\%explicit NEVRA matching\fP: \fBrepoquery\-n\fP, \fBrepoquery\-na\fP, \fBrepoquery\-nevra\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] repoquery [<select\-options>] [<query\-options>] [<package\-file\-spec>]\fP
+Searches available DNF repositories for selected packages and displays the requested information about them. It
+is an equivalent of \fBrpm \-q\fP for remote repositories.
+.TP
+.B \fBdnf [options] repoquery \-\-groupmember <package\-spec>...\fP
+List groups that contain <package\-spec>.
+.TP
+.B \fBdnf [options] repoquery \-\-querytags\fP
+Provides the list of tags recognized by the \-\fI\%\-queryformat\fP repoquery option.
+.sp
+There are also a few specific repoquery commands \fBrepoquery\-n\fP, \fBrepoquery\-na\fP and \fBrepoquery\-nevra\fP
+that allow the specification of an exact argument in the NEVRA format (does not affect arguments of options like \-\-whatprovides <arg>, ...).
+.UNINDENT
+.SS Select Options
+.sp
+Together with \fB<package\-file\-spec>\fP, control what packages are displayed in the output. If \fB<package\-file\-spec>\fP is given, limits the resulting set of
+packages to those matching the specification. All packages are considered if no \fB<package\-file\-spec>\fP is specified.
+.INDENT 0.0
+.TP
+.B \fB<package\-file\-spec>\fP
+Package specification in the NEVRA format (name[\-[epoch:]version[\-release]][.arch]), a package provide or a file provide. See \fI\%Specifying Packages\fP\&.
+.TP
+.B \fB\-a\fP, \fB\-\-all\fP
+Query all packages (for rpmquery compatibility, also a shorthand for repoquery \(aq*\(aq or repoquery
+without arguments).
+.TP
+.B \fB\-\-arch <arch>[,<arch>...], \-\-archlist <arch>[,<arch>...]\fP
+Limit the resulting set only to packages of selected architectures (default is all
+architectures). In some cases the result is affected by the basearch of the running system, therefore
+to run repoquery for an arch incompatible with your system use the \fB\-\-forcearch=<arch>\fP
+option to change the basearch.
+.TP
+.B \fB\-\-duplicates\fP
+Limit the resulting set to installed duplicate packages (i.e. more package versions
+for the same name and architecture). Installonly packages are excluded from this set.
+.TP
+.B \fB\-\-unneeded\fP
+Limit the resulting set to leaves packages that were installed as dependencies so they are no longer needed. This
+switch lists packages that are going to be removed after executing the \fBdnf autoremove\fP command.
+.TP
+.B \fB\-\-available\fP
+Limit the resulting set to available packages only (set by default).
+.TP
+.B \fB\-\-disable\-modular\-filtering\fP
+Disables filtering of modular packages, so that packages of inactive module streams are included in the result.
+.TP
+.B \fB\-\-extras\fP
+Limit the resulting set to packages that are not present in any of the available repositories.
+.TP
+.B \fB\-f <file>\fP, \fB\-\-file <file>\fP
+Limit the resulting set only to the package that owns \fB<file>\fP\&.
+.TP
+.B \fB\-\-installed\fP
+Limit the resulting set to installed packages only. The exclude option in the configuration file
+might influence the result, but if the command line option  \-\fI\%\-disableexcludes\fP is used, it ensures that all installed packages will be listed.
+.TP
+.B \fB\-\-installonly\fP
+Limit the resulting set to installed installonly packages.
+.TP
+.B \fB\-\-latest\-limit <number>\fP
+Limit the resulting set to <number> of latest packages for every package name and architecture.
+If <number> is negative, skip <number> of latest packages. For a negative <number> use the
+\fB\-\-latest\-limit=<number>\fP syntax.
+.TP
+.B \fB\-\-recent\fP
+Limit the resulting set to packages that were recently edited.
+.TP
+.B \fB\-\-repo <repoid>\fP
+Limit the resulting set only to packages from a repository identified by \fB<repoid>\fP\&.
+Can be used multiple times with accumulative effect.
+.TP
+.B \fB\-\-unsatisfied\fP
+Report unsatisfied dependencies among installed packages (i.e. missing requires and
+existing conflicts).
+.TP
+.B \fB\-\-upgrades\fP
+Limit the resulting set to packages that provide an upgrade for some already installed package.
+.TP
+.B \fB\-\-userinstalled\fP
+Limit the resulting set to packages installed by the user. The exclude option
+in the configuration file might influence the result, but if the command line option  \-\fI\%\-disableexcludes\fP is used, it ensures that all installed packages will be listed.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-whatdepends <capability>[,<capability>...]\fP
+Limit the resulting set only to packages that require, enhance, recommend, suggest or
+supplement any of \fB<capabilities>\fP\&.
+.TP
+.B \fB\-\-whatconflicts <capability>[,<capability>...]\fP
+Limit the resulting set only to packages that conflict with any of \fB<capabilities>\fP\&.
+.TP
+.B \fB\-\-whatenhances <capability>[,<capability>...]\fP
+Limit the resulting set only to packages that enhance any of \fB<capabilities>\fP\&. Use \-\fI\%\-whatdepends\fP if you want to list all depending packages.
+.TP
+.B \fB\-\-whatobsoletes <capability>[,<capability>...]\fP
+Limit the resulting set only to packages that obsolete any of \fB<capabilities>\fP\&.
+.TP
+.B \fB\-\-whatprovides <capability>[,<capability>...]\fP
+Limit the resulting set only to packages that provide any of \fB<capabilities>\fP\&.
+.TP
+.B \fB\-\-whatrecommends <capability>[,<capability>...]\fP
+Limit the resulting set only to packages that recommend any of \fB<capabilities>\fP\&. Use \-\fI\%\-whatdepends\fP if you want to list all depending packages.
+.TP
+.B \fB\-\-whatrequires <capability>[,<capability>...]\fP
+Limit the resulting set only to packages that require any of \fB<capabilities>\fP\&. Use \-\fI\%\-whatdepends\fP if you want to list all depending packages.
+.TP
+.B \fB\-\-whatsuggests <capability>[,<capability>...]\fP
+Limit the resulting set only to packages that suggest any of \fB<capabilities>\fP\&. Use \-\fI\%\-whatdepends\fP if you want to list all depending packages.
+.TP
+.B \fB\-\-whatsupplements <capability>[,<capability>...]\fP
+Limit the resulting set only to packages that supplement any of \fB<capabilities>\fP\&. Use \-\fI\%\-whatdepends\fP if you want to list all depending packages.
+.TP
+.B \fB\-\-alldeps\fP
+This option is stackable with \fB\-\-whatrequires\fP or \-\fI\%\-whatdepends\fP only. Additionally it adds all packages requiring
+the package features to the result set (used as default).
+.TP
+.B \fB\-\-exactdeps\fP
+This option is stackable with \fB\-\-whatrequires\fP or \-\fI\%\-whatdepends\fP only. Limit the resulting set only to packages
+that require \fB<capability>\fP specified by \-\-whatrequires.
+.TP
+.B \fB\-\-srpm\fP
+Operate on the corresponding source RPM.
+.UNINDENT
+.SS Query Options
+.sp
+Set what information is displayed about each package.
+.sp
+The following are mutually exclusive, i.e. at most one can be specified. If no query option is given, matching packages
+are displayed in the standard NEVRA notation.
+.INDENT 0.0
+.TP
+.B \fB\-i, \-\-info\fP
+Show detailed information about the package.
+.TP
+.B \fB\-l, \-\-list\fP
+Show the list of files in the package.
+.TP
+.B \fB\-s, \-\-source\fP
+Show the package source RPM name.
+.TP
+.B \fB\-\-changelogs\fP
+Print the package changelogs.
+.TP
+.B \fB\-\-conflicts\fP
+Display capabilities that the package conflicts with. Same as \fB\-\-qf "%{conflicts}\fP\&.
+.TP
+.B \fB\-\-depends\fP
+Display capabilities that the package depends on, enhances, recommends, suggests or
+supplements.
+.TP
+.B \fB\-\-enhances\fP
+Display capabilities enhanced by the package. Same as \fB\-\-qf "%{enhances}""\fP\&.
+.TP
+.B \fB\-\-location\fP
+Show a location where the package could be downloaded from.
+.TP
+.B \fB\-\-obsoletes\fP
+Display capabilities that the package obsoletes. Same as \fB\-\-qf "%{obsoletes}"\fP\&.
+.TP
+.B \fB\-\-provides\fP
+Display capabilities provided by the package. Same as \fB\-\-qf "%{provides}"\fP\&.
+.TP
+.B \fB\-\-recommends\fP
+Display capabilities recommended by the package. Same as \fB\-\-qf "%{recommends}"\fP\&.
+.TP
+.B \fB\-\-requires\fP
+Display capabilities that the package depends on. Same as \fB\-\-qf "%{requires}"\fP\&.
+.TP
+.B \fB\-\-requires\-pre\fP
+Display capabilities that the package depends on for running a \fB%pre\fP script.
+Same as \fB\-\-qf "%{requires\-pre}"\fP\&.
+.TP
+.B \fB\-\-suggests\fP
+Display capabilities suggested by the package. Same as \fB\-\-qf "%{suggests}"\fP\&.
+.TP
+.B \fB\-\-supplements\fP
+Display capabilities supplemented by the package. Same as \fB\-\-qf "%{supplements}"\fP\&.
+.TP
+.B \fB\-\-tree\fP
+Display a recursive tree of packages with capabilities specified by one of the following supplementary options:
+\fB\-\-whatrequires\fP, \fB\-\-requires\fP, \fB\-\-conflicts\fP, \fB\-\-enhances\fP, \fB\-\-suggests\fP, \fB\-\-provides\fP,
+\fB\-\-supplements\fP, \fB\-\-recommends\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-deplist\fP
+Produce a list of all direct dependencies and what packages provide those
+dependencies for the given packages. The result only shows the newest
+providers (which can be changed by using \-\-verbose).
+.TP
+.B \fB\-\-nvr\fP
+Show found packages in the name\-version\-release format. Same as
+\fB\-\-qf "%{name}\-%{version}\-%{release}"\fP\&.
+.TP
+.B \fB\-\-nevra\fP
+Show found packages in the name\-epoch:version\-release.architecture format. Same as
+\fB\-\-qf "%{name}\-%{epoch}:%{version}\-%{release}.%{arch}"\fP (default).
+.TP
+.B \fB\-\-envra\fP
+Show found packages in the epoch:name\-version\-release.architecture format. Same as
+\fB\-\-qf "%{epoch}:%{name}\-%{version}\-%{release}.%{arch}"\fP
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-qf <format>\fP, \fB\-\-queryformat <format>\fP
+Custom display format. \fB<format>\fP is the string to output for each matched package. Every occurrence of
+\fB%{<tag>}\fP within is replaced by the corresponding attribute of the package. The list of recognized tags can be displayed
+by running \fBdnf repoquery \-\-querytags\fP\&.
+.TP
+.B \fB\-\-recursive\fP
+Query packages recursively. Has to be used with \fB\-\-whatrequires <REQ>\fP
+(optionally with \fB\-\-alldeps\fP, but not with \fB\-\-exactdeps\fP) or with
+\fB\-\-requires <REQ> \-\-resolve\fP\&.
+.TP
+.B \fB\-\-resolve\fP
+resolve capabilities to originating package(s).
+.UNINDENT
+.SS Examples
+.sp
+Display NEVRAs of all available packages matching \fBlight*\fP:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery \(aqlight*\(aq
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Display NEVRAs of all available packages matching name \fBlight*\fP and architecture \fBnoarch\fP (accepts only arguments in the "<name>.<arch>" format):
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery\-na \(aqlight*.noarch\(aq
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Display requires of all lighttpd packages:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery \-\-requires lighttpd
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Display packages providing the requires of python packages:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery \-\-requires python \-\-resolve
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Display source rpm of ligttpd package:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery \-\-source lighttpd
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Display package name that owns the given file:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery \-\-file /etc/lighttpd/lighttpd.conf
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Display name, architecture and the containing repository of all lighttpd packages:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery \-\-queryformat \(aq%{name}.%{arch} : %{reponame}\(aq lighttpd
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Display all available packages providing "webserver":
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery \-\-whatprovides webserver
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Display all available packages providing "webserver" but only for "i686" architecture:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery \-\-whatprovides webserver \-\-arch i686
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Display duplicate packages:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery \-\-duplicates
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Display source packages that require a <provide> for a build:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery \-\-disablerepo="*" \-\-enablerepo="*\-source" \-\-arch=src \-\-whatrequires <provide>
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS Repository\-Packages Command
+.nf
+Command: \fBrepository\-packages\fP
+Deprecated aliases: \fBrepo\-pkgs\fP, \fBrepo\-packages\fP, \fBrepository\-pkgs\fP
+.fi
+.sp
+.sp
+The repository\-packages command allows the user to run commands on top of all packages in the repository named \fB<repoid>\fP\&. However, any dependency resolution takes into account packages from all enabled repositories. The \fB<package\-file\-spec>\fP and \fB<package\-spec>\fP specifications further limit the candidates to only those packages matching at least one of them.
+.sp
+The \fBinfo\fP subcommand lists description and summary information about packages depending on the packages\(aq relation to the repository. The \fBlist\fP subcommand just prints lists of those packages.
+.INDENT 0.0
+.TP
+.B \fBdnf [options] repository\-packages <repoid> check\-update [<package\-file\-spec>...]\fP
+Non\-interactively checks if updates of the specified packages in the repository are available. DNF exit code will be 100 when there are updates available and a list of the updates will be printed.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> info [\-\-all] [<package\-file\-spec>...]\fP
+List all related packages.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> info \-\-installed [<package\-file\-spec>...]\fP
+List packages installed from the repository.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> info \-\-available [<package\-file\-spec>...]\fP
+List packages available in the repository but not currently installed on the system.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> info \-\-extras [<package\-file\-specs>...]\fP
+List packages installed from the repository that are not available in any repository.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> info \-\-obsoletes [<package\-file\-spec>...]\fP
+List packages in the repository that obsolete packages installed on the system.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> info \-\-recent [<package\-file\-spec>...]\fP
+List packages recently added into the repository.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> info \-\-upgrades [<package\-file\-spec>...]\fP
+List packages in the repository that upgrade packages installed on the system.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> install [<package\-spec>...]\fP
+Install packages matching \fB<package\-spec>\fP from the repository. If \fB<package\-spec>\fP isn\(aqt specified at all, install all packages from the repository.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> list [\-\-all] [<package\-file\-spec>...]\fP
+List all related packages.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> list \-\-installed [<package\-file\-spec>...]\fP
+List packages installed from the repository.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> list \-\-available [<package\-file\-spec>...]\fP
+List packages available in the repository but not currently installed on the system.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> list \-\-extras [<package\-file\-spec>...]\fP
+List packages installed from the repository that are not available in any repository.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> list \-\-obsoletes [<package\-file\-spec>...]\fP
+List packages in the repository that obsolete packages installed on the system.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> list \-\-recent [<package\-file\-spec>...]\fP
+List packages recently added into the repository.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> list \-\-upgrades [<package\-file\-spec>...]\fP
+List packages in the repository that upgrade packages installed on the system.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> move\-to [<package\-spec>...]\fP
+Reinstall all those packages that are available in the repository.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> reinstall [<package\-spec>...]\fP
+Run the \fBreinstall\-old\fP subcommand. If it fails, run the \fBmove\-to\fP subcommand.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> reinstall\-old [<package\-spec>...]\fP
+Reinstall all those packages that were installed from the repository and simultaneously are available in the repository.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> remove [<package\-spec>...]\fP
+Remove all packages installed from the repository along with any packages depending on the packages being removed. If \fBclean_requirements_on_remove\fP is enabled (the default) also removes any dependencies that are no longer needed.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> remove\-or\-distro\-sync [<package\-spec>...]\fP
+Select all packages installed from the repository. Upgrade, downgrade or keep those of them that are available in another repository to match the latest version available there and remove the others along with any packages depending on the packages being removed. If \fBclean_requirements_on_remove\fP is enabled (the default) also removes any dependencies that are no longer needed.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> remove\-or\-reinstall [<package\-spec>...]\fP
+Select all packages installed from the repository. Reinstall those of them that are available in another repository and remove the others along with any packages depending on the packages being removed. If \fBclean_requirements_on_remove\fP is enabled (the default) also removes any dependencies that are no longer needed.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> upgrade [<package\-spec>...]\fP
+Update all packages to the highest resolvable version available in the repository.
+When versions are specified in the \fB<package\-spec>\fP, update to these versions.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> upgrade\-to [<package\-specs>...]\fP
+A deprecated alias for the upgrade subcommand.
+.UNINDENT
+.SS Search Command
+.nf
+Command: \fBsearch\fP
+Aliases: \fBse\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] search [\-\-all] <keywords>...\fP
+Search package metadata for keywords. Keywords are matched as case\-insensitive substrings, globbing is supported.
+By default lists packages that match all requested keys (AND operation). Keys are searched in package names and summaries.
+If the "\-\-all" option is used, lists packages that match at least one of the keys (an OR operation).
+In addition the keys are searched in the package descriptions and URLs.
+The result is sorted from the most relevant results to the least.
+.UNINDENT
+.sp
+This command by default does not force a sync of expired metadata. See also \fI\%Metadata Synchronization\fP\&.
+.SS Shell Command
+.nf
+Command: \fBshell\fP
+Aliases: \fBsh\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] shell [filename]\fP
+Open an interactive shell for conducting multiple commands during a single execution of DNF. These commands can be issued manually
+or passed to DNF from a file. The commands are much the same as the normal DNF command line options. There are a few additional
+commands documented below.
+.INDENT 7.0
+.TP
+.B \fBconfig [conf\-option] [value]\fP
+.INDENT 7.0
+.IP \(bu 2
+Set a configuration option to a requested value. If no value is given it prints the current value.
+.UNINDENT
+.TP
+.B \fBrepo [list|enable|disable] [repo\-id]\fP
+.INDENT 7.0
+.IP \(bu 2
+list: list repositories and their status
+.IP \(bu 2
+enable: enable repository
+.IP \(bu 2
+disable: disable repository
+.UNINDENT
+.TP
+.B \fBtransaction [list|reset|solve|run]\fP
+.INDENT 7.0
+.IP \(bu 2
+list: resolve and list the content of the transaction
+.IP \(bu 2
+reset: reset the transaction
+.IP \(bu 2
+run: resolve and run the transaction
+.UNINDENT
+.UNINDENT
+.sp
+Note that all local packages must be used in the first shell transaction subcommand (e.g.
+\fIinstall /tmp/nodejs\-1\-1.x86_64.rpm /tmp/acpi\-1\-1.noarch.rpm\fP) otherwise an error will occur.
+Any \fIdisable\fP, \fIenable\fP, and \fIreset\fP module operations (e.g. \fImodule enable nodejs\fP) must also
+be performed before any other shell transaction subcommand is used.
+.UNINDENT
+.SS Swap Command
+.nf
+Command: \fBswap\fP
+.fi
+.sp
+.sp
+\fBdnf [options] swap <remove\-spec> <install\-spec>\fP
+.INDENT 0.0
+.INDENT 3.5
+Remove spec and install spec in one transaction. Each \fB<spec>\fP can be either a
+\fI\%<package\-spec>\fP, which specifies a package directly, or a
+\fB@<group\-spec>\fP, which specifies an (environment) group which contains it. Automatic
+conflict solving is provided in DNF by the \-\-allowerasing option that provides the functionality of the swap
+command automatically.
+.UNINDENT
+.UNINDENT
+.SS Updateinfo Command
+.nf
+Command: \fBupdateinfo\fP
+Aliases: \fBupif\fP
+Deprecated aliases: \fBlist\-updateinfo\fP, \fBlist\-security\fP, \fBlist\-sec\fP, \fBinfo\-updateinfo\fP, \fBinfo\-security\fP, \fBinfo\-sec\fP, \fBsummary\-updateinfo\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] updateinfo [\-\-summary|\-\-list|\-\-info] [<availability>] [<spec>...]\fP
+Display information about update advisories.
+.sp
+Depending on the output type, DNF displays just counts of advisory types
+(omitted or \fB\-\-summary\fP), list of advisories (\fB\-\-list\fP) or detailed
+information (\fB\-\-info\fP). The \fB\-v\fP option extends the output. When
+used with \fB\-\-info\fP, the information is even more detailed. When used
+with \fB\-\-list\fP, an additional column with date of the last advisory update
+is added.
+.sp
+\fB<availability>\fP specifies whether advisories about newer versions of
+installed packages (omitted or \fB\-\-available\fP), advisories about equal and
+older versions of installed packages (\fB\-\-installed\fP), advisories about
+newer versions of those installed packages for which a newer version is
+available (\fB\-\-updates\fP) or advisories about any versions of installed
+packages (\fB\-\-all\fP) are taken into account. Most of the time, \fB\-\-available\fP
+and \fB\-\-updates\fP displays the same output. The outputs differ only in the
+cases when an advisory refers to a newer version but there is no enabled
+repository which contains any newer version.
+.sp
+Note, that \fB\-\-available\fP takes only the latest installed versions of
+packages into account. In case of the kernel packages (when multiple
+version could be installed simultaneously) also packages of the currently
+running version of kernel are added.
+.sp
+To print only advisories referencing a CVE or a bugzilla use \fB\-\-with\-cve\fP or
+\fB\-\-with\-bz\fP options. When these switches are used also the output
+of the \fB\-\-list\fP is altered \- the ID of the CVE or the bugzilla is printed
+instead of the one of the advisory.
+.sp
+If given and if neither ID, type (\fBbugfix\fP, \fBenhancement\fP,
+\fBsecurity\fP/\fBsec\fP) nor a package name of an advisory matches
+\fB<spec>\fP, the advisory is not taken into account. The matching is
+case\-sensitive and in the case of advisory IDs and package names, globbing
+is supported.
+.sp
+Output of the \fB\-\-summary\fP option is affected by the autocheck_running_kernel configuration option.
+.UNINDENT
+.SS Upgrade Command
+.nf
+Command: \fBupgrade\fP
+Aliases: \fBup\fP
+Deprecated aliases: \fBupdate\fP, \fBupgrade\-to\fP, \fBupdate\-to\fP, \fBlocalupdate\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] upgrade\fP
+Updates each package to the latest version that is both available and
+resolvable.
+.TP
+.B \fBdnf [options] upgrade <package\-spec>...\fP
+Updates each specified package to the latest available version. Updates
+dependencies as necessary. When versions are specified in the
+\fB<package\-spec>\fP, update to these versions.
+.TP
+.B \fBdnf [options] upgrade @<spec>...\fP
+Alias for the \fIdnf module update\fP command.
+.UNINDENT
+.sp
+If the main \fBobsoletes\fP configure option is true or the \fB\-\-obsoletes\fP flag
+is present, dnf will include package obsoletes in its calculations.
+For more information see obsoletes\&.
+.sp
+See also \fI\%Configuration Files Replacement Policy\fP\&.
+.SS Upgrade\-Minimal Command
+.nf
+Command: \fBupgrade\-minimal\fP
+Aliases: \fBup\-min\fP
+Deprecated aliases: \fBupdate\-minimal\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] upgrade\-minimal\fP
+Updates each package to the latest available version that provides a bugfix, enhancement
+or a fix for a security issue (security).
+.TP
+.B \fBdnf [options] upgrade\-minimal <package\-spec>...\fP
+Updates each specified package to the latest available version that provides
+a bugfix, enhancement or a fix for security issue (security). Updates
+dependencies as necessary.
+.UNINDENT
+.SH SPECIFYING PACKAGES
+.sp
+Many commands take a \fB<package\-spec>\fP parameter that selects a package for
+the operation. The \fB<package\-spec>\fP argument is matched against package
+NEVRAs, provides and file provides.
+.sp
+\fB<package\-file\-spec>\fP is similar to \fB<package\-spec>\fP, except provides
+matching is not performed. Therefore, \fB<package\-file\-spec>\fP is matched only
+against NEVRAs and file provides.
+.sp
+\fB<package\-name\-spec>\fP is matched against NEVRAs only.
+.SS Globs
+.sp
+Package specification supports the same glob pattern matching that shell does,
+in all three above mentioned packages it matches against (NEVRAs, provides and
+file provides).
+.sp
+The following patterns are supported:
+.INDENT 0.0
+.TP
+.B \fB*\fP
+Matches any number of characters.
+.TP
+.B \fB?\fP
+Matches any single character.
+.TP
+.B \fB[]\fP
+Matches any one of the enclosed characters. A pair of characters separated
+by a hyphen denotes a range expression; any character that falls between
+those two characters, inclusive, is matched. If the first character
+following the \fB[\fP is a \fB!\fP or a \fB^\fP then any character not enclosed
+is matched.
+.UNINDENT
+.sp
+Note: Curly brackets (\fB{}\fP) are not supported. You can still use them in
+shells that support them and let the shell do the expansion, but if quoted or
+escaped, dnf will not expand them.
+.SS NEVRA Matching
+.sp
+When matching against NEVRAs, partial matching is supported. DNF tries to match
+the spec against the following list of NEVRA forms (in decreasing order of
+priority):
+.INDENT 0.0
+.IP \(bu 2
+\fBname\-[epoch:]version\-release.arch\fP
+.IP \(bu 2
+\fBname.arch\fP
+.IP \(bu 2
+\fBname\fP
+.IP \(bu 2
+\fBname\-[epoch:]version\-release\fP
+.IP \(bu 2
+\fBname\-[epoch:]version\fP
+.UNINDENT
+.sp
+Note that \fBname\fP can in general contain dashes (e.g. \fBpackage\-with\-dashes\fP).
+.sp
+The first form that matches any packages is used and the remaining forms are
+not tried. If none of the forms match any packages, an attempt is made to match
+the \fB<package\-spec>\fP against full package NEVRAs. This is only relevant
+if globs are present in the \fB<package\-spec>\fP\&.
+.sp
+\fB<package\-spec>\fP matches NEVRAs the same way \fB<package\-name\-spec>\fP does,
+but in case matching NEVRAs fails, it attempts to match against provides and
+file provides of packages as well.
+.sp
+You can specify globs as part of any of the five NEVRA components. You can also
+specify a glob pattern to match over multiple NEVRA components (in other words,
+to match across the NEVRA separators). In that case, however, you need to write
+the spec to match against full package NEVRAs, as it is not possible to split
+such spec into NEVRA forms.
+.SS Specifying NEVRA Matching Explicitly
+.sp
+Some commands (\fBautoremove\fP, \fBinstall\fP, \fBremove\fP and \fBrepoquery\fP) also
+have aliases with suffixes \fB\-n\fP, \fB\-na\fP and \fB\-nevra\fP that allow to
+explicitly specify how to parse the arguments:
+.INDENT 0.0
+.IP \(bu 2
+Command \fBinstall\-n\fP only matches against \fBname\fP\&.
+.IP \(bu 2
+Command \fBinstall\-na\fP only matches against \fBname.arch\fP\&.
+.IP \(bu 2
+Command \fBinstall\-nevra\fP only matches against \fBname\-[epoch:]version\-release.arch\fP\&.
+.UNINDENT
+.SH SPECIFYING PROVIDES
+.sp
+\fB<provide\-spec>\fP in command descriptions means the command operates on
+packages providing the given spec. This can either be an explicit provide, an
+implicit provide (i.e. name of the package) or a file provide. The selection is
+case\-sensitive and globbing is supported.
+.SS Specifying File Provides
+.sp
+If a spec starts with either \fB/\fP or \fB*/\fP, it is considered as a potential file provide.
+.SH SPECIFYING GROUPS
+.sp
+\fB<group\-spec>\fP allows one to select (environment) groups a particular operation should work
+on. It is a case insensitive string (supporting globbing characters) that is
+matched against a group\(aqs ID, canonical name and name translated into the
+current LC_MESSAGES locale (if possible).
+.SH SPECIFYING MODULES
+.sp
+\fB<module\-spec>\fP allows one to select modules or profiles a particular operation should work
+on.
+.sp
+It is in the form of \fBNAME:STREAM:VERSION:CONTEXT:ARCH/PROFILE\fP and supported partial forms are the following:
+.INDENT 0.0
+.IP \(bu 2
+\fBNAME\fP
+.IP \(bu 2
+\fBNAME:STREAM\fP
+.IP \(bu 2
+\fBNAME:STREAM:VERSION\fP
+.IP \(bu 2
+\fBNAME:STREAM:VERSION:CONTEXT\fP
+.IP \(bu 2
+all above combinations with \fB::ARCH\fP (e.g. \fBNAME::ARCH\fP)
+.IP \(bu 2
+\fBNAME:STREAM:VERSION:CONTEXT:ARCH\fP
+.IP \(bu 2
+all above combinations with \fB/PROFILE\fP (e.g. \fBNAME/PROFILE\fP)
+.UNINDENT
+.sp
+In case stream is not specified, the enabled or the default stream is used, in this order. In case profile is not specified, the system default profile or the \(aqdefault\(aq profile is used.
+.SH SPECIFYING TRANSACTIONS
+.sp
+\fB<transaction\-spec>\fP can be in one of several forms. If it is an integer, it
+specifies a transaction ID. Specifying \fBlast\fP is the same as specifying the ID
+of the most recent transaction. The last form is \fBlast\-<offset>\fP, where
+\fB<offset>\fP is a positive integer. It specifies offset\-th transaction preceding
+the most recent transaction.
+.SH PACKAGE FILTERING
+.sp
+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.
+.SS Exclude Filtering
+.sp
+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 \-\fI\%\-disableexcludes\fP
+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 \-\fI\%\-disableplugin\fP command line option.
+.sp
+To disable all excludes for e.g. the install command you can use the following combination
+of command line options:
+.sp
+\fBdnf \-\-disableexcludes=all \-\-disableplugin="*" install bash\fP
+.SS Modular Filtering
+.sp
+Please see the modularity documentation for details on how Modular
+Filtering works.
+.sp
+With modularity, only RPM packages from \fBactive\fP module streams are included in the available
+package set. RPM packages from \fBinactive\fP module streams, as well as non\-modular packages with
+the same name or provides as a package from an \fBactive\fP module stream, are filtered out. Modular
+filtering is not applied to packages added from the command line, installed packages, or packages
+from repositories with \fBmodule_hotfixes=true\fP in their \fB\&.repo\fP file.
+.sp
+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
+\fBmodule_hotfixes=true\fP in the \fB\&.repo\fP file or use \fB\-\-setopt=<repo_id>.module_hotfixes=true\fP\&.
+.sp
+To discover the module which contains an excluded package use
+\fI\%dnf module provides\fP\&.
+.SH METADATA SYNCHRONIZATION
+.sp
+Correct operation of DNF depends on having access to up\-to\-date data from all enabled repositories but contacting remote mirrors on every operation considerably slows it down and costs bandwidth for both the client and the repository provider. The metadata_expire (see \fBdnf.conf(5)\fP) repository configuration option is used by DNF to determine whether a particular local copy of repository data is due to be re\-synced. It is crucial that the repository providers set the option well, namely to a value where it is guaranteed that if particular metadata was available in time \fBT\fP on the server, then all packages it references will still be available for download from the server in time \fBT + metadata_expire\fP\&.
+.sp
+To further reduce the bandwidth load, some of the commands where having up\-to\-date metadata is not critical (e.g. the \fBlist\fP command) do not look at whether a repository is expired and whenever any version of it is locally available to the user\(aqs account, it will be used. For non\-root use, see also the \fB\-\-cacheonly\fP switch. Note that in all situations the user can force synchronization of all enabled repositories with the \fB\-\-refresh\fP switch.
+.SH CONFIGURATION FILES REPLACEMENT POLICY
+.sp
+The updated packages could replace the old modified configuration files
+with the new ones or keep the older files. Neither of the files are actually replaced.
+To the conflicting ones RPM gives additional suffix to the origin name. Which file
+should maintain the true name after transaction is not controlled by package manager
+but is specified by each package itself, following packaging guideline.
+.SH FILES
+.INDENT 0.0
+.TP
+.B \fBCache Files\fP
+/var/cache/dnf
+.TP
+.B \fBMain Configuration\fP
+/etc/dnf/dnf.conf
+.TP
+.B \fBRepository\fP
+/etc/yum.repos.d/
+.UNINDENT
+.SH SEE ALSO
+.INDENT 0.0
+.IP \(bu 2
+\fBdnf.conf(5)\fP, DNF Configuration Reference
+.IP \(bu 2
+\fBdnf\-PLUGIN(8)\fP for documentation on DNF plugins.
+.IP \(bu 2
+\fBdnf.modularity(7)\fP, Modularity overview\&.
+.IP \(bu 2
+\fBdnf\-transaction\-json(5)\fP, Stored Transaction JSON Format Specification\&.
+.IP \(bu 2
+\fI\%DNF\fP project homepage (\fI\%https://github.com/rpm\-software\-management/dnf/\fP)
+.IP \(bu 2
+How to report a bug (\fI\%https://github.com/rpm\-software\-management/dnf/wiki/Bug\-Reporting\fP)
+.IP \(bu 2
+\fI\%YUM\fP project homepage (\fI\%http://yum.baseurl.org/\fP)
+.UNINDENT
+.SH AUTHOR
+See AUTHORS in DNF source distribution.
+.SH COPYRIGHT
+2012-2022, Red Hat, Licensed under GPLv2+
+.\" Generated by docutils manpage writer.
+.
diff --git a/yum-shell.8 b/yum-shell.8
new file mode 100644
index 0000000..3be759a
--- /dev/null
+++ b/yum-shell.8
@@ -0,0 +1,2123 @@
+.\" Man page generated from reStructuredText.
+.
+.
+.nr rst2man-indent-level 0
+.
+.de1 rstReportMargin
+\\$1 \\n[an-margin]
+level \\n[rst2man-indent-level]
+level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
+-
+\\n[rst2man-indent0]
+\\n[rst2man-indent1]
+\\n[rst2man-indent2]
+..
+.de1 INDENT
+.\" .rstReportMargin pre:
+. RS \\$1
+. nr rst2man-indent\\n[rst2man-indent-level] \\n[an-margin]
+. nr rst2man-indent-level +1
+.\" .rstReportMargin post:
+..
+.de UNINDENT
+. RE
+.\" indent \\n[an-margin]
+.\" old: \\n[rst2man-indent\\n[rst2man-indent-level]]
+.nr rst2man-indent-level -1
+.\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
+.in \\n[rst2man-indent\\n[rst2man-indent-level]]u
+..
+.TH "YUM-SHELL" "8" "Apr 29, 2022" "4.12.0" "DNF"
+.SH NAME
+yum-shell \- redirecting to DNF Command Reference
+.SH SYNOPSIS
+.sp
+\fBdnf [options] <command> [<args>...]\fP
+.SH DESCRIPTION
+.sp
+\fI\%DNF\fP is the next upcoming major version of \fI\%YUM\fP, a package manager for RPM\-based Linux
+distributions. It roughly maintains CLI compatibility with YUM and defines a strict API for
+extensions and plugins.
+.sp
+Plugins can modify or extend features of DNF or provide additional CLI commands on top of those
+mentioned below. If you know the name of such a command (including commands mentioned below), you
+may find/install the package which provides it using the appropriate virtual provide in the form of
+\fBdnf\-command(<alias>)\fP, where \fB<alias>\fP is the name of the command; e.g.\(ga\(gadnf install
+\(aqdnf\-command(versionlock)\(aq\(ga\(ga installs a \fBversionlock\fP plugin. This approach also applies to
+specifying dependencies of packages that require a particular DNF command.
+.sp
+Return values:
+.INDENT 0.0
+.IP \(bu 2
+\fB0\fP  : Operation was successful.
+.IP \(bu 2
+\fB1\fP  : An error occurred, which was handled by dnf.
+.IP \(bu 2
+\fB3\fP  : An unknown unhandled error occurred during operation.
+.IP \(bu 2
+\fB100\fP: See \fI\%check\-update\fP
+.IP \(bu 2
+\fB200\fP: There was a problem with acquiring or releasing of locks.
+.UNINDENT
+.sp
+Available commands:
+.INDENT 0.0
+.IP \(bu 2
+\fI\%alias\fP
+.IP \(bu 2
+\fI\%autoremove\fP
+.IP \(bu 2
+\fI\%check\fP
+.IP \(bu 2
+\fI\%check\-update\fP
+.IP \(bu 2
+\fI\%clean\fP
+.IP \(bu 2
+\fI\%deplist\fP
+.IP \(bu 2
+\fI\%distro\-sync\fP
+.IP \(bu 2
+\fI\%downgrade\fP
+.IP \(bu 2
+\fI\%group\fP
+.IP \(bu 2
+\fI\%help\fP
+.IP \(bu 2
+\fI\%history\fP
+.IP \(bu 2
+\fI\%info\fP
+.IP \(bu 2
+\fI\%install\fP
+.IP \(bu 2
+\fI\%list\fP
+.IP \(bu 2
+\fI\%makecache\fP
+.IP \(bu 2
+\fI\%mark\fP
+.IP \(bu 2
+\fI\%module\fP
+.IP \(bu 2
+\fI\%provides\fP
+.IP \(bu 2
+\fI\%reinstall\fP
+.IP \(bu 2
+\fI\%remove\fP
+.IP \(bu 2
+\fI\%repoinfo\fP
+.IP \(bu 2
+\fI\%repolist\fP
+.IP \(bu 2
+\fI\%repoquery\fP
+.IP \(bu 2
+\fI\%repository\-packages\fP
+.IP \(bu 2
+\fI\%search\fP
+.IP \(bu 2
+\fI\%shell\fP
+.IP \(bu 2
+\fI\%swap\fP
+.IP \(bu 2
+\fI\%updateinfo\fP
+.IP \(bu 2
+\fI\%upgrade\fP
+.IP \(bu 2
+\fI\%upgrade\-minimal\fP
+.UNINDENT
+.sp
+Additional information:
+.INDENT 0.0
+.IP \(bu 2
+\fI\%Options\fP
+.IP \(bu 2
+\fI\%Specifying Packages\fP
+.IP \(bu 2
+\fI\%Specifying Provides\fP
+.IP \(bu 2
+\fI\%Specifying File Provides\fP
+.IP \(bu 2
+\fI\%Specifying Groups\fP
+.IP \(bu 2
+\fI\%Specifying Transactions\fP
+.IP \(bu 2
+\fI\%Metadata Synchronization\fP
+.IP \(bu 2
+\fI\%Configuration Files Replacement Policy\fP
+.IP \(bu 2
+\fI\%Files\fP
+.IP \(bu 2
+\fI\%See Also\fP
+.UNINDENT
+.SH OPTIONS
+.INDENT 0.0
+.TP
+.B \fB\-4\fP
+Resolve to IPv4 addresses only.
+.TP
+.B \fB\-6\fP
+Resolve to IPv6 addresses only.
+.TP
+.B \fB\-\-advisory=<advisory>, \-\-advisories=<advisory>\fP
+Include packages corresponding to the advisory ID, Eg. FEDORA\-2201\-123.
+Applicable for the install, repoquery, updateinfo and upgrade commands.
+.TP
+.B \fB\-\-allowerasing\fP
+Allow erasing of installed packages to resolve dependencies. This option could be used as an alternative to the \fByum swap\fP command where packages to remove are not explicitly defined.
+.TP
+.B \fB\-\-assumeno\fP
+Automatically answer no for all questions.
+.TP
+.B \fB\-b, \-\-best\fP
+Try the best available package versions in transactions. Specifically during \fI\%dnf upgrade\fP, which by default skips over updates that can not be installed for dependency reasons, the switch forces DNF to only consider the latest packages. When running into packages with broken dependencies, DNF will fail giving a reason why the latest version can not be installed.
+.sp
+Note that the use of the newest available version is only guaranteed for
+the packages directly requested (e.g. as a command line arguments), and the
+solver may use older versions of dependencies to meet their requirements.
+.TP
+.B \fB\-\-bugfix\fP
+Include packages that fix a bugfix issue. Applicable for the install, repoquery, updateinfo and
+upgrade commands.
+.TP
+.B \fB\-\-bz=<bugzilla>, \-\-bzs=<bugzilla>\fP
+Include packages that fix a Bugzilla ID, Eg. 123123. Applicable for the install, repoquery,
+updateinfo and upgrade commands.
+.TP
+.B \fB\-C, \-\-cacheonly\fP
+Run entirely from system cache, don\(aqt update the cache and use it even in case it is expired.
+.sp
+DNF uses a separate cache for each user under which it executes. The cache for the root user is called the system cache. This switch allows a regular user read\-only access to the system cache, which usually is more fresh than the user\(aqs and thus he does not have to wait for metadata sync.
+.TP
+.B \fB\-\-color=<color>\fP
+Control whether color is used in terminal output. Valid values are \fBalways\fP, \fBnever\fP and \fBauto\fP (default).
+.TP
+.B \fB\-\-comment=<comment>\fP
+Add a comment to the transaction history.
+.TP
+.B \fB\-c <config file>, \-\-config=<config file>\fP
+Configuration file location.
+.TP
+.B \fB\-\-cve=<cves>, \-\-cves=<cves>\fP
+Include packages that fix a CVE (Common Vulnerabilities and Exposures) ID
+(\fI\%http://cve.mitre.org/about/\fP), Eg. CVE\-2201\-0123. Applicable for the install, repoquery, updateinfo,
+and upgrade commands.
+.TP
+.B \fB\-d <debug level>, \-\-debuglevel=<debug level>\fP
+Debugging output level. This is an integer value between 0 (no additional information strings) and 10 (shows all debugging information, even that not understandable to the user), default is 2. Deprecated, use \fB\-v\fP instead.
+.TP
+.B \fB\-\-debugsolver\fP
+Dump data aiding in dependency solver debugging into \fB\&./debugdata\fP\&.
+.UNINDENT
+.sp
+\fB\-\-disableexcludes=[all|main|<repoid>], \-\-disableexcludepkgs=[all|main|<repoid>]\fP
+.INDENT 0.0
+.INDENT 3.5
+Disable the configuration file excludes. Takes one of the following three options:
+.INDENT 0.0
+.IP \(bu 2
+\fBall\fP, disables all configuration file excludes
+.IP \(bu 2
+\fBmain\fP, disables excludes defined in the \fB[main]\fP section
+.IP \(bu 2
+\fBrepoid\fP, disables excludes defined for the given repository
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-disable, \-\-set\-disabled\fP
+Disable specified repositories (automatically saves). The option has to be used together with the
+\fBconfig\-manager\fP command (dnf\-plugins\-core).
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-disableplugin=<plugin names>\fP
+Disable the listed plugins specified by names or globs.
+.TP
+.B \fB\-\-disablerepo=<repoid>\fP
+Temporarily disable active repositories for the purpose of the current dnf command.
+Accepts an id, a comma\-separated list of ids, or a glob of ids. This option can be
+specified multiple times, but is mutually exclusive with \fB\-\-repo\fP\&.
+.TP
+.B \fB\-\-downloaddir=<path>, \-\-destdir=<path>\fP
+Redirect downloaded packages to provided directory. The option has to be used together with the \-\fI\%\-downloadonly\fP command line option, with the
+\fBdownload\fP, \fBmodulesync\fP or \fBreposync\fP commands (dnf\-plugins\-core) or with the \fBsystem\-upgrade\fP command
+(dnf\-plugins\-extras).
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-downloadonly\fP
+Download the resolved package set without performing any rpm transaction (install/upgrade/erase).
+.TP
+.B \fB\-e <error level>, \-\-errorlevel=<error level>\fP
+Error output level. This is an integer value between 0 (no error output) and
+10 (shows all error messages), default is 3. Deprecated, use \fB\-v\fP instead.
+.TP
+.B \fB\-\-enable, \-\-set\-enabled\fP
+Enable specified repositories (automatically saves). The option has to be used together with the
+\fBconfig\-manager\fP command (dnf\-plugins\-core).
+.TP
+.B \fB\-\-enableplugin=<plugin names>\fP
+Enable the listed plugins specified by names or globs.
+.TP
+.B \fB\-\-enablerepo=<repoid>\fP
+Temporarily enable additional repositories for the purpose of the current dnf command.
+Accepts an id, a comma\-separated list of ids, or a glob of ids. This option can be
+specified multiple times.
+.TP
+.B \fB\-\-enhancement\fP
+Include enhancement relevant packages. Applicable for the install, repoquery, updateinfo and
+upgrade commands.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-x <package\-file\-spec>, \-\-exclude=<package\-file\-spec>\fP
+Exclude packages specified by \fB<package\-file\-spec>\fP from the operation.
+.TP
+.B \fB\-\-excludepkgs=<package\-file\-spec>\fP
+Deprecated option. It was replaced by the \-\fI\%\-exclude\fP option.
+.TP
+.B \fB\-\-forcearch=<arch>\fP
+Force the use of an architecture. Any architecture can be specified.
+However, use of an architecture not supported natively by your CPU will
+require emulation of some kind. This is usually through QEMU. The behavior of \fB\-\-forcearch\fP
+can be configured by using the arch and ignorearch
+configuration options with values \fB<arch>\fP and \fBTrue\fP respectively.
+.TP
+.B \fB\-h, \-\-help, \-\-help\-cmd\fP
+Show the help.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-installroot=<path>\fP
+Specifies an alternative installroot, relative to where all packages will be
+installed. Think of this like doing \fBchroot <root> dnf\fP, except using
+\fB\-\-installroot\fP allows dnf to work before the chroot is created. It requires absolute path.
+.UNINDENT
+.INDENT 0.0
+.IP \(bu 2
+\fIcachedir\fP, \fIlog files\fP, \fIreleasever\fP, and \fIgpgkey\fP are taken from or
+stored in the installroot. \fIGpgkeys\fP are imported into the installroot from
+a path relative to the host which can be specified in the repository section
+of configuration files.
+.IP \(bu 2
+\fIconfiguration file\fP and reposdir are searched inside the installroot first. If
+they are not present, they are taken from the host system.
+Note:  When a path is specified within a command line argument
+(\fB\-\-config=<config file>\fP in case of \fIconfiguration file\fP and
+\fB\-\-setopt=reposdir=<reposdir>\fP for \fIreposdir\fP) then this path is always
+relative to the host with no exceptions.
+.IP \(bu 2
+\fIvars\fP are taken from the host system or installroot according to reposdir
+\&. When \fIreposdir\fP path is specified within a command line argument, vars are taken from the
+installroot. When varsdir paths are specified within a command line
+argument (\fB\-\-setopt=varsdir=<reposdir>\fP) then those path are always relative to the host with no
+exceptions.
+.IP \(bu 2
+The \fIpluginpath\fP and \fIpluginconfpath\fP are relative to the host.
+.UNINDENT
+.INDENT 0.0
+.INDENT 3.5
+Note: You may also want to use the command\-line option
+\fB\-\-releasever=<release>\fP when creating the installroot, otherwise the
+\fI$releasever\fP value is taken from the rpmdb within the installroot (and thus
+it is empty at the time of creation and the transaction will fail). If \fB\-\-releasever=/\fP is used, the
+releasever will be detected from the host (\fB/\fP) system. The new installroot path at the time of creation
+does not contain the \fIrepository\fP, \fIreleasever\fP and \fIdnf.conf\fP files.
+.sp
+On a modular system you may also want to use the
+\fB\-\-setopt=module_platform_id=<module_platform_name:stream>\fP command\-line option when creating the installroot,
+otherwise the module_platform_id value will be taken from the
+\fB/etc/os\-release\fP file within the installroot (and thus it will be empty at the time of creation, the modular
+dependency could be unsatisfied and modules content could be excluded).
+.sp
+Installroot examples:
+.INDENT 0.0
+.TP
+.B \fBdnf \-\-installroot=<installroot> \-\-releasever=<release> install system\-release\fP
+Permanently sets the \fBreleasever\fP of the system in the
+\fB<installroot>\fP directory to \fB<release>\fP\&.
+.TP
+.B \fBdnf \-\-installroot=<installroot> \-\-setopt=reposdir=<path> \-\-config /path/dnf.conf upgrade\fP
+Upgrades packages inside the installroot from a repository described by
+\fB\-\-setopt\fP using configuration from \fB/path/dnf.conf\fP\&.
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-newpackage\fP
+Include newpackage relevant packages. Applicable for the install, repoquery, updateinfo and
+upgrade commands.
+.TP
+.B \fB\-\-noautoremove\fP
+Disable removal of dependencies that are no longer used. It sets
+clean_requirements_on_remove configuration option to \fBFalse\fP\&.
+.TP
+.B \fB\-\-nobest\fP
+Set best option to \fBFalse\fP, so that transactions are not limited to best candidates only.
+.TP
+.B \fB\-\-nodocs\fP
+Do not install documentation. Sets the rpm flag \(aqRPMTRANS_FLAG_NODOCS\(aq.
+.TP
+.B \fB\-\-nogpgcheck\fP
+Skip checking GPG signatures on packages (if RPM policy allows).
+.TP
+.B \fB\-\-noplugins\fP
+Disable all plugins.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-obsoletes\fP
+This option has an effect on an install/update, it enables
+dnf\(aqs obsoletes processing logic. For more information see the
+obsoletes option.
+.sp
+This option also displays capabilities that the package obsoletes when used together with the \fI\%repoquery\fP command.
+.sp
+Configuration Option: obsoletes
+.TP
+.B \fB\-q, \-\-quiet\fP
+In combination with a non\-interactive command, shows just the relevant content. Suppresses messages notifying about the current state or actions of DNF.
+.TP
+.B \fB\-R <minutes>, \-\-randomwait=<minutes>\fP
+Maximum command wait time.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-refresh\fP
+Set metadata as expired before running the command.
+.TP
+.B \fB\-\-releasever=<release>\fP
+Configure DNF as if the distribution release was \fB<release>\fP\&. This can
+affect cache paths, values in configuration files and mirrorlist URLs.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-repofrompath <repo>,<path/url>\fP
+Specify a repository to add to the repositories for this query.
+This option can be used multiple times.
+.UNINDENT
+.INDENT 0.0
+.IP \(bu 2
+The repository label is specified by \fB<repo>\fP\&.
+.IP \(bu 2
+The path or url to the repository is specified by \fB<path/url>\fP\&.
+It is the same path as a baseurl and can be also enriched by the
+repo variables\&.
+.IP \(bu 2
+The configuration for the repository can be adjusted using \-\fI\%\-setopt\fP=<repo>.<option>=<value>.
+.IP \(bu 2
+If you want to view only packages from this repository, combine this
+with the \fB\-\-repo=<repo>\fP or \fB\-\-disablerepo="*"\fP switches.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-repo=<repoid>, \-\-repoid=<repoid>\fP
+Enable just specific repositories by an id or a glob. Can be used multiple
+times with accumulative effect. It is basically a shortcut for
+\fB\-\-disablerepo="*" \-\-enablerepo=<repoid>\fP and is mutually exclusive with
+the \fB\-\-disablerepo\fP option.
+.TP
+.B \fB\-\-rpmverbosity=<name>\fP
+RPM debug scriptlet output level. Sets the debug level to \fB<name>\fP for RPM scriptlets.
+For available levels, see the \fBrpmverbosity\fP configuration option.
+.TP
+.B \fB\-\-sec\-severity=<severity>, \-\-secseverity=<severity>\fP
+Includes packages that provide a fix for an issue of the specified severity.
+Applicable for the install, repoquery, updateinfo and upgrade commands.
+.TP
+.B \fB\-\-security\fP
+Includes packages that provide a fix for a security issue. Applicable for the
+upgrade command.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-setopt=<option>=<value>\fP
+Override a configuration option from the configuration file. To override configuration options for repositories, use
+\fBrepoid.option\fP for the \fB<option>\fP\&. Values for configuration options like \fBexcludepkgs\fP, \fBincludepkgs\fP,
+\fBinstallonlypkgs\fP and \fBtsflags\fP are appended to the original value, they do not override it. However, specifying
+an empty value (e.g. \fB\-\-setopt=tsflags=\fP) will clear the option.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-skip\-broken\fP
+Resolve depsolve problems by removing packages that are causing problems from the transaction.
+It is an alias for the strict configuration option with value \fBFalse\fP\&.
+Additionally, with the \fI\%enable\fP and
+\fI\%disable\fP module subcommands it allows one to perform an action even in case of
+broken modular dependencies.
+.TP
+.B \fB\-\-showduplicates\fP
+Show duplicate packages in repositories. Applicable for the list and search commands.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-v, \-\-verbose\fP
+Verbose operation, show debug messages.
+.TP
+.B \fB\-\-version\fP
+Show DNF version and exit.
+.TP
+.B \fB\-y, \-\-assumeyes\fP
+Automatically answer yes for all questions.
+.UNINDENT
+.sp
+List options are comma\-separated. Command\-line options override respective settings from configuration files.
+.SH COMMANDS
+.sp
+For an explanation of \fB<package\-spec>\fP, \fB<package\-file\-spec>\fP and \fB<package\-name\-spec>\fP see
+\fI\%Specifying Packages\fP\&.
+.sp
+For an explanation of \fB<provide\-spec>\fP see \fI\%Specifying Provides\fP\&.
+.sp
+For an explanation of \fB<group\-spec>\fP see \fI\%Specifying Groups\fP\&.
+.sp
+For an explanation of \fB<module\-spec>\fP see \fI\%Specifying Modules\fP\&.
+.sp
+For an explanation of \fB<transaction\-spec>\fP see \fI\%Specifying Transactions\fP\&.
+.SS Alias Command
+.nf
+Command: \fBalias\fP
+.fi
+.sp
+.sp
+Allows the user to define and manage a list of aliases (in the form \fB<name=value>\fP),
+which can be then used as dnf commands to abbreviate longer command sequences. For examples on using
+the alias command, see \fI\%Alias Examples\fP\&. For examples on the alias
+processing, see \fI\%Alias Processing Examples\fP\&.
+.sp
+To use an alias (name=value), the name must be placed as the first "command" (e.g. the first argument
+that is not an option). It is then replaced by its value and the resulting sequence is again searched
+for aliases. The alias processing stops when the first found command is not a name of any alias.
+.sp
+In case the processing would result in an infinite recursion, the original arguments are used instead.
+.sp
+Also, like in shell aliases, if the result starts with a \fB\e\fP, the alias processing will stop.
+.sp
+All aliases are defined in configuration files in the \fB/etc/dnf/aliases.d/\fP directory in the [aliases] section,
+and aliases created by the alias command are written to the \fBUSER.conf\fP file. In case of conflicts,
+the \fBUSER.conf\fP has the highest priority, and alphabetical ordering is used for the rest of the
+configuration files.
+.sp
+Optionally, there is the \fBenabled\fP option in the \fB[main]\fP section defaulting to True. This can be set for each
+file separately in the respective file, or globally for all aliases in the \fBALIASES.conf\fP file.
+.sp
+\fBdnf alias [options] [list] [<name>...]\fP
+.INDENT 0.0
+.INDENT 3.5
+List aliases with their final result. The \fB[<alias>...]\fP parameter further limits the result to only those aliases matching it.
+.UNINDENT
+.UNINDENT
+.sp
+\fBdnf alias [options] add <name=value>...\fP
+.INDENT 0.0
+.INDENT 3.5
+Create new aliases.
+.UNINDENT
+.UNINDENT
+.sp
+\fBdnf alias [options] delete <name>...\fP
+.INDENT 0.0
+.INDENT 3.5
+Delete aliases.
+.UNINDENT
+.UNINDENT
+.SS Alias Examples
+.INDENT 0.0
+.TP
+.B \fBdnf alias list\fP
+Lists all defined aliases.
+.TP
+.B \fBdnf alias add rm=remove\fP
+Adds a new command alias called \fBrm\fP which works the same as the \fBremove\fP command.
+.TP
+.B \fBdnf alias add upgrade="\eupgrade \-\-skip\-broken \-\-disableexcludes=all \-\-obsoletes"\fP
+Adds a new command alias called \fBupgrade\fP which works the same as the \fBupgrade\fP command,
+with additional options. Note that the original \fBupgrade\fP command is prefixed with a \fB\e\fP
+to prevent an infinite loop in alias processing.
+.UNINDENT
+.SS Alias Processing Examples
+.sp
+If there are defined aliases \fBin=install\fP and \fBFORCE="\-\-skip\-broken \-\-disableexcludes=all"\fP:
+.INDENT 0.0
+.IP \(bu 2
+\fBdnf FORCE in\fP will be replaced with \fBdnf \-\-skip\-broken \-\-disableexcludes=all install\fP
+.IP \(bu 2
+\fBdnf in FORCE\fP will be replaced with \fBdnf install FORCE\fP (which will fail)
+.UNINDENT
+.sp
+If there is defined alias \fBin=install\fP:
+.INDENT 0.0
+.IP \(bu 2
+\fBdnf in\fP will be replaced with \fBdnf install\fP
+.IP \(bu 2
+\fBdnf \-\-repo updates in\fP will be replaced with \fBdnf \-\-repo updates in\fP (which will fail)
+.UNINDENT
+.SS Autoremove Command
+.nf
+Command: \fBautoremove\fP
+Aliases for \fI\%explicit NEVRA matching\fP: \fBautoremove\-n\fP, \fBautoremove\-na\fP, \fBautoremove\-nevra\fP
+.fi
+.sp
+.sp
+\fBdnf [options] autoremove\fP
+.INDENT 0.0
+.INDENT 3.5
+Removes all "leaf" packages from the system that were originally installed as dependencies of user\-installed packages, but which are no longer required by any such package.
+.UNINDENT
+.UNINDENT
+.sp
+Packages listed in installonlypkgs are never automatically removed by
+this command.
+.sp
+\fBdnf [options] autoremove <spec>...\fP
+.INDENT 0.0
+.INDENT 3.5
+This is an alias for the \fI\%Remove Command\fP command with clean_requirements_on_remove set to
+\fBTrue\fP\&. It removes the specified packages from the system along with any packages depending on the
+packages being removed. Each \fB<spec>\fP can be either a \fB<package\-spec>\fP, which specifies a
+package directly, or a \fB@<group\-spec>\fP, which specifies an (environment) group which contains
+it. It also removes any dependencies that are no longer needed.
+.sp
+There are also a few specific autoremove commands \fBautoremove\-n\fP, \fBautoremove\-na\fP and
+\fBautoremove\-nevra\fP that allow the specification of an exact argument in the NEVRA
+(name\-epoch:version\-release.architecture) format.
+.UNINDENT
+.UNINDENT
+.sp
+This command by default does not force a sync of expired metadata. See also \fI\%Metadata Synchronization\fP\&.
+.SS Check Command
+.nf
+Command: \fBcheck\fP
+.fi
+.sp
+.sp
+\fBdnf [options] check [\-\-dependencies] [\-\-duplicates] [\-\-obsoleted] [\-\-provides]\fP
+.INDENT 0.0
+.INDENT 3.5
+Checks the local packagedb and produces information on any problems it
+finds. You can limit the checks to be performed by using the \fB\-\-dependencies\fP,
+\fB\-\-duplicates\fP, \fB\-\-obsoleted\fP and \fB\-\-provides\fP options (the default is to
+check everything).
+.UNINDENT
+.UNINDENT
+.SS Check\-Update Command
+.nf
+Command: \fBcheck\-update\fP
+Aliases: \fBcheck\-upgrade\fP
+.fi
+.sp
+.sp
+\fBdnf [options] check\-update [\-\-changelogs] [<package\-file\-spec>...]\fP
+.INDENT 0.0
+.INDENT 3.5
+Non\-interactively checks if updates of the specified packages are available. If no \fB<package\-file\-spec>\fP is given, checks whether any updates at all are available for your system. DNF exit code will be 100 when there are updates available and a list of the updates will be printed, 0 if not and 1 if an error occurs. If \fB\-\-changelogs\fP option is specified, also changelog delta of packages about to be updated is printed.
+.sp
+Please note that having a specific newer version available for an installed package (and reported by \fBcheck\-update\fP) does not imply that subsequent \fBdnf upgrade\fP will install it. The difference is that \fBdnf upgrade\fP has restrictions (like package dependencies being satisfied) to take into account.
+.sp
+The output is affected by the autocheck_running_kernel configuration option.
+.UNINDENT
+.UNINDENT
+.SS Clean Command
+.nf
+Command: \fBclean\fP
+.fi
+.sp
+.sp
+Performs cleanup of temporary files kept for repositories. This includes any
+such data left behind from disabled or removed repositories as well as for
+different distribution release versions.
+.INDENT 0.0
+.TP
+.B \fBdnf clean dbcache\fP
+Removes cache files generated from the repository metadata. This forces DNF
+to regenerate the cache files the next time it is run.
+.TP
+.B \fBdnf clean expire\-cache\fP
+Marks the repository metadata expired. DNF will re\-validate the cache for
+each repository the next time it is used.
+.TP
+.B \fBdnf clean metadata\fP
+Removes repository metadata. Those are the files which DNF uses to determine
+the remote availability of packages. Using this option will make DNF
+download all the metadata the next time it is run.
+.TP
+.B \fBdnf clean packages\fP
+Removes any cached packages from the system.
+.TP
+.B \fBdnf clean all\fP
+Does all of the above.
+.UNINDENT
+.SS Deplist Command
+.INDENT 0.0
+.TP
+.B \fBdnf [options] deplist [<select\-options>] [<query\-options>] [<package\-spec>]\fP
+Deprecated alias for \fI\%dnf repoquery \-\-deplist\fP\&.
+.UNINDENT
+.SS Distro\-Sync Command
+.nf
+Command: \fBdistro\-sync\fP
+Aliases: \fBdsync\fP
+Deprecated aliases: \fBdistrosync\fP, \fBdistribution\-synchronization\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf distro\-sync [<package\-spec>...]\fP
+As necessary upgrades, downgrades or keeps selected installed packages to match
+the latest version available from any enabled repository. If no package is given, all installed packages are considered.
+.sp
+See also \fI\%Configuration Files Replacement Policy\fP\&.
+.UNINDENT
+.SS Downgrade Command
+.nf
+Command: \fBdowngrade\fP
+Aliases: \fBdg\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] downgrade <package\-spec>...\fP
+Downgrades the specified packages to the highest installable package of all known lower versions
+if possible. When version is given and is lower than version of installed package then it
+downgrades to target version.
+.UNINDENT
+.SS Group Command
+.nf
+Command: \fBgroup\fP
+Aliases: \fBgrp\fP
+Deprecated aliases: \fBgroups\fP, \fBgrouplist\fP, \fBgroupinstall\fP, \fBgroupupdate\fP, \fBgroupremove\fP, \fBgrouperase\fP, \fBgroupinfo\fP
+.fi
+.sp
+.sp
+Groups are virtual collections of packages. DNF keeps track of groups that the user selected ("marked") installed and can manipulate the comprising packages with simple commands.
+.INDENT 0.0
+.TP
+.B \fBdnf [options] group [summary] <group\-spec>\fP
+Display overview of how many groups are installed and available. With a
+spec, limit the output to the matching groups. \fBsummary\fP is the default
+groups subcommand.
+.TP
+.B \fBdnf [options] group info <group\-spec>\fP
+Display package lists of a group. Shows which packages are installed or
+available from a repository when \fB\-v\fP is used.
+.TP
+.B \fBdnf [options] group install [\-\-with\-optional] <group\-spec>...\fP
+Mark the specified group installed and install packages it contains. Also
+include \fIoptional\fP packages of the group if \fB\-\-with\-optional\fP is
+specified. All \fImandatory\fP and \fIDefault\fP packages will be installed whenever possible.
+Conditional packages are installed if they meet their requirement.
+If the group is already (partially) installed, the command installs the missing packages from the group.
+Depending on the value of obsoletes configuration option group installation takes obsoletes into account.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdnf [options] group list <group\-spec>...\fP
+List all matching groups, either among installed or available groups. If
+nothing is specified, list all known groups. \fB\-\-installed\fP and \fB\-\-available\fP options narrow down the requested list.
+Records are ordered by the \fIdisplay_order\fP tag defined in comps.xml file.
+Provides a list of all hidden groups by using option \fB\-\-hidden\fP\&.
+Provides group IDs when the \fB\-v\fP or \fB\-\-ids\fP options are used.
+.TP
+.B \fBdnf [options] group remove <group\-spec>...\fP
+Mark the group removed and remove those packages in the group from the system which do not belong to another installed group and were not installed explicitly by the user.
+.TP
+.B \fBdnf [options] group upgrade <group\-spec>...\fP
+Upgrades the packages from the group and upgrades the group itself. The latter comprises of installing packages that were added to the group by the distribution and removing packages that got removed from the group as far as they were not installed explicitly by the user.
+.UNINDENT
+.sp
+Groups can also be marked installed or removed without physically manipulating any packages:
+.INDENT 0.0
+.TP
+.B \fBdnf [options] group mark install <group\-spec>...\fP
+Mark the specified group installed. No packages will be installed by this command, but the group is then considered installed.
+.TP
+.B \fBdnf [options] group mark remove <group\-spec>...\fP
+Mark the specified group removed. No packages will be removed by this command.
+.UNINDENT
+.sp
+See also \fI\%Configuration Files Replacement Policy\fP\&.
+.SS Help Command
+.nf
+Command: \fBhelp\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf help [<command>]\fP
+Displays the help text for all commands. If given a command name then only
+displays help for that particular command.
+.UNINDENT
+.SS History Command
+.nf
+Command: \fBhistory\fP
+Aliases: \fBhist\fP
+.fi
+.sp
+.sp
+The history command allows the user to view what has happened in past
+transactions and act according to this information (assuming the
+\fBhistory_record\fP configuration option is set).
+.INDENT 0.0
+.TP
+.B \fBdnf history [list] [\-\-reverse] [<spec>...]\fP
+The default history action is listing information about given transactions
+in a table. Each \fB<spec>\fP can be either a \fB<transaction\-spec>\fP, which
+specifies a transaction directly, or a \fB<transaction\-spec>..<transaction\-spec>\fP,
+which specifies a range of transactions, or a \fB<package\-name\-spec>\fP,
+which specifies a transaction by a package which it manipulated. When no
+transaction is specified, list all known transactions.
+.INDENT 7.0
+.TP
+.B \fB\-\-reverse\fP
+The order of \fBhistory list\fP output is printed in reverse order.
+.UNINDENT
+.TP
+.B \fBdnf history info [<spec>...]\fP
+Describe the given transactions. The meaning of \fB<spec>\fP is the same as
+in the \fI\%History List Command\fP\&. When no
+transaction is specified, describe what happened during the latest
+transaction.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdnf history redo <transaction\-spec>|<package\-file\-spec>\fP
+Repeat the specified transaction. Uses the last transaction (with the highest ID)
+if more than one transaction for given <package\-file\-spec> is found. If it is not possible
+to redo some operations due to the current state of RPMDB, it will not redo the transaction.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdnf history replay [\-\-ignore\-installed] [\-\-ignore\-extras] [\-\-skip\-unavailable] <filename>\fP
+Replay a transaction stored in file \fB<filename>\fP by \fI\%History Store
+Command\fP\&. The replay will perform the exact
+same operations on the packages as in the original transaction and will
+return with an error if case of any differences in installed packages or
+their versions. See also the Transaction JSON Format specification of the
+file format.
+.INDENT 7.0
+.TP
+.B \fB\-\-ignore\-installed\fP
+Don\(aqt check for the installed packages being in the same state as those
+recorded in the transaction. E.g. in case there is an upgrade
+\fBfoo\-1.0\fP \-> \fBfoo\-2.0\fP stored in the transaction, but there is
+\fBfoo\-1.1\fP installed on the target system.
+.TP
+.B \fB\-\-ignore\-extras\fP
+Don\(aqt check for extra packages pulled into the transaction on the
+target system. E.g. the target system may not have some dependency,
+which was installed on the source system. The replay errors out on this
+by default, as the transaction would not be the same.
+.TP
+.B \fB\-\-skip\-unavailable\fP
+In case some packages stored in the transaction are not available on
+the target system, skip them instead of erroring out.
+.UNINDENT
+.TP
+.B \fBdnf history rollback <transaction\-spec>|<package\-file\-spec>\fP
+Undo all transactions performed after the specified transaction. Uses the last transaction
+(with the highest ID) if more than one transaction for given <package\-file\-spec> is found.
+If it is not possible to undo some transactions due to the current state of RPMDB, it will not undo
+any transaction.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdnf history store [\-\-output <output\-file>] <transaction\-spec>\fP
+Store a transaction specified by \fB<transaction\-spec>\fP\&. The transaction
+can later be replayed by the \fI\%History Replay Command\fP\&.
+.sp
+Warning: The stored transaction format is considered unstable and may
+change at any time. It will work if the same version of dnf is used to
+store and replay (or between versions as long as it stays the same).
+.sp
+\fB\-o <output\-file>, \-\-output=<output\-file>\fP
+Store the serialized transaction into \fB<output\-file\fP\&. Default is \fBtransaction.json\fP\&.
+.TP
+.B \fBdnf history undo <transaction\-spec>|<package\-file\-spec>\fP
+Perform the opposite operation to all operations performed in the specified transaction.
+Uses the last transaction (with the highest ID) if more than one transaction for given
+<package\-file\-spec> is found. If it is not possible to undo some operations due to
+the current state of RPMDB, it will not undo the transaction.
+.TP
+.B \fBdnf history userinstalled\fP
+Show all installonly packages, packages installed outside of DNF and packages not
+installed as dependency. I.e. it lists packages that will stay on the system when
+\fI\%Autoremove Command\fP or \fI\%Remove Command\fP along with
+\fIclean_requirements_on_remove\fP configuration option set to True is executed. Note the same
+results can be accomplished with \fBdnf repoquery \-\-userinstalled\fP, and the repoquery
+command is more powerful in formatting of the output.
+.UNINDENT
+.sp
+This command by default does not force a sync of expired metadata, except for
+the redo, rollback, and undo subcommands.
+See also \fI\%Metadata Synchronization\fP
+and \fI\%Configuration Files Replacement Policy\fP\&.
+.SS Info Command
+.nf
+Command: \fBinfo\fP
+Aliases: \fBif\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] info [<package\-file\-spec>...]\fP
+Lists description and summary information about installed and available packages.
+.UNINDENT
+.sp
+The info command limits the displayed packages the same way as the \fI\%list command\fP\&.
+.sp
+This command by default does not force a sync of expired metadata. See also \fI\%Metadata Synchronization\fP\&.
+.SS Install Command
+.nf
+Command: \fBinstall\fP
+Aliases: \fBin\fP
+Aliases for \fI\%explicit NEVRA matching\fP: \fBinstall\-n\fP, \fBinstall\-na\fP, \fBinstall\-nevra\fP
+Deprecated aliases: \fBlocalinstall\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] install <spec>...\fP
+Makes sure that the given packages and their dependencies are installed
+on the system. Each \fB<spec>\fP can be either a \fI\%<package\-spec>\fP,
+or a @\fI\%<module\-spec>\fP, or a @\fI\%<group\-spec>\fP\&.
+See \fI\%Install Examples\fP\&.
+If a given package or provide cannot be (and is not already) installed,
+the exit code will be non\-zero.
+If the \fB<spec>\fP matches both a @\fI\%<module\-spec>\fP and
+a @\fI\%<group\-spec>\fP, only the module is installed.
+.sp
+When \fI\%<package\-spec>\fP to specify the exact version
+of the package is given, DNF will install the desired version, no matter which
+version of the package is already installed. The former version of the package
+will be removed in the case of non\-installonly package.
+.sp
+On the other hand if \fI\%<package\-spec>\fP specifies only a name,
+DNF also takes into account packages obsoleting it when picking which package to install.
+This behaviour is specific to the install command.
+Note that this can lead to seemingly unexpected results if a package has multiple versions and
+some older version is being obsoleted. It creates a split in the upgrade\-path and both ways
+are considered correct, the resulting package is picked simply by lexicographical order.
+.sp
+There are also a few specific install commands \fBinstall\-n\fP, \fBinstall\-na\fP and
+\fBinstall\-nevra\fP that allow the specification of an exact argument in the NEVRA format.
+.sp
+See also \fI\%Configuration Files Replacement Policy\fP\&.
+.UNINDENT
+.SS Install Examples
+.INDENT 0.0
+.TP
+.B \fBdnf install tito\fP
+Install the \fBtito\fP package (tito is the package name).
+.TP
+.B \fBdnf install ~/Downloads/tito\-0.6.2\-1.fc22.noarch.rpm\fP
+Install a local rpm file tito\-0.6.2\-1.fc22.noarch.rpm from the ~/Downloads/
+directory.
+.TP
+.B \fBdnf install tito\-0.5.6\-1.fc22\fP
+Install the package with a specific version. If the package is already installed it
+will automatically try to downgrade or upgrade to the specific version.
+.TP
+.B \fBdnf \-\-best install tito\fP
+Install the latest available version of the package. If the package is already installed it
+will try to automatically upgrade to the latest version. If the latest version
+of the package cannot be installed, the installation will fail.
+.TP
+.B \fBdnf install vim\fP
+DNF will automatically recognize that vim is not a package name, but
+will look up and install a package that provides vim with all the required
+dependencies. Note: Package name match has precedence over package provides
+match.
+.TP
+.B \fBdnf install https://kojipkgs.fedoraproject.org//packages/tito/0.6.0/1.fc22/noarch/tito\-0.6.0\-1.fc22.noarch.rpm\fP
+Install a package directly from a URL.
+.TP
+.B \fBdnf install \(aq@docker\(aq\fP
+Install all default profiles of module \(aqdocker\(aq and their RPMs. Module streams get enabled accordingly.
+.TP
+.B \fBdnf install \(aq@Web Server\(aq\fP
+Install the \(aqWeb Server\(aq environmental group.
+.TP
+.B \fBdnf install /usr/bin/rpmsign\fP
+Install a package that provides the /usr/bin/rpmsign file.
+.TP
+.B \fBdnf \-y install tito \-\-setopt=install_weak_deps=False\fP
+Install the \fBtito\fP package (tito is the package name) without weak deps. Weak deps are not required for
+core functionality of the package, but they enhance the original package (like extended
+documentation, plugins, additional functions, etc.).
+.TP
+.B \fBdnf install \-\-advisory=FEDORA\-2018\-b7b99fe852 \e*\fP
+Install all packages that belong to the "FEDORA\-2018\-b7b99fe852" advisory.
+.UNINDENT
+.SS List Command
+.nf
+Command: \fBlist\fP
+Aliases: \fBls\fP
+.fi
+.sp
+.sp
+Prints lists of packages depending on the packages\(aq relation to the
+system. A package is \fBinstalled\fP if it is present in the RPMDB, and it is \fBavailable\fP
+if it is not installed but is present in a repository that DNF knows about.
+.sp
+The list command also limits the displayed packages according to specific criteria,
+e.g. to only those that update an installed package (respecting the repository
+priority). The exclude option in the configuration file can influence the
+result, but if the \-\fI\%\-disableexcludes\fP command line
+option is used, it ensures that all installed packages will be listed.
+.INDENT 0.0
+.TP
+.B \fBdnf [options] list [\-\-all] [<package\-file\-spec>...]\fP
+Lists all packages, present in the RPMDB, in a repository or both.
+.TP
+.B \fBdnf [options] list \-\-installed [<package\-file\-spec>...]\fP
+Lists installed packages.
+.TP
+.B \fBdnf [options] list \-\-available [<package\-file\-spec>...]\fP
+Lists available packages.
+.TP
+.B \fBdnf [options] list \-\-extras [<package\-file\-spec>...]\fP
+Lists extras, that is packages installed on the system that are not
+available in any known repository.
+.TP
+.B \fBdnf [options] list \-\-obsoletes [<package\-file\-spec>...]\fP
+List packages installed on the system that are obsoleted by packages in
+any known repository.
+.TP
+.B \fBdnf [options] list \-\-recent [<package\-file\-spec>...]\fP
+List packages recently added into the repositories.
+.TP
+.B \fBdnf [options] list \-\-upgrades [<package\-file\-spec>...]\fP
+List upgrades available for the installed packages.
+.TP
+.B \fBdnf [options] list \-\-autoremove\fP
+List packages which will be removed by the \fBdnf autoremove\fP command.
+.UNINDENT
+.sp
+This command by default does not force a sync of expired metadata. See also \fI\%Metadata Synchronization\fP\&.
+.SS Makecache Command
+.nf
+Command: \fBmakecache\fP
+Aliases: \fBmc\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] makecache\fP
+Downloads and caches metadata for enabled repositories. Tries to
+avoid downloading whenever possible (e.g. when the local metadata hasn\(aqt
+expired yet or when the metadata timestamp hasn\(aqt changed).
+.TP
+.B \fBdnf [options] makecache \-\-timer\fP
+Like plain \fBmakecache\fP, but instructs DNF to be more resource\-aware,
+meaning it will not do anything if running on battery power and will terminate
+immediately if it\(aqs too soon after the last successful \fBmakecache\fP run
+(see \fBdnf.conf(5)\fP, metadata_timer_sync).
+.UNINDENT
+.SS Mark Command
+.nf
+Command: \fBmark\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf mark install <package\-spec>...\fP
+Marks the specified packages as installed by user. This can be useful if any package was installed as a dependency and is desired to stay on the system when \fI\%Autoremove Command\fP or \fI\%Remove Command\fP along with \fIclean_requirements_on_remove\fP configuration option set to \fBTrue\fP is executed.
+.TP
+.B \fBdnf mark remove <package\-spec>...\fP
+Unmarks the specified packages as installed by user. Whenever you as a user don\(aqt need a specific package you can mark it for removal. The package stays installed on the system but will be removed when \fI\%Autoremove Command\fP or \fI\%Remove Command\fP along with \fIclean_requirements_on_remove\fP configuration option set to \fBTrue\fP is executed. You should use this operation instead of \fI\%Remove Command\fP if you\(aqre not sure whether the package is a requirement of other user installed packages on the system.
+.TP
+.B \fBdnf mark group <package\-spec>...\fP
+Marks the specified packages as installed by group. This can be useful if any package was
+installed as a dependency or a user and is desired to be protected and handled as a group
+member like during group remove.
+.UNINDENT
+.SS Module Command
+.nf
+Command: \fBmodule\fP
+.fi
+.sp
+.sp
+Modularity overview is available at man page dnf.modularity(7)\&.
+Module subcommands take \fI\%<module\-spec>\fP\&... arguments that specify modules or profiles.
+.INDENT 0.0
+.TP
+.B \fBdnf [options] module install <module\-spec>...\fP
+Install module profiles, including their packages.
+In case no profile was provided, all default profiles get installed.
+Module streams get enabled accordingly.
+.sp
+This command cannot be used for switching module streams. Use the
+\fI\%dnf module switch\-to\fP command for that.
+.TP
+.B \fBdnf [options] module update <module\-spec>...\fP
+Update packages associated with an active module stream, optionally restricted to a profile.
+If the \fIprofile_name\fP is provided, only the packages referenced by that profile will be updated.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdnf [options] module switch\-to <module\-spec>...\fP
+Switch to or enable a module stream, change versions of installed packages to versions provided
+by the new stream, and remove packages from the old stream that are no longer available. It also
+updates installed profiles if they are available for the new stream. When a profile was
+provided, it installs that profile and does not update any already installed profiles.
+.sp
+This command can be used as a stronger version of the
+\fI\%dnf module enable\fP command, which not only enables modules,
+but also does a \fIdistrosync\fP to all modular packages in the enabled modules.
+.sp
+It can also be used as a stronger version of the
+\fI\%dnf module install\fP command, but it requires to specify
+profiles that are supposed to be installed, because \fIswitch\-to\fP command does not use \fIdefault
+profiles\fP\&. The \fIswitch\-to\fP command doesn\(aqt only install profiles, it also makes a \fIdistrosync\fP
+to all modular packages in the installed module.
+.TP
+.B \fBdnf [options] module remove <module\-spec>...\fP
+Remove installed module profiles, including packages that were installed with the
+\fI\%dnf module install\fP command. Will not remove packages
+required by other installed module profiles or by other user\-installed packages.
+In case no profile was provided, all installed profiles get removed.
+.TP
+.B \fBdnf [options] module remove \-\-all <module\-spec>...\fP
+Remove installed module profiles, including packages that were installed with the
+\fI\%dnf module install\fP command.
+With \-\-all option it additionally removes all packages whose names are provided by specified
+modules. Packages required by other installed module profiles and packages whose names are also
+provided by any other module are not removed.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdnf [options] module enable <module\-spec>...\fP
+Enable a module stream and make the stream RPMs available in the package set.
+.sp
+Modular dependencies are resolved, dependencies checked and also recursively enabled. In case
+of modular dependency issue the operation will be rejected. To perform the action anyway please use
+\-\fI\%\-skip\-broken\fP option.
+.sp
+This command cannot be used for switching module streams. Use the
+\fI\%dnf module switch\-to\fP command for that.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdnf [options] module disable <module\-name>...\fP
+Disable a module. All related module streams will become unavailable.
+Consequently, all installed profiles will be removed and the module RPMs
+will become unavailable in the package set. In case of modular
+dependency issue the operation will be rejected. To perform the action anyway please use \-\fI\%\-skip\-broken\fP option.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdnf [options] module reset <module\-name>...\fP
+Reset module state so it\(aqs no longer enabled or disabled.
+Consequently, all installed profiles will be removed and
+only RPMs from the default stream will be available in the package set.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdnf [options] module provides <package\-name\-spec>...\fP
+Lists all modular packages matching \fB<package\-name\-spec>\fP from all modules (including disabled), along with the modules and streams they belong to.
+.TP
+.B \fBdnf [options] module list [\-\-all] [module_name...]\fP
+Lists all module streams, their profiles and states (enabled, disabled, default).
+.TP
+.B \fBdnf [options] module list \-\-enabled [module_name...]\fP
+Lists module streams that are enabled.
+.TP
+.B \fBdnf [options] module list \-\-disabled [module_name...]\fP
+Lists module streams that are disabled.
+.TP
+.B \fBdnf [options] module list \-\-installed [module_name...]\fP
+List module streams with installed profiles.
+.TP
+.B \fBdnf [options] module info <module\-spec>...\fP
+Print detailed information about given module stream.
+.TP
+.B \fBdnf [options] module info \-\-profile <module\-spec>...\fP
+Print detailed information about given module profiles.
+.TP
+.B \fBdnf [options] module repoquery <module\-spec>...\fP
+List all available packages belonging to selected modules.
+.TP
+.B \fBdnf [options] module repoquery \-\-available <module\-spec>...\fP
+List all available packages belonging to selected modules.
+.TP
+.B \fBdnf [options] module repoquery \-\-installed <module\-spec>...\fP
+List all installed packages with same name like packages belonging to selected modules.
+.UNINDENT
+.SS Provides Command
+.nf
+Command: \fBprovides\fP
+Aliases: \fBprov\fP, \fBwhatprovides\fP, \fBwp\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] provides <provide\-spec>\fP
+Finds the packages providing the given \fB<provide\-spec>\fP\&. This is useful
+when one knows a filename and wants to find what package (installed or not)
+provides this file.
+The \fB<provide\-spec>\fP is gradually looked for at following locations:
+.INDENT 7.0
+.IP 1. 3
+The \fB<provide\-spec>\fP is matched with all file provides of any available package:
+.INDENT 3.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+$ dnf provides /usr/bin/gzip
+gzip\-1.9\-9.fc29.x86_64 : The GNU data compression program
+Matched from:
+Filename    : /usr/bin/gzip
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.IP 2. 3
+Then all provides of all available packages are searched:
+.INDENT 3.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+$ dnf provides "gzip(x86\-64)"
+gzip\-1.9\-9.fc29.x86_64 : The GNU data compression program
+Matched from:
+Provide     : gzip(x86\-64) = 1.9\-9.fc29
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.IP 3. 3
+DNF assumes that the \fB<provide\-spec>\fP is a system command, prepends it with \fB/usr/bin/\fP, \fB/usr/sbin/\fP prefixes (one at a time) and does the file provides search again. For legacy reasons (packages that didn\(aqt do UsrMove) also \fB/bin\fP and \fB/sbin\fP prefixes are being searched:
+.INDENT 3.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+$ dnf provides zless
+gzip\-1.9\-9.fc29.x86_64 : The GNU data compression program
+Matched from:
+Filename    : /usr/bin/zless
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.IP 4. 3
+If this last step also fails, DNF returns "Error: No Matches found".
+.UNINDENT
+.sp
+This command by default does not force a sync of expired metadata. See also \fI\%Metadata Synchronization\fP\&.
+.UNINDENT
+.SS Reinstall Command
+.nf
+Command: \fBreinstall\fP
+Aliases: \fBrei\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] reinstall <package\-spec>...\fP
+Installs the specified packages, fails if some of the packages are either
+not installed or not available (i.e. there is no repository where to
+download the same RPM).
+.UNINDENT
+.SS Remove Command
+.nf
+Command: \fBremove\fP
+Aliases: \fBrm\fP
+Aliases for \fI\%explicit NEVRA matching\fP: \fBremove\-n\fP, \fBremove\-na\fP, \fBremove\-nevra\fP
+Deprecated aliases: \fBerase\fP, \fBerase\-n\fP, \fBerase\-na\fP, \fBerase\-nevra\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] remove <package\-spec>...\fP
+Removes the specified packages from the system along with any packages depending on the packages being removed. Each \fB<spec>\fP can be either a \fB<package\-spec>\fP, which specifies a package directly, or a \fB@<group\-spec>\fP, which specifies an (environment) group which contains it. If \fBclean_requirements_on_remove\fP is enabled (the default), also removes any dependencies that are no longer needed.
+.TP
+.B \fBdnf [options] remove \-\-duplicates\fP
+Removes older versions of duplicate packages. To ensure the integrity of the system it
+reinstalls the newest package. In some cases the command cannot resolve conflicts. In such cases
+the \fI\%dnf shell\fP command with \fBremove \-\-duplicates\fP and \fBupgrade\fP
+dnf\-shell sub\-commands could help.
+.TP
+.B \fBdnf [options] remove \-\-oldinstallonly\fP
+Removes old installonly packages, keeping only latest versions and version of running kernel.
+.sp
+There are also a few specific remove commands \fBremove\-n\fP, \fBremove\-na\fP and \fBremove\-nevra\fP
+that allow the specification of an exact argument in the NEVRA format.
+.UNINDENT
+.SS Remove Examples
+.INDENT 0.0
+.TP
+.B \fBdnf remove acpi tito\fP
+Remove the \fBacpi\fP and \fBtito\fP packages.
+.TP
+.B \fBdnf remove $(dnf repoquery \-\-extras \-\-exclude=tito,acpi)\fP
+Remove packages not present in any repository, but don\(aqt remove the \fBtito\fP
+and \fBacpi\fP packages (they still might be removed if they depend on some of the removed packages).
+.UNINDENT
+.sp
+Remove older versions of duplicated packages (an equivalent of yum\(aqs \fIpackage\-cleanup \-\-cleandups\fP):
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf remove \-\-duplicates
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS Repoinfo Command
+.nf
+Command: \fBrepoinfo\fP
+.fi
+.sp
+.INDENT 0.0
+.INDENT 3.5
+An alias for the \fI\%repolist\fP command
+that provides more detailed information like \fBdnf repolist \-v\fP\&.
+.UNINDENT
+.UNINDENT
+.SS Repolist Command
+.nf
+Command: \fBrepolist\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] repolist [\-\-enabled|\-\-disabled|\-\-all]\fP
+Depending on the exact command lists enabled, disabled or all known
+repositories. Lists all enabled repositories by default. Provides more
+detailed information when \fB\-v\fP option is used.
+.UNINDENT
+.sp
+This command by default does not force a sync of expired metadata. See also \fI\%Metadata Synchronization\fP\&.
+.SS Repoquery Command
+.nf
+Command: \fBrepoquery\fP
+Aliases: \fBrq\fP
+Aliases for \fI\%explicit NEVRA matching\fP: \fBrepoquery\-n\fP, \fBrepoquery\-na\fP, \fBrepoquery\-nevra\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] repoquery [<select\-options>] [<query\-options>] [<package\-file\-spec>]\fP
+Searches available DNF repositories for selected packages and displays the requested information about them. It
+is an equivalent of \fBrpm \-q\fP for remote repositories.
+.TP
+.B \fBdnf [options] repoquery \-\-groupmember <package\-spec>...\fP
+List groups that contain <package\-spec>.
+.TP
+.B \fBdnf [options] repoquery \-\-querytags\fP
+Provides the list of tags recognized by the \-\fI\%\-queryformat\fP repoquery option.
+.sp
+There are also a few specific repoquery commands \fBrepoquery\-n\fP, \fBrepoquery\-na\fP and \fBrepoquery\-nevra\fP
+that allow the specification of an exact argument in the NEVRA format (does not affect arguments of options like \-\-whatprovides <arg>, ...).
+.UNINDENT
+.SS Select Options
+.sp
+Together with \fB<package\-file\-spec>\fP, control what packages are displayed in the output. If \fB<package\-file\-spec>\fP is given, limits the resulting set of
+packages to those matching the specification. All packages are considered if no \fB<package\-file\-spec>\fP is specified.
+.INDENT 0.0
+.TP
+.B \fB<package\-file\-spec>\fP
+Package specification in the NEVRA format (name[\-[epoch:]version[\-release]][.arch]), a package provide or a file provide. See \fI\%Specifying Packages\fP\&.
+.TP
+.B \fB\-a\fP, \fB\-\-all\fP
+Query all packages (for rpmquery compatibility, also a shorthand for repoquery \(aq*\(aq or repoquery
+without arguments).
+.TP
+.B \fB\-\-arch <arch>[,<arch>...], \-\-archlist <arch>[,<arch>...]\fP
+Limit the resulting set only to packages of selected architectures (default is all
+architectures). In some cases the result is affected by the basearch of the running system, therefore
+to run repoquery for an arch incompatible with your system use the \fB\-\-forcearch=<arch>\fP
+option to change the basearch.
+.TP
+.B \fB\-\-duplicates\fP
+Limit the resulting set to installed duplicate packages (i.e. more package versions
+for the same name and architecture). Installonly packages are excluded from this set.
+.TP
+.B \fB\-\-unneeded\fP
+Limit the resulting set to leaves packages that were installed as dependencies so they are no longer needed. This
+switch lists packages that are going to be removed after executing the \fBdnf autoremove\fP command.
+.TP
+.B \fB\-\-available\fP
+Limit the resulting set to available packages only (set by default).
+.TP
+.B \fB\-\-disable\-modular\-filtering\fP
+Disables filtering of modular packages, so that packages of inactive module streams are included in the result.
+.TP
+.B \fB\-\-extras\fP
+Limit the resulting set to packages that are not present in any of the available repositories.
+.TP
+.B \fB\-f <file>\fP, \fB\-\-file <file>\fP
+Limit the resulting set only to the package that owns \fB<file>\fP\&.
+.TP
+.B \fB\-\-installed\fP
+Limit the resulting set to installed packages only. The exclude option in the configuration file
+might influence the result, but if the command line option  \-\fI\%\-disableexcludes\fP is used, it ensures that all installed packages will be listed.
+.TP
+.B \fB\-\-installonly\fP
+Limit the resulting set to installed installonly packages.
+.TP
+.B \fB\-\-latest\-limit <number>\fP
+Limit the resulting set to <number> of latest packages for every package name and architecture.
+If <number> is negative, skip <number> of latest packages. For a negative <number> use the
+\fB\-\-latest\-limit=<number>\fP syntax.
+.TP
+.B \fB\-\-recent\fP
+Limit the resulting set to packages that were recently edited.
+.TP
+.B \fB\-\-repo <repoid>\fP
+Limit the resulting set only to packages from a repository identified by \fB<repoid>\fP\&.
+Can be used multiple times with accumulative effect.
+.TP
+.B \fB\-\-unsatisfied\fP
+Report unsatisfied dependencies among installed packages (i.e. missing requires and
+existing conflicts).
+.TP
+.B \fB\-\-upgrades\fP
+Limit the resulting set to packages that provide an upgrade for some already installed package.
+.TP
+.B \fB\-\-userinstalled\fP
+Limit the resulting set to packages installed by the user. The exclude option
+in the configuration file might influence the result, but if the command line option  \-\fI\%\-disableexcludes\fP is used, it ensures that all installed packages will be listed.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-whatdepends <capability>[,<capability>...]\fP
+Limit the resulting set only to packages that require, enhance, recommend, suggest or
+supplement any of \fB<capabilities>\fP\&.
+.TP
+.B \fB\-\-whatconflicts <capability>[,<capability>...]\fP
+Limit the resulting set only to packages that conflict with any of \fB<capabilities>\fP\&.
+.TP
+.B \fB\-\-whatenhances <capability>[,<capability>...]\fP
+Limit the resulting set only to packages that enhance any of \fB<capabilities>\fP\&. Use \-\fI\%\-whatdepends\fP if you want to list all depending packages.
+.TP
+.B \fB\-\-whatobsoletes <capability>[,<capability>...]\fP
+Limit the resulting set only to packages that obsolete any of \fB<capabilities>\fP\&.
+.TP
+.B \fB\-\-whatprovides <capability>[,<capability>...]\fP
+Limit the resulting set only to packages that provide any of \fB<capabilities>\fP\&.
+.TP
+.B \fB\-\-whatrecommends <capability>[,<capability>...]\fP
+Limit the resulting set only to packages that recommend any of \fB<capabilities>\fP\&. Use \-\fI\%\-whatdepends\fP if you want to list all depending packages.
+.TP
+.B \fB\-\-whatrequires <capability>[,<capability>...]\fP
+Limit the resulting set only to packages that require any of \fB<capabilities>\fP\&. Use \-\fI\%\-whatdepends\fP if you want to list all depending packages.
+.TP
+.B \fB\-\-whatsuggests <capability>[,<capability>...]\fP
+Limit the resulting set only to packages that suggest any of \fB<capabilities>\fP\&. Use \-\fI\%\-whatdepends\fP if you want to list all depending packages.
+.TP
+.B \fB\-\-whatsupplements <capability>[,<capability>...]\fP
+Limit the resulting set only to packages that supplement any of \fB<capabilities>\fP\&. Use \-\fI\%\-whatdepends\fP if you want to list all depending packages.
+.TP
+.B \fB\-\-alldeps\fP
+This option is stackable with \fB\-\-whatrequires\fP or \-\fI\%\-whatdepends\fP only. Additionally it adds all packages requiring
+the package features to the result set (used as default).
+.TP
+.B \fB\-\-exactdeps\fP
+This option is stackable with \fB\-\-whatrequires\fP or \-\fI\%\-whatdepends\fP only. Limit the resulting set only to packages
+that require \fB<capability>\fP specified by \-\-whatrequires.
+.TP
+.B \fB\-\-srpm\fP
+Operate on the corresponding source RPM.
+.UNINDENT
+.SS Query Options
+.sp
+Set what information is displayed about each package.
+.sp
+The following are mutually exclusive, i.e. at most one can be specified. If no query option is given, matching packages
+are displayed in the standard NEVRA notation.
+.INDENT 0.0
+.TP
+.B \fB\-i, \-\-info\fP
+Show detailed information about the package.
+.TP
+.B \fB\-l, \-\-list\fP
+Show the list of files in the package.
+.TP
+.B \fB\-s, \-\-source\fP
+Show the package source RPM name.
+.TP
+.B \fB\-\-changelogs\fP
+Print the package changelogs.
+.TP
+.B \fB\-\-conflicts\fP
+Display capabilities that the package conflicts with. Same as \fB\-\-qf "%{conflicts}\fP\&.
+.TP
+.B \fB\-\-depends\fP
+Display capabilities that the package depends on, enhances, recommends, suggests or
+supplements.
+.TP
+.B \fB\-\-enhances\fP
+Display capabilities enhanced by the package. Same as \fB\-\-qf "%{enhances}""\fP\&.
+.TP
+.B \fB\-\-location\fP
+Show a location where the package could be downloaded from.
+.TP
+.B \fB\-\-obsoletes\fP
+Display capabilities that the package obsoletes. Same as \fB\-\-qf "%{obsoletes}"\fP\&.
+.TP
+.B \fB\-\-provides\fP
+Display capabilities provided by the package. Same as \fB\-\-qf "%{provides}"\fP\&.
+.TP
+.B \fB\-\-recommends\fP
+Display capabilities recommended by the package. Same as \fB\-\-qf "%{recommends}"\fP\&.
+.TP
+.B \fB\-\-requires\fP
+Display capabilities that the package depends on. Same as \fB\-\-qf "%{requires}"\fP\&.
+.TP
+.B \fB\-\-requires\-pre\fP
+Display capabilities that the package depends on for running a \fB%pre\fP script.
+Same as \fB\-\-qf "%{requires\-pre}"\fP\&.
+.TP
+.B \fB\-\-suggests\fP
+Display capabilities suggested by the package. Same as \fB\-\-qf "%{suggests}"\fP\&.
+.TP
+.B \fB\-\-supplements\fP
+Display capabilities supplemented by the package. Same as \fB\-\-qf "%{supplements}"\fP\&.
+.TP
+.B \fB\-\-tree\fP
+Display a recursive tree of packages with capabilities specified by one of the following supplementary options:
+\fB\-\-whatrequires\fP, \fB\-\-requires\fP, \fB\-\-conflicts\fP, \fB\-\-enhances\fP, \fB\-\-suggests\fP, \fB\-\-provides\fP,
+\fB\-\-supplements\fP, \fB\-\-recommends\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-deplist\fP
+Produce a list of all direct dependencies and what packages provide those
+dependencies for the given packages. The result only shows the newest
+providers (which can be changed by using \-\-verbose).
+.TP
+.B \fB\-\-nvr\fP
+Show found packages in the name\-version\-release format. Same as
+\fB\-\-qf "%{name}\-%{version}\-%{release}"\fP\&.
+.TP
+.B \fB\-\-nevra\fP
+Show found packages in the name\-epoch:version\-release.architecture format. Same as
+\fB\-\-qf "%{name}\-%{epoch}:%{version}\-%{release}.%{arch}"\fP (default).
+.TP
+.B \fB\-\-envra\fP
+Show found packages in the epoch:name\-version\-release.architecture format. Same as
+\fB\-\-qf "%{epoch}:%{name}\-%{version}\-%{release}.%{arch}"\fP
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-qf <format>\fP, \fB\-\-queryformat <format>\fP
+Custom display format. \fB<format>\fP is the string to output for each matched package. Every occurrence of
+\fB%{<tag>}\fP within is replaced by the corresponding attribute of the package. The list of recognized tags can be displayed
+by running \fBdnf repoquery \-\-querytags\fP\&.
+.TP
+.B \fB\-\-recursive\fP
+Query packages recursively. Has to be used with \fB\-\-whatrequires <REQ>\fP
+(optionally with \fB\-\-alldeps\fP, but not with \fB\-\-exactdeps\fP) or with
+\fB\-\-requires <REQ> \-\-resolve\fP\&.
+.TP
+.B \fB\-\-resolve\fP
+resolve capabilities to originating package(s).
+.UNINDENT
+.SS Examples
+.sp
+Display NEVRAs of all available packages matching \fBlight*\fP:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery \(aqlight*\(aq
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Display NEVRAs of all available packages matching name \fBlight*\fP and architecture \fBnoarch\fP (accepts only arguments in the "<name>.<arch>" format):
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery\-na \(aqlight*.noarch\(aq
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Display requires of all lighttpd packages:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery \-\-requires lighttpd
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Display packages providing the requires of python packages:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery \-\-requires python \-\-resolve
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Display source rpm of ligttpd package:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery \-\-source lighttpd
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Display package name that owns the given file:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery \-\-file /etc/lighttpd/lighttpd.conf
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Display name, architecture and the containing repository of all lighttpd packages:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery \-\-queryformat \(aq%{name}.%{arch} : %{reponame}\(aq lighttpd
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Display all available packages providing "webserver":
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery \-\-whatprovides webserver
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Display all available packages providing "webserver" but only for "i686" architecture:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery \-\-whatprovides webserver \-\-arch i686
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Display duplicate packages:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery \-\-duplicates
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Display source packages that require a <provide> for a build:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery \-\-disablerepo="*" \-\-enablerepo="*\-source" \-\-arch=src \-\-whatrequires <provide>
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS Repository\-Packages Command
+.nf
+Command: \fBrepository\-packages\fP
+Deprecated aliases: \fBrepo\-pkgs\fP, \fBrepo\-packages\fP, \fBrepository\-pkgs\fP
+.fi
+.sp
+.sp
+The repository\-packages command allows the user to run commands on top of all packages in the repository named \fB<repoid>\fP\&. However, any dependency resolution takes into account packages from all enabled repositories. The \fB<package\-file\-spec>\fP and \fB<package\-spec>\fP specifications further limit the candidates to only those packages matching at least one of them.
+.sp
+The \fBinfo\fP subcommand lists description and summary information about packages depending on the packages\(aq relation to the repository. The \fBlist\fP subcommand just prints lists of those packages.
+.INDENT 0.0
+.TP
+.B \fBdnf [options] repository\-packages <repoid> check\-update [<package\-file\-spec>...]\fP
+Non\-interactively checks if updates of the specified packages in the repository are available. DNF exit code will be 100 when there are updates available and a list of the updates will be printed.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> info [\-\-all] [<package\-file\-spec>...]\fP
+List all related packages.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> info \-\-installed [<package\-file\-spec>...]\fP
+List packages installed from the repository.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> info \-\-available [<package\-file\-spec>...]\fP
+List packages available in the repository but not currently installed on the system.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> info \-\-extras [<package\-file\-specs>...]\fP
+List packages installed from the repository that are not available in any repository.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> info \-\-obsoletes [<package\-file\-spec>...]\fP
+List packages in the repository that obsolete packages installed on the system.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> info \-\-recent [<package\-file\-spec>...]\fP
+List packages recently added into the repository.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> info \-\-upgrades [<package\-file\-spec>...]\fP
+List packages in the repository that upgrade packages installed on the system.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> install [<package\-spec>...]\fP
+Install packages matching \fB<package\-spec>\fP from the repository. If \fB<package\-spec>\fP isn\(aqt specified at all, install all packages from the repository.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> list [\-\-all] [<package\-file\-spec>...]\fP
+List all related packages.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> list \-\-installed [<package\-file\-spec>...]\fP
+List packages installed from the repository.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> list \-\-available [<package\-file\-spec>...]\fP
+List packages available in the repository but not currently installed on the system.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> list \-\-extras [<package\-file\-spec>...]\fP
+List packages installed from the repository that are not available in any repository.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> list \-\-obsoletes [<package\-file\-spec>...]\fP
+List packages in the repository that obsolete packages installed on the system.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> list \-\-recent [<package\-file\-spec>...]\fP
+List packages recently added into the repository.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> list \-\-upgrades [<package\-file\-spec>...]\fP
+List packages in the repository that upgrade packages installed on the system.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> move\-to [<package\-spec>...]\fP
+Reinstall all those packages that are available in the repository.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> reinstall [<package\-spec>...]\fP
+Run the \fBreinstall\-old\fP subcommand. If it fails, run the \fBmove\-to\fP subcommand.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> reinstall\-old [<package\-spec>...]\fP
+Reinstall all those packages that were installed from the repository and simultaneously are available in the repository.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> remove [<package\-spec>...]\fP
+Remove all packages installed from the repository along with any packages depending on the packages being removed. If \fBclean_requirements_on_remove\fP is enabled (the default) also removes any dependencies that are no longer needed.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> remove\-or\-distro\-sync [<package\-spec>...]\fP
+Select all packages installed from the repository. Upgrade, downgrade or keep those of them that are available in another repository to match the latest version available there and remove the others along with any packages depending on the packages being removed. If \fBclean_requirements_on_remove\fP is enabled (the default) also removes any dependencies that are no longer needed.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> remove\-or\-reinstall [<package\-spec>...]\fP
+Select all packages installed from the repository. Reinstall those of them that are available in another repository and remove the others along with any packages depending on the packages being removed. If \fBclean_requirements_on_remove\fP is enabled (the default) also removes any dependencies that are no longer needed.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> upgrade [<package\-spec>...]\fP
+Update all packages to the highest resolvable version available in the repository.
+When versions are specified in the \fB<package\-spec>\fP, update to these versions.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> upgrade\-to [<package\-specs>...]\fP
+A deprecated alias for the upgrade subcommand.
+.UNINDENT
+.SS Search Command
+.nf
+Command: \fBsearch\fP
+Aliases: \fBse\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] search [\-\-all] <keywords>...\fP
+Search package metadata for keywords. Keywords are matched as case\-insensitive substrings, globbing is supported.
+By default lists packages that match all requested keys (AND operation). Keys are searched in package names and summaries.
+If the "\-\-all" option is used, lists packages that match at least one of the keys (an OR operation).
+In addition the keys are searched in the package descriptions and URLs.
+The result is sorted from the most relevant results to the least.
+.UNINDENT
+.sp
+This command by default does not force a sync of expired metadata. See also \fI\%Metadata Synchronization\fP\&.
+.SS Shell Command
+.nf
+Command: \fBshell\fP
+Aliases: \fBsh\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] shell [filename]\fP
+Open an interactive shell for conducting multiple commands during a single execution of DNF. These commands can be issued manually
+or passed to DNF from a file. The commands are much the same as the normal DNF command line options. There are a few additional
+commands documented below.
+.INDENT 7.0
+.TP
+.B \fBconfig [conf\-option] [value]\fP
+.INDENT 7.0
+.IP \(bu 2
+Set a configuration option to a requested value. If no value is given it prints the current value.
+.UNINDENT
+.TP
+.B \fBrepo [list|enable|disable] [repo\-id]\fP
+.INDENT 7.0
+.IP \(bu 2
+list: list repositories and their status
+.IP \(bu 2
+enable: enable repository
+.IP \(bu 2
+disable: disable repository
+.UNINDENT
+.TP
+.B \fBtransaction [list|reset|solve|run]\fP
+.INDENT 7.0
+.IP \(bu 2
+list: resolve and list the content of the transaction
+.IP \(bu 2
+reset: reset the transaction
+.IP \(bu 2
+run: resolve and run the transaction
+.UNINDENT
+.UNINDENT
+.sp
+Note that all local packages must be used in the first shell transaction subcommand (e.g.
+\fIinstall /tmp/nodejs\-1\-1.x86_64.rpm /tmp/acpi\-1\-1.noarch.rpm\fP) otherwise an error will occur.
+Any \fIdisable\fP, \fIenable\fP, and \fIreset\fP module operations (e.g. \fImodule enable nodejs\fP) must also
+be performed before any other shell transaction subcommand is used.
+.UNINDENT
+.SS Swap Command
+.nf
+Command: \fBswap\fP
+.fi
+.sp
+.sp
+\fBdnf [options] swap <remove\-spec> <install\-spec>\fP
+.INDENT 0.0
+.INDENT 3.5
+Remove spec and install spec in one transaction. Each \fB<spec>\fP can be either a
+\fI\%<package\-spec>\fP, which specifies a package directly, or a
+\fB@<group\-spec>\fP, which specifies an (environment) group which contains it. Automatic
+conflict solving is provided in DNF by the \-\-allowerasing option that provides the functionality of the swap
+command automatically.
+.UNINDENT
+.UNINDENT
+.SS Updateinfo Command
+.nf
+Command: \fBupdateinfo\fP
+Aliases: \fBupif\fP
+Deprecated aliases: \fBlist\-updateinfo\fP, \fBlist\-security\fP, \fBlist\-sec\fP, \fBinfo\-updateinfo\fP, \fBinfo\-security\fP, \fBinfo\-sec\fP, \fBsummary\-updateinfo\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] updateinfo [\-\-summary|\-\-list|\-\-info] [<availability>] [<spec>...]\fP
+Display information about update advisories.
+.sp
+Depending on the output type, DNF displays just counts of advisory types
+(omitted or \fB\-\-summary\fP), list of advisories (\fB\-\-list\fP) or detailed
+information (\fB\-\-info\fP). The \fB\-v\fP option extends the output. When
+used with \fB\-\-info\fP, the information is even more detailed. When used
+with \fB\-\-list\fP, an additional column with date of the last advisory update
+is added.
+.sp
+\fB<availability>\fP specifies whether advisories about newer versions of
+installed packages (omitted or \fB\-\-available\fP), advisories about equal and
+older versions of installed packages (\fB\-\-installed\fP), advisories about
+newer versions of those installed packages for which a newer version is
+available (\fB\-\-updates\fP) or advisories about any versions of installed
+packages (\fB\-\-all\fP) are taken into account. Most of the time, \fB\-\-available\fP
+and \fB\-\-updates\fP displays the same output. The outputs differ only in the
+cases when an advisory refers to a newer version but there is no enabled
+repository which contains any newer version.
+.sp
+Note, that \fB\-\-available\fP takes only the latest installed versions of
+packages into account. In case of the kernel packages (when multiple
+version could be installed simultaneously) also packages of the currently
+running version of kernel are added.
+.sp
+To print only advisories referencing a CVE or a bugzilla use \fB\-\-with\-cve\fP or
+\fB\-\-with\-bz\fP options. When these switches are used also the output
+of the \fB\-\-list\fP is altered \- the ID of the CVE or the bugzilla is printed
+instead of the one of the advisory.
+.sp
+If given and if neither ID, type (\fBbugfix\fP, \fBenhancement\fP,
+\fBsecurity\fP/\fBsec\fP) nor a package name of an advisory matches
+\fB<spec>\fP, the advisory is not taken into account. The matching is
+case\-sensitive and in the case of advisory IDs and package names, globbing
+is supported.
+.sp
+Output of the \fB\-\-summary\fP option is affected by the autocheck_running_kernel configuration option.
+.UNINDENT
+.SS Upgrade Command
+.nf
+Command: \fBupgrade\fP
+Aliases: \fBup\fP
+Deprecated aliases: \fBupdate\fP, \fBupgrade\-to\fP, \fBupdate\-to\fP, \fBlocalupdate\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] upgrade\fP
+Updates each package to the latest version that is both available and
+resolvable.
+.TP
+.B \fBdnf [options] upgrade <package\-spec>...\fP
+Updates each specified package to the latest available version. Updates
+dependencies as necessary. When versions are specified in the
+\fB<package\-spec>\fP, update to these versions.
+.TP
+.B \fBdnf [options] upgrade @<spec>...\fP
+Alias for the \fIdnf module update\fP command.
+.UNINDENT
+.sp
+If the main \fBobsoletes\fP configure option is true or the \fB\-\-obsoletes\fP flag
+is present, dnf will include package obsoletes in its calculations.
+For more information see obsoletes\&.
+.sp
+See also \fI\%Configuration Files Replacement Policy\fP\&.
+.SS Upgrade\-Minimal Command
+.nf
+Command: \fBupgrade\-minimal\fP
+Aliases: \fBup\-min\fP
+Deprecated aliases: \fBupdate\-minimal\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] upgrade\-minimal\fP
+Updates each package to the latest available version that provides a bugfix, enhancement
+or a fix for a security issue (security).
+.TP
+.B \fBdnf [options] upgrade\-minimal <package\-spec>...\fP
+Updates each specified package to the latest available version that provides
+a bugfix, enhancement or a fix for security issue (security). Updates
+dependencies as necessary.
+.UNINDENT
+.SH SPECIFYING PACKAGES
+.sp
+Many commands take a \fB<package\-spec>\fP parameter that selects a package for
+the operation. The \fB<package\-spec>\fP argument is matched against package
+NEVRAs, provides and file provides.
+.sp
+\fB<package\-file\-spec>\fP is similar to \fB<package\-spec>\fP, except provides
+matching is not performed. Therefore, \fB<package\-file\-spec>\fP is matched only
+against NEVRAs and file provides.
+.sp
+\fB<package\-name\-spec>\fP is matched against NEVRAs only.
+.SS Globs
+.sp
+Package specification supports the same glob pattern matching that shell does,
+in all three above mentioned packages it matches against (NEVRAs, provides and
+file provides).
+.sp
+The following patterns are supported:
+.INDENT 0.0
+.TP
+.B \fB*\fP
+Matches any number of characters.
+.TP
+.B \fB?\fP
+Matches any single character.
+.TP
+.B \fB[]\fP
+Matches any one of the enclosed characters. A pair of characters separated
+by a hyphen denotes a range expression; any character that falls between
+those two characters, inclusive, is matched. If the first character
+following the \fB[\fP is a \fB!\fP or a \fB^\fP then any character not enclosed
+is matched.
+.UNINDENT
+.sp
+Note: Curly brackets (\fB{}\fP) are not supported. You can still use them in
+shells that support them and let the shell do the expansion, but if quoted or
+escaped, dnf will not expand them.
+.SS NEVRA Matching
+.sp
+When matching against NEVRAs, partial matching is supported. DNF tries to match
+the spec against the following list of NEVRA forms (in decreasing order of
+priority):
+.INDENT 0.0
+.IP \(bu 2
+\fBname\-[epoch:]version\-release.arch\fP
+.IP \(bu 2
+\fBname.arch\fP
+.IP \(bu 2
+\fBname\fP
+.IP \(bu 2
+\fBname\-[epoch:]version\-release\fP
+.IP \(bu 2
+\fBname\-[epoch:]version\fP
+.UNINDENT
+.sp
+Note that \fBname\fP can in general contain dashes (e.g. \fBpackage\-with\-dashes\fP).
+.sp
+The first form that matches any packages is used and the remaining forms are
+not tried. If none of the forms match any packages, an attempt is made to match
+the \fB<package\-spec>\fP against full package NEVRAs. This is only relevant
+if globs are present in the \fB<package\-spec>\fP\&.
+.sp
+\fB<package\-spec>\fP matches NEVRAs the same way \fB<package\-name\-spec>\fP does,
+but in case matching NEVRAs fails, it attempts to match against provides and
+file provides of packages as well.
+.sp
+You can specify globs as part of any of the five NEVRA components. You can also
+specify a glob pattern to match over multiple NEVRA components (in other words,
+to match across the NEVRA separators). In that case, however, you need to write
+the spec to match against full package NEVRAs, as it is not possible to split
+such spec into NEVRA forms.
+.SS Specifying NEVRA Matching Explicitly
+.sp
+Some commands (\fBautoremove\fP, \fBinstall\fP, \fBremove\fP and \fBrepoquery\fP) also
+have aliases with suffixes \fB\-n\fP, \fB\-na\fP and \fB\-nevra\fP that allow to
+explicitly specify how to parse the arguments:
+.INDENT 0.0
+.IP \(bu 2
+Command \fBinstall\-n\fP only matches against \fBname\fP\&.
+.IP \(bu 2
+Command \fBinstall\-na\fP only matches against \fBname.arch\fP\&.
+.IP \(bu 2
+Command \fBinstall\-nevra\fP only matches against \fBname\-[epoch:]version\-release.arch\fP\&.
+.UNINDENT
+.SH SPECIFYING PROVIDES
+.sp
+\fB<provide\-spec>\fP in command descriptions means the command operates on
+packages providing the given spec. This can either be an explicit provide, an
+implicit provide (i.e. name of the package) or a file provide. The selection is
+case\-sensitive and globbing is supported.
+.SS Specifying File Provides
+.sp
+If a spec starts with either \fB/\fP or \fB*/\fP, it is considered as a potential file provide.
+.SH SPECIFYING GROUPS
+.sp
+\fB<group\-spec>\fP allows one to select (environment) groups a particular operation should work
+on. It is a case insensitive string (supporting globbing characters) that is
+matched against a group\(aqs ID, canonical name and name translated into the
+current LC_MESSAGES locale (if possible).
+.SH SPECIFYING MODULES
+.sp
+\fB<module\-spec>\fP allows one to select modules or profiles a particular operation should work
+on.
+.sp
+It is in the form of \fBNAME:STREAM:VERSION:CONTEXT:ARCH/PROFILE\fP and supported partial forms are the following:
+.INDENT 0.0
+.IP \(bu 2
+\fBNAME\fP
+.IP \(bu 2
+\fBNAME:STREAM\fP
+.IP \(bu 2
+\fBNAME:STREAM:VERSION\fP
+.IP \(bu 2
+\fBNAME:STREAM:VERSION:CONTEXT\fP
+.IP \(bu 2
+all above combinations with \fB::ARCH\fP (e.g. \fBNAME::ARCH\fP)
+.IP \(bu 2
+\fBNAME:STREAM:VERSION:CONTEXT:ARCH\fP
+.IP \(bu 2
+all above combinations with \fB/PROFILE\fP (e.g. \fBNAME/PROFILE\fP)
+.UNINDENT
+.sp
+In case stream is not specified, the enabled or the default stream is used, in this order. In case profile is not specified, the system default profile or the \(aqdefault\(aq profile is used.
+.SH SPECIFYING TRANSACTIONS
+.sp
+\fB<transaction\-spec>\fP can be in one of several forms. If it is an integer, it
+specifies a transaction ID. Specifying \fBlast\fP is the same as specifying the ID
+of the most recent transaction. The last form is \fBlast\-<offset>\fP, where
+\fB<offset>\fP is a positive integer. It specifies offset\-th transaction preceding
+the most recent transaction.
+.SH PACKAGE FILTERING
+.sp
+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.
+.SS Exclude Filtering
+.sp
+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 \-\fI\%\-disableexcludes\fP
+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 \-\fI\%\-disableplugin\fP command line option.
+.sp
+To disable all excludes for e.g. the install command you can use the following combination
+of command line options:
+.sp
+\fBdnf \-\-disableexcludes=all \-\-disableplugin="*" install bash\fP
+.SS Modular Filtering
+.sp
+Please see the modularity documentation for details on how Modular
+Filtering works.
+.sp
+With modularity, only RPM packages from \fBactive\fP module streams are included in the available
+package set. RPM packages from \fBinactive\fP module streams, as well as non\-modular packages with
+the same name or provides as a package from an \fBactive\fP module stream, are filtered out. Modular
+filtering is not applied to packages added from the command line, installed packages, or packages
+from repositories with \fBmodule_hotfixes=true\fP in their \fB\&.repo\fP file.
+.sp
+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
+\fBmodule_hotfixes=true\fP in the \fB\&.repo\fP file or use \fB\-\-setopt=<repo_id>.module_hotfixes=true\fP\&.
+.sp
+To discover the module which contains an excluded package use
+\fI\%dnf module provides\fP\&.
+.SH METADATA SYNCHRONIZATION
+.sp
+Correct operation of DNF depends on having access to up\-to\-date data from all enabled repositories but contacting remote mirrors on every operation considerably slows it down and costs bandwidth for both the client and the repository provider. The metadata_expire (see \fBdnf.conf(5)\fP) repository configuration option is used by DNF to determine whether a particular local copy of repository data is due to be re\-synced. It is crucial that the repository providers set the option well, namely to a value where it is guaranteed that if particular metadata was available in time \fBT\fP on the server, then all packages it references will still be available for download from the server in time \fBT + metadata_expire\fP\&.
+.sp
+To further reduce the bandwidth load, some of the commands where having up\-to\-date metadata is not critical (e.g. the \fBlist\fP command) do not look at whether a repository is expired and whenever any version of it is locally available to the user\(aqs account, it will be used. For non\-root use, see also the \fB\-\-cacheonly\fP switch. Note that in all situations the user can force synchronization of all enabled repositories with the \fB\-\-refresh\fP switch.
+.SH CONFIGURATION FILES REPLACEMENT POLICY
+.sp
+The updated packages could replace the old modified configuration files
+with the new ones or keep the older files. Neither of the files are actually replaced.
+To the conflicting ones RPM gives additional suffix to the origin name. Which file
+should maintain the true name after transaction is not controlled by package manager
+but is specified by each package itself, following packaging guideline.
+.SH FILES
+.INDENT 0.0
+.TP
+.B \fBCache Files\fP
+/var/cache/dnf
+.TP
+.B \fBMain Configuration\fP
+/etc/dnf/dnf.conf
+.TP
+.B \fBRepository\fP
+/etc/yum.repos.d/
+.UNINDENT
+.SH SEE ALSO
+.INDENT 0.0
+.IP \(bu 2
+\fBdnf.conf(5)\fP, DNF Configuration Reference
+.IP \(bu 2
+\fBdnf\-PLUGIN(8)\fP for documentation on DNF plugins.
+.IP \(bu 2
+\fBdnf.modularity(7)\fP, Modularity overview\&.
+.IP \(bu 2
+\fBdnf\-transaction\-json(5)\fP, Stored Transaction JSON Format Specification\&.
+.IP \(bu 2
+\fI\%DNF\fP project homepage (\fI\%https://github.com/rpm\-software\-management/dnf/\fP)
+.IP \(bu 2
+How to report a bug (\fI\%https://github.com/rpm\-software\-management/dnf/wiki/Bug\-Reporting\fP)
+.IP \(bu 2
+\fI\%YUM\fP project homepage (\fI\%http://yum.baseurl.org/\fP)
+.UNINDENT
+.SH AUTHOR
+See AUTHORS in DNF source distribution.
+.SH COPYRIGHT
+2012-2022, Red Hat, Licensed under GPLv2+
+.\" Generated by docutils manpage writer.
+.
diff --git a/yum.8 b/yum.8
new file mode 100644
index 0000000..7d6a78d
--- /dev/null
+++ b/yum.8
@@ -0,0 +1,2123 @@
+.\" Man page generated from reStructuredText.
+.
+.
+.nr rst2man-indent-level 0
+.
+.de1 rstReportMargin
+\\$1 \\n[an-margin]
+level \\n[rst2man-indent-level]
+level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
+-
+\\n[rst2man-indent0]
+\\n[rst2man-indent1]
+\\n[rst2man-indent2]
+..
+.de1 INDENT
+.\" .rstReportMargin pre:
+. RS \\$1
+. nr rst2man-indent\\n[rst2man-indent-level] \\n[an-margin]
+. nr rst2man-indent-level +1
+.\" .rstReportMargin post:
+..
+.de UNINDENT
+. RE
+.\" indent \\n[an-margin]
+.\" old: \\n[rst2man-indent\\n[rst2man-indent-level]]
+.nr rst2man-indent-level -1
+.\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
+.in \\n[rst2man-indent\\n[rst2man-indent-level]]u
+..
+.TH "YUM" "8" "Apr 29, 2022" "4.12.0" "DNF"
+.SH NAME
+yum \- redirecting to DNF Command Reference
+.SH SYNOPSIS
+.sp
+\fBdnf [options] <command> [<args>...]\fP
+.SH DESCRIPTION
+.sp
+\fI\%DNF\fP is the next upcoming major version of \fI\%YUM\fP, a package manager for RPM\-based Linux
+distributions. It roughly maintains CLI compatibility with YUM and defines a strict API for
+extensions and plugins.
+.sp
+Plugins can modify or extend features of DNF or provide additional CLI commands on top of those
+mentioned below. If you know the name of such a command (including commands mentioned below), you
+may find/install the package which provides it using the appropriate virtual provide in the form of
+\fBdnf\-command(<alias>)\fP, where \fB<alias>\fP is the name of the command; e.g.\(ga\(gadnf install
+\(aqdnf\-command(versionlock)\(aq\(ga\(ga installs a \fBversionlock\fP plugin. This approach also applies to
+specifying dependencies of packages that require a particular DNF command.
+.sp
+Return values:
+.INDENT 0.0
+.IP \(bu 2
+\fB0\fP  : Operation was successful.
+.IP \(bu 2
+\fB1\fP  : An error occurred, which was handled by dnf.
+.IP \(bu 2
+\fB3\fP  : An unknown unhandled error occurred during operation.
+.IP \(bu 2
+\fB100\fP: See \fI\%check\-update\fP
+.IP \(bu 2
+\fB200\fP: There was a problem with acquiring or releasing of locks.
+.UNINDENT
+.sp
+Available commands:
+.INDENT 0.0
+.IP \(bu 2
+\fI\%alias\fP
+.IP \(bu 2
+\fI\%autoremove\fP
+.IP \(bu 2
+\fI\%check\fP
+.IP \(bu 2
+\fI\%check\-update\fP
+.IP \(bu 2
+\fI\%clean\fP
+.IP \(bu 2
+\fI\%deplist\fP
+.IP \(bu 2
+\fI\%distro\-sync\fP
+.IP \(bu 2
+\fI\%downgrade\fP
+.IP \(bu 2
+\fI\%group\fP
+.IP \(bu 2
+\fI\%help\fP
+.IP \(bu 2
+\fI\%history\fP
+.IP \(bu 2
+\fI\%info\fP
+.IP \(bu 2
+\fI\%install\fP
+.IP \(bu 2
+\fI\%list\fP
+.IP \(bu 2
+\fI\%makecache\fP
+.IP \(bu 2
+\fI\%mark\fP
+.IP \(bu 2
+\fI\%module\fP
+.IP \(bu 2
+\fI\%provides\fP
+.IP \(bu 2
+\fI\%reinstall\fP
+.IP \(bu 2
+\fI\%remove\fP
+.IP \(bu 2
+\fI\%repoinfo\fP
+.IP \(bu 2
+\fI\%repolist\fP
+.IP \(bu 2
+\fI\%repoquery\fP
+.IP \(bu 2
+\fI\%repository\-packages\fP
+.IP \(bu 2
+\fI\%search\fP
+.IP \(bu 2
+\fI\%shell\fP
+.IP \(bu 2
+\fI\%swap\fP
+.IP \(bu 2
+\fI\%updateinfo\fP
+.IP \(bu 2
+\fI\%upgrade\fP
+.IP \(bu 2
+\fI\%upgrade\-minimal\fP
+.UNINDENT
+.sp
+Additional information:
+.INDENT 0.0
+.IP \(bu 2
+\fI\%Options\fP
+.IP \(bu 2
+\fI\%Specifying Packages\fP
+.IP \(bu 2
+\fI\%Specifying Provides\fP
+.IP \(bu 2
+\fI\%Specifying File Provides\fP
+.IP \(bu 2
+\fI\%Specifying Groups\fP
+.IP \(bu 2
+\fI\%Specifying Transactions\fP
+.IP \(bu 2
+\fI\%Metadata Synchronization\fP
+.IP \(bu 2
+\fI\%Configuration Files Replacement Policy\fP
+.IP \(bu 2
+\fI\%Files\fP
+.IP \(bu 2
+\fI\%See Also\fP
+.UNINDENT
+.SH OPTIONS
+.INDENT 0.0
+.TP
+.B \fB\-4\fP
+Resolve to IPv4 addresses only.
+.TP
+.B \fB\-6\fP
+Resolve to IPv6 addresses only.
+.TP
+.B \fB\-\-advisory=<advisory>, \-\-advisories=<advisory>\fP
+Include packages corresponding to the advisory ID, Eg. FEDORA\-2201\-123.
+Applicable for the install, repoquery, updateinfo and upgrade commands.
+.TP
+.B \fB\-\-allowerasing\fP
+Allow erasing of installed packages to resolve dependencies. This option could be used as an alternative to the \fByum swap\fP command where packages to remove are not explicitly defined.
+.TP
+.B \fB\-\-assumeno\fP
+Automatically answer no for all questions.
+.TP
+.B \fB\-b, \-\-best\fP
+Try the best available package versions in transactions. Specifically during \fI\%dnf upgrade\fP, which by default skips over updates that can not be installed for dependency reasons, the switch forces DNF to only consider the latest packages. When running into packages with broken dependencies, DNF will fail giving a reason why the latest version can not be installed.
+.sp
+Note that the use of the newest available version is only guaranteed for
+the packages directly requested (e.g. as a command line arguments), and the
+solver may use older versions of dependencies to meet their requirements.
+.TP
+.B \fB\-\-bugfix\fP
+Include packages that fix a bugfix issue. Applicable for the install, repoquery, updateinfo and
+upgrade commands.
+.TP
+.B \fB\-\-bz=<bugzilla>, \-\-bzs=<bugzilla>\fP
+Include packages that fix a Bugzilla ID, Eg. 123123. Applicable for the install, repoquery,
+updateinfo and upgrade commands.
+.TP
+.B \fB\-C, \-\-cacheonly\fP
+Run entirely from system cache, don\(aqt update the cache and use it even in case it is expired.
+.sp
+DNF uses a separate cache for each user under which it executes. The cache for the root user is called the system cache. This switch allows a regular user read\-only access to the system cache, which usually is more fresh than the user\(aqs and thus he does not have to wait for metadata sync.
+.TP
+.B \fB\-\-color=<color>\fP
+Control whether color is used in terminal output. Valid values are \fBalways\fP, \fBnever\fP and \fBauto\fP (default).
+.TP
+.B \fB\-\-comment=<comment>\fP
+Add a comment to the transaction history.
+.TP
+.B \fB\-c <config file>, \-\-config=<config file>\fP
+Configuration file location.
+.TP
+.B \fB\-\-cve=<cves>, \-\-cves=<cves>\fP
+Include packages that fix a CVE (Common Vulnerabilities and Exposures) ID
+(\fI\%http://cve.mitre.org/about/\fP), Eg. CVE\-2201\-0123. Applicable for the install, repoquery, updateinfo,
+and upgrade commands.
+.TP
+.B \fB\-d <debug level>, \-\-debuglevel=<debug level>\fP
+Debugging output level. This is an integer value between 0 (no additional information strings) and 10 (shows all debugging information, even that not understandable to the user), default is 2. Deprecated, use \fB\-v\fP instead.
+.TP
+.B \fB\-\-debugsolver\fP
+Dump data aiding in dependency solver debugging into \fB\&./debugdata\fP\&.
+.UNINDENT
+.sp
+\fB\-\-disableexcludes=[all|main|<repoid>], \-\-disableexcludepkgs=[all|main|<repoid>]\fP
+.INDENT 0.0
+.INDENT 3.5
+Disable the configuration file excludes. Takes one of the following three options:
+.INDENT 0.0
+.IP \(bu 2
+\fBall\fP, disables all configuration file excludes
+.IP \(bu 2
+\fBmain\fP, disables excludes defined in the \fB[main]\fP section
+.IP \(bu 2
+\fBrepoid\fP, disables excludes defined for the given repository
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-disable, \-\-set\-disabled\fP
+Disable specified repositories (automatically saves). The option has to be used together with the
+\fBconfig\-manager\fP command (dnf\-plugins\-core).
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-disableplugin=<plugin names>\fP
+Disable the listed plugins specified by names or globs.
+.TP
+.B \fB\-\-disablerepo=<repoid>\fP
+Temporarily disable active repositories for the purpose of the current dnf command.
+Accepts an id, a comma\-separated list of ids, or a glob of ids. This option can be
+specified multiple times, but is mutually exclusive with \fB\-\-repo\fP\&.
+.TP
+.B \fB\-\-downloaddir=<path>, \-\-destdir=<path>\fP
+Redirect downloaded packages to provided directory. The option has to be used together with the \-\fI\%\-downloadonly\fP command line option, with the
+\fBdownload\fP, \fBmodulesync\fP or \fBreposync\fP commands (dnf\-plugins\-core) or with the \fBsystem\-upgrade\fP command
+(dnf\-plugins\-extras).
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-downloadonly\fP
+Download the resolved package set without performing any rpm transaction (install/upgrade/erase).
+.TP
+.B \fB\-e <error level>, \-\-errorlevel=<error level>\fP
+Error output level. This is an integer value between 0 (no error output) and
+10 (shows all error messages), default is 3. Deprecated, use \fB\-v\fP instead.
+.TP
+.B \fB\-\-enable, \-\-set\-enabled\fP
+Enable specified repositories (automatically saves). The option has to be used together with the
+\fBconfig\-manager\fP command (dnf\-plugins\-core).
+.TP
+.B \fB\-\-enableplugin=<plugin names>\fP
+Enable the listed plugins specified by names or globs.
+.TP
+.B \fB\-\-enablerepo=<repoid>\fP
+Temporarily enable additional repositories for the purpose of the current dnf command.
+Accepts an id, a comma\-separated list of ids, or a glob of ids. This option can be
+specified multiple times.
+.TP
+.B \fB\-\-enhancement\fP
+Include enhancement relevant packages. Applicable for the install, repoquery, updateinfo and
+upgrade commands.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-x <package\-file\-spec>, \-\-exclude=<package\-file\-spec>\fP
+Exclude packages specified by \fB<package\-file\-spec>\fP from the operation.
+.TP
+.B \fB\-\-excludepkgs=<package\-file\-spec>\fP
+Deprecated option. It was replaced by the \-\fI\%\-exclude\fP option.
+.TP
+.B \fB\-\-forcearch=<arch>\fP
+Force the use of an architecture. Any architecture can be specified.
+However, use of an architecture not supported natively by your CPU will
+require emulation of some kind. This is usually through QEMU. The behavior of \fB\-\-forcearch\fP
+can be configured by using the arch and ignorearch
+configuration options with values \fB<arch>\fP and \fBTrue\fP respectively.
+.TP
+.B \fB\-h, \-\-help, \-\-help\-cmd\fP
+Show the help.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-installroot=<path>\fP
+Specifies an alternative installroot, relative to where all packages will be
+installed. Think of this like doing \fBchroot <root> dnf\fP, except using
+\fB\-\-installroot\fP allows dnf to work before the chroot is created. It requires absolute path.
+.UNINDENT
+.INDENT 0.0
+.IP \(bu 2
+\fIcachedir\fP, \fIlog files\fP, \fIreleasever\fP, and \fIgpgkey\fP are taken from or
+stored in the installroot. \fIGpgkeys\fP are imported into the installroot from
+a path relative to the host which can be specified in the repository section
+of configuration files.
+.IP \(bu 2
+\fIconfiguration file\fP and reposdir are searched inside the installroot first. If
+they are not present, they are taken from the host system.
+Note:  When a path is specified within a command line argument
+(\fB\-\-config=<config file>\fP in case of \fIconfiguration file\fP and
+\fB\-\-setopt=reposdir=<reposdir>\fP for \fIreposdir\fP) then this path is always
+relative to the host with no exceptions.
+.IP \(bu 2
+\fIvars\fP are taken from the host system or installroot according to reposdir
+\&. When \fIreposdir\fP path is specified within a command line argument, vars are taken from the
+installroot. When varsdir paths are specified within a command line
+argument (\fB\-\-setopt=varsdir=<reposdir>\fP) then those path are always relative to the host with no
+exceptions.
+.IP \(bu 2
+The \fIpluginpath\fP and \fIpluginconfpath\fP are relative to the host.
+.UNINDENT
+.INDENT 0.0
+.INDENT 3.5
+Note: You may also want to use the command\-line option
+\fB\-\-releasever=<release>\fP when creating the installroot, otherwise the
+\fI$releasever\fP value is taken from the rpmdb within the installroot (and thus
+it is empty at the time of creation and the transaction will fail). If \fB\-\-releasever=/\fP is used, the
+releasever will be detected from the host (\fB/\fP) system. The new installroot path at the time of creation
+does not contain the \fIrepository\fP, \fIreleasever\fP and \fIdnf.conf\fP files.
+.sp
+On a modular system you may also want to use the
+\fB\-\-setopt=module_platform_id=<module_platform_name:stream>\fP command\-line option when creating the installroot,
+otherwise the module_platform_id value will be taken from the
+\fB/etc/os\-release\fP file within the installroot (and thus it will be empty at the time of creation, the modular
+dependency could be unsatisfied and modules content could be excluded).
+.sp
+Installroot examples:
+.INDENT 0.0
+.TP
+.B \fBdnf \-\-installroot=<installroot> \-\-releasever=<release> install system\-release\fP
+Permanently sets the \fBreleasever\fP of the system in the
+\fB<installroot>\fP directory to \fB<release>\fP\&.
+.TP
+.B \fBdnf \-\-installroot=<installroot> \-\-setopt=reposdir=<path> \-\-config /path/dnf.conf upgrade\fP
+Upgrades packages inside the installroot from a repository described by
+\fB\-\-setopt\fP using configuration from \fB/path/dnf.conf\fP\&.
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-newpackage\fP
+Include newpackage relevant packages. Applicable for the install, repoquery, updateinfo and
+upgrade commands.
+.TP
+.B \fB\-\-noautoremove\fP
+Disable removal of dependencies that are no longer used. It sets
+clean_requirements_on_remove configuration option to \fBFalse\fP\&.
+.TP
+.B \fB\-\-nobest\fP
+Set best option to \fBFalse\fP, so that transactions are not limited to best candidates only.
+.TP
+.B \fB\-\-nodocs\fP
+Do not install documentation. Sets the rpm flag \(aqRPMTRANS_FLAG_NODOCS\(aq.
+.TP
+.B \fB\-\-nogpgcheck\fP
+Skip checking GPG signatures on packages (if RPM policy allows).
+.TP
+.B \fB\-\-noplugins\fP
+Disable all plugins.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-obsoletes\fP
+This option has an effect on an install/update, it enables
+dnf\(aqs obsoletes processing logic. For more information see the
+obsoletes option.
+.sp
+This option also displays capabilities that the package obsoletes when used together with the \fI\%repoquery\fP command.
+.sp
+Configuration Option: obsoletes
+.TP
+.B \fB\-q, \-\-quiet\fP
+In combination with a non\-interactive command, shows just the relevant content. Suppresses messages notifying about the current state or actions of DNF.
+.TP
+.B \fB\-R <minutes>, \-\-randomwait=<minutes>\fP
+Maximum command wait time.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-refresh\fP
+Set metadata as expired before running the command.
+.TP
+.B \fB\-\-releasever=<release>\fP
+Configure DNF as if the distribution release was \fB<release>\fP\&. This can
+affect cache paths, values in configuration files and mirrorlist URLs.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-repofrompath <repo>,<path/url>\fP
+Specify a repository to add to the repositories for this query.
+This option can be used multiple times.
+.UNINDENT
+.INDENT 0.0
+.IP \(bu 2
+The repository label is specified by \fB<repo>\fP\&.
+.IP \(bu 2
+The path or url to the repository is specified by \fB<path/url>\fP\&.
+It is the same path as a baseurl and can be also enriched by the
+repo variables\&.
+.IP \(bu 2
+The configuration for the repository can be adjusted using \-\fI\%\-setopt\fP=<repo>.<option>=<value>.
+.IP \(bu 2
+If you want to view only packages from this repository, combine this
+with the \fB\-\-repo=<repo>\fP or \fB\-\-disablerepo="*"\fP switches.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-repo=<repoid>, \-\-repoid=<repoid>\fP
+Enable just specific repositories by an id or a glob. Can be used multiple
+times with accumulative effect. It is basically a shortcut for
+\fB\-\-disablerepo="*" \-\-enablerepo=<repoid>\fP and is mutually exclusive with
+the \fB\-\-disablerepo\fP option.
+.TP
+.B \fB\-\-rpmverbosity=<name>\fP
+RPM debug scriptlet output level. Sets the debug level to \fB<name>\fP for RPM scriptlets.
+For available levels, see the \fBrpmverbosity\fP configuration option.
+.TP
+.B \fB\-\-sec\-severity=<severity>, \-\-secseverity=<severity>\fP
+Includes packages that provide a fix for an issue of the specified severity.
+Applicable for the install, repoquery, updateinfo and upgrade commands.
+.TP
+.B \fB\-\-security\fP
+Includes packages that provide a fix for a security issue. Applicable for the
+upgrade command.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-setopt=<option>=<value>\fP
+Override a configuration option from the configuration file. To override configuration options for repositories, use
+\fBrepoid.option\fP for the \fB<option>\fP\&. Values for configuration options like \fBexcludepkgs\fP, \fBincludepkgs\fP,
+\fBinstallonlypkgs\fP and \fBtsflags\fP are appended to the original value, they do not override it. However, specifying
+an empty value (e.g. \fB\-\-setopt=tsflags=\fP) will clear the option.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-skip\-broken\fP
+Resolve depsolve problems by removing packages that are causing problems from the transaction.
+It is an alias for the strict configuration option with value \fBFalse\fP\&.
+Additionally, with the \fI\%enable\fP and
+\fI\%disable\fP module subcommands it allows one to perform an action even in case of
+broken modular dependencies.
+.TP
+.B \fB\-\-showduplicates\fP
+Show duplicate packages in repositories. Applicable for the list and search commands.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-v, \-\-verbose\fP
+Verbose operation, show debug messages.
+.TP
+.B \fB\-\-version\fP
+Show DNF version and exit.
+.TP
+.B \fB\-y, \-\-assumeyes\fP
+Automatically answer yes for all questions.
+.UNINDENT
+.sp
+List options are comma\-separated. Command\-line options override respective settings from configuration files.
+.SH COMMANDS
+.sp
+For an explanation of \fB<package\-spec>\fP, \fB<package\-file\-spec>\fP and \fB<package\-name\-spec>\fP see
+\fI\%Specifying Packages\fP\&.
+.sp
+For an explanation of \fB<provide\-spec>\fP see \fI\%Specifying Provides\fP\&.
+.sp
+For an explanation of \fB<group\-spec>\fP see \fI\%Specifying Groups\fP\&.
+.sp
+For an explanation of \fB<module\-spec>\fP see \fI\%Specifying Modules\fP\&.
+.sp
+For an explanation of \fB<transaction\-spec>\fP see \fI\%Specifying Transactions\fP\&.
+.SS Alias Command
+.nf
+Command: \fBalias\fP
+.fi
+.sp
+.sp
+Allows the user to define and manage a list of aliases (in the form \fB<name=value>\fP),
+which can be then used as dnf commands to abbreviate longer command sequences. For examples on using
+the alias command, see \fI\%Alias Examples\fP\&. For examples on the alias
+processing, see \fI\%Alias Processing Examples\fP\&.
+.sp
+To use an alias (name=value), the name must be placed as the first "command" (e.g. the first argument
+that is not an option). It is then replaced by its value and the resulting sequence is again searched
+for aliases. The alias processing stops when the first found command is not a name of any alias.
+.sp
+In case the processing would result in an infinite recursion, the original arguments are used instead.
+.sp
+Also, like in shell aliases, if the result starts with a \fB\e\fP, the alias processing will stop.
+.sp
+All aliases are defined in configuration files in the \fB/etc/dnf/aliases.d/\fP directory in the [aliases] section,
+and aliases created by the alias command are written to the \fBUSER.conf\fP file. In case of conflicts,
+the \fBUSER.conf\fP has the highest priority, and alphabetical ordering is used for the rest of the
+configuration files.
+.sp
+Optionally, there is the \fBenabled\fP option in the \fB[main]\fP section defaulting to True. This can be set for each
+file separately in the respective file, or globally for all aliases in the \fBALIASES.conf\fP file.
+.sp
+\fBdnf alias [options] [list] [<name>...]\fP
+.INDENT 0.0
+.INDENT 3.5
+List aliases with their final result. The \fB[<alias>...]\fP parameter further limits the result to only those aliases matching it.
+.UNINDENT
+.UNINDENT
+.sp
+\fBdnf alias [options] add <name=value>...\fP
+.INDENT 0.0
+.INDENT 3.5
+Create new aliases.
+.UNINDENT
+.UNINDENT
+.sp
+\fBdnf alias [options] delete <name>...\fP
+.INDENT 0.0
+.INDENT 3.5
+Delete aliases.
+.UNINDENT
+.UNINDENT
+.SS Alias Examples
+.INDENT 0.0
+.TP
+.B \fBdnf alias list\fP
+Lists all defined aliases.
+.TP
+.B \fBdnf alias add rm=remove\fP
+Adds a new command alias called \fBrm\fP which works the same as the \fBremove\fP command.
+.TP
+.B \fBdnf alias add upgrade="\eupgrade \-\-skip\-broken \-\-disableexcludes=all \-\-obsoletes"\fP
+Adds a new command alias called \fBupgrade\fP which works the same as the \fBupgrade\fP command,
+with additional options. Note that the original \fBupgrade\fP command is prefixed with a \fB\e\fP
+to prevent an infinite loop in alias processing.
+.UNINDENT
+.SS Alias Processing Examples
+.sp
+If there are defined aliases \fBin=install\fP and \fBFORCE="\-\-skip\-broken \-\-disableexcludes=all"\fP:
+.INDENT 0.0
+.IP \(bu 2
+\fBdnf FORCE in\fP will be replaced with \fBdnf \-\-skip\-broken \-\-disableexcludes=all install\fP
+.IP \(bu 2
+\fBdnf in FORCE\fP will be replaced with \fBdnf install FORCE\fP (which will fail)
+.UNINDENT
+.sp
+If there is defined alias \fBin=install\fP:
+.INDENT 0.0
+.IP \(bu 2
+\fBdnf in\fP will be replaced with \fBdnf install\fP
+.IP \(bu 2
+\fBdnf \-\-repo updates in\fP will be replaced with \fBdnf \-\-repo updates in\fP (which will fail)
+.UNINDENT
+.SS Autoremove Command
+.nf
+Command: \fBautoremove\fP
+Aliases for \fI\%explicit NEVRA matching\fP: \fBautoremove\-n\fP, \fBautoremove\-na\fP, \fBautoremove\-nevra\fP
+.fi
+.sp
+.sp
+\fBdnf [options] autoremove\fP
+.INDENT 0.0
+.INDENT 3.5
+Removes all "leaf" packages from the system that were originally installed as dependencies of user\-installed packages, but which are no longer required by any such package.
+.UNINDENT
+.UNINDENT
+.sp
+Packages listed in installonlypkgs are never automatically removed by
+this command.
+.sp
+\fBdnf [options] autoremove <spec>...\fP
+.INDENT 0.0
+.INDENT 3.5
+This is an alias for the \fI\%Remove Command\fP command with clean_requirements_on_remove set to
+\fBTrue\fP\&. It removes the specified packages from the system along with any packages depending on the
+packages being removed. Each \fB<spec>\fP can be either a \fB<package\-spec>\fP, which specifies a
+package directly, or a \fB@<group\-spec>\fP, which specifies an (environment) group which contains
+it. It also removes any dependencies that are no longer needed.
+.sp
+There are also a few specific autoremove commands \fBautoremove\-n\fP, \fBautoremove\-na\fP and
+\fBautoremove\-nevra\fP that allow the specification of an exact argument in the NEVRA
+(name\-epoch:version\-release.architecture) format.
+.UNINDENT
+.UNINDENT
+.sp
+This command by default does not force a sync of expired metadata. See also \fI\%Metadata Synchronization\fP\&.
+.SS Check Command
+.nf
+Command: \fBcheck\fP
+.fi
+.sp
+.sp
+\fBdnf [options] check [\-\-dependencies] [\-\-duplicates] [\-\-obsoleted] [\-\-provides]\fP
+.INDENT 0.0
+.INDENT 3.5
+Checks the local packagedb and produces information on any problems it
+finds. You can limit the checks to be performed by using the \fB\-\-dependencies\fP,
+\fB\-\-duplicates\fP, \fB\-\-obsoleted\fP and \fB\-\-provides\fP options (the default is to
+check everything).
+.UNINDENT
+.UNINDENT
+.SS Check\-Update Command
+.nf
+Command: \fBcheck\-update\fP
+Aliases: \fBcheck\-upgrade\fP
+.fi
+.sp
+.sp
+\fBdnf [options] check\-update [\-\-changelogs] [<package\-file\-spec>...]\fP
+.INDENT 0.0
+.INDENT 3.5
+Non\-interactively checks if updates of the specified packages are available. If no \fB<package\-file\-spec>\fP is given, checks whether any updates at all are available for your system. DNF exit code will be 100 when there are updates available and a list of the updates will be printed, 0 if not and 1 if an error occurs. If \fB\-\-changelogs\fP option is specified, also changelog delta of packages about to be updated is printed.
+.sp
+Please note that having a specific newer version available for an installed package (and reported by \fBcheck\-update\fP) does not imply that subsequent \fBdnf upgrade\fP will install it. The difference is that \fBdnf upgrade\fP has restrictions (like package dependencies being satisfied) to take into account.
+.sp
+The output is affected by the autocheck_running_kernel configuration option.
+.UNINDENT
+.UNINDENT
+.SS Clean Command
+.nf
+Command: \fBclean\fP
+.fi
+.sp
+.sp
+Performs cleanup of temporary files kept for repositories. This includes any
+such data left behind from disabled or removed repositories as well as for
+different distribution release versions.
+.INDENT 0.0
+.TP
+.B \fBdnf clean dbcache\fP
+Removes cache files generated from the repository metadata. This forces DNF
+to regenerate the cache files the next time it is run.
+.TP
+.B \fBdnf clean expire\-cache\fP
+Marks the repository metadata expired. DNF will re\-validate the cache for
+each repository the next time it is used.
+.TP
+.B \fBdnf clean metadata\fP
+Removes repository metadata. Those are the files which DNF uses to determine
+the remote availability of packages. Using this option will make DNF
+download all the metadata the next time it is run.
+.TP
+.B \fBdnf clean packages\fP
+Removes any cached packages from the system.
+.TP
+.B \fBdnf clean all\fP
+Does all of the above.
+.UNINDENT
+.SS Deplist Command
+.INDENT 0.0
+.TP
+.B \fBdnf [options] deplist [<select\-options>] [<query\-options>] [<package\-spec>]\fP
+Deprecated alias for \fI\%dnf repoquery \-\-deplist\fP\&.
+.UNINDENT
+.SS Distro\-Sync Command
+.nf
+Command: \fBdistro\-sync\fP
+Aliases: \fBdsync\fP
+Deprecated aliases: \fBdistrosync\fP, \fBdistribution\-synchronization\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf distro\-sync [<package\-spec>...]\fP
+As necessary upgrades, downgrades or keeps selected installed packages to match
+the latest version available from any enabled repository. If no package is given, all installed packages are considered.
+.sp
+See also \fI\%Configuration Files Replacement Policy\fP\&.
+.UNINDENT
+.SS Downgrade Command
+.nf
+Command: \fBdowngrade\fP
+Aliases: \fBdg\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] downgrade <package\-spec>...\fP
+Downgrades the specified packages to the highest installable package of all known lower versions
+if possible. When version is given and is lower than version of installed package then it
+downgrades to target version.
+.UNINDENT
+.SS Group Command
+.nf
+Command: \fBgroup\fP
+Aliases: \fBgrp\fP
+Deprecated aliases: \fBgroups\fP, \fBgrouplist\fP, \fBgroupinstall\fP, \fBgroupupdate\fP, \fBgroupremove\fP, \fBgrouperase\fP, \fBgroupinfo\fP
+.fi
+.sp
+.sp
+Groups are virtual collections of packages. DNF keeps track of groups that the user selected ("marked") installed and can manipulate the comprising packages with simple commands.
+.INDENT 0.0
+.TP
+.B \fBdnf [options] group [summary] <group\-spec>\fP
+Display overview of how many groups are installed and available. With a
+spec, limit the output to the matching groups. \fBsummary\fP is the default
+groups subcommand.
+.TP
+.B \fBdnf [options] group info <group\-spec>\fP
+Display package lists of a group. Shows which packages are installed or
+available from a repository when \fB\-v\fP is used.
+.TP
+.B \fBdnf [options] group install [\-\-with\-optional] <group\-spec>...\fP
+Mark the specified group installed and install packages it contains. Also
+include \fIoptional\fP packages of the group if \fB\-\-with\-optional\fP is
+specified. All \fImandatory\fP and \fIDefault\fP packages will be installed whenever possible.
+Conditional packages are installed if they meet their requirement.
+If the group is already (partially) installed, the command installs the missing packages from the group.
+Depending on the value of obsoletes configuration option group installation takes obsoletes into account.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdnf [options] group list <group\-spec>...\fP
+List all matching groups, either among installed or available groups. If
+nothing is specified, list all known groups. \fB\-\-installed\fP and \fB\-\-available\fP options narrow down the requested list.
+Records are ordered by the \fIdisplay_order\fP tag defined in comps.xml file.
+Provides a list of all hidden groups by using option \fB\-\-hidden\fP\&.
+Provides group IDs when the \fB\-v\fP or \fB\-\-ids\fP options are used.
+.TP
+.B \fBdnf [options] group remove <group\-spec>...\fP
+Mark the group removed and remove those packages in the group from the system which do not belong to another installed group and were not installed explicitly by the user.
+.TP
+.B \fBdnf [options] group upgrade <group\-spec>...\fP
+Upgrades the packages from the group and upgrades the group itself. The latter comprises of installing packages that were added to the group by the distribution and removing packages that got removed from the group as far as they were not installed explicitly by the user.
+.UNINDENT
+.sp
+Groups can also be marked installed or removed without physically manipulating any packages:
+.INDENT 0.0
+.TP
+.B \fBdnf [options] group mark install <group\-spec>...\fP
+Mark the specified group installed. No packages will be installed by this command, but the group is then considered installed.
+.TP
+.B \fBdnf [options] group mark remove <group\-spec>...\fP
+Mark the specified group removed. No packages will be removed by this command.
+.UNINDENT
+.sp
+See also \fI\%Configuration Files Replacement Policy\fP\&.
+.SS Help Command
+.nf
+Command: \fBhelp\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf help [<command>]\fP
+Displays the help text for all commands. If given a command name then only
+displays help for that particular command.
+.UNINDENT
+.SS History Command
+.nf
+Command: \fBhistory\fP
+Aliases: \fBhist\fP
+.fi
+.sp
+.sp
+The history command allows the user to view what has happened in past
+transactions and act according to this information (assuming the
+\fBhistory_record\fP configuration option is set).
+.INDENT 0.0
+.TP
+.B \fBdnf history [list] [\-\-reverse] [<spec>...]\fP
+The default history action is listing information about given transactions
+in a table. Each \fB<spec>\fP can be either a \fB<transaction\-spec>\fP, which
+specifies a transaction directly, or a \fB<transaction\-spec>..<transaction\-spec>\fP,
+which specifies a range of transactions, or a \fB<package\-name\-spec>\fP,
+which specifies a transaction by a package which it manipulated. When no
+transaction is specified, list all known transactions.
+.INDENT 7.0
+.TP
+.B \fB\-\-reverse\fP
+The order of \fBhistory list\fP output is printed in reverse order.
+.UNINDENT
+.TP
+.B \fBdnf history info [<spec>...]\fP
+Describe the given transactions. The meaning of \fB<spec>\fP is the same as
+in the \fI\%History List Command\fP\&. When no
+transaction is specified, describe what happened during the latest
+transaction.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdnf history redo <transaction\-spec>|<package\-file\-spec>\fP
+Repeat the specified transaction. Uses the last transaction (with the highest ID)
+if more than one transaction for given <package\-file\-spec> is found. If it is not possible
+to redo some operations due to the current state of RPMDB, it will not redo the transaction.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdnf history replay [\-\-ignore\-installed] [\-\-ignore\-extras] [\-\-skip\-unavailable] <filename>\fP
+Replay a transaction stored in file \fB<filename>\fP by \fI\%History Store
+Command\fP\&. The replay will perform the exact
+same operations on the packages as in the original transaction and will
+return with an error if case of any differences in installed packages or
+their versions. See also the Transaction JSON Format specification of the
+file format.
+.INDENT 7.0
+.TP
+.B \fB\-\-ignore\-installed\fP
+Don\(aqt check for the installed packages being in the same state as those
+recorded in the transaction. E.g. in case there is an upgrade
+\fBfoo\-1.0\fP \-> \fBfoo\-2.0\fP stored in the transaction, but there is
+\fBfoo\-1.1\fP installed on the target system.
+.TP
+.B \fB\-\-ignore\-extras\fP
+Don\(aqt check for extra packages pulled into the transaction on the
+target system. E.g. the target system may not have some dependency,
+which was installed on the source system. The replay errors out on this
+by default, as the transaction would not be the same.
+.TP
+.B \fB\-\-skip\-unavailable\fP
+In case some packages stored in the transaction are not available on
+the target system, skip them instead of erroring out.
+.UNINDENT
+.TP
+.B \fBdnf history rollback <transaction\-spec>|<package\-file\-spec>\fP
+Undo all transactions performed after the specified transaction. Uses the last transaction
+(with the highest ID) if more than one transaction for given <package\-file\-spec> is found.
+If it is not possible to undo some transactions due to the current state of RPMDB, it will not undo
+any transaction.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdnf history store [\-\-output <output\-file>] <transaction\-spec>\fP
+Store a transaction specified by \fB<transaction\-spec>\fP\&. The transaction
+can later be replayed by the \fI\%History Replay Command\fP\&.
+.sp
+Warning: The stored transaction format is considered unstable and may
+change at any time. It will work if the same version of dnf is used to
+store and replay (or between versions as long as it stays the same).
+.sp
+\fB\-o <output\-file>, \-\-output=<output\-file>\fP
+Store the serialized transaction into \fB<output\-file\fP\&. Default is \fBtransaction.json\fP\&.
+.TP
+.B \fBdnf history undo <transaction\-spec>|<package\-file\-spec>\fP
+Perform the opposite operation to all operations performed in the specified transaction.
+Uses the last transaction (with the highest ID) if more than one transaction for given
+<package\-file\-spec> is found. If it is not possible to undo some operations due to
+the current state of RPMDB, it will not undo the transaction.
+.TP
+.B \fBdnf history userinstalled\fP
+Show all installonly packages, packages installed outside of DNF and packages not
+installed as dependency. I.e. it lists packages that will stay on the system when
+\fI\%Autoremove Command\fP or \fI\%Remove Command\fP along with
+\fIclean_requirements_on_remove\fP configuration option set to True is executed. Note the same
+results can be accomplished with \fBdnf repoquery \-\-userinstalled\fP, and the repoquery
+command is more powerful in formatting of the output.
+.UNINDENT
+.sp
+This command by default does not force a sync of expired metadata, except for
+the redo, rollback, and undo subcommands.
+See also \fI\%Metadata Synchronization\fP
+and \fI\%Configuration Files Replacement Policy\fP\&.
+.SS Info Command
+.nf
+Command: \fBinfo\fP
+Aliases: \fBif\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] info [<package\-file\-spec>...]\fP
+Lists description and summary information about installed and available packages.
+.UNINDENT
+.sp
+The info command limits the displayed packages the same way as the \fI\%list command\fP\&.
+.sp
+This command by default does not force a sync of expired metadata. See also \fI\%Metadata Synchronization\fP\&.
+.SS Install Command
+.nf
+Command: \fBinstall\fP
+Aliases: \fBin\fP
+Aliases for \fI\%explicit NEVRA matching\fP: \fBinstall\-n\fP, \fBinstall\-na\fP, \fBinstall\-nevra\fP
+Deprecated aliases: \fBlocalinstall\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] install <spec>...\fP
+Makes sure that the given packages and their dependencies are installed
+on the system. Each \fB<spec>\fP can be either a \fI\%<package\-spec>\fP,
+or a @\fI\%<module\-spec>\fP, or a @\fI\%<group\-spec>\fP\&.
+See \fI\%Install Examples\fP\&.
+If a given package or provide cannot be (and is not already) installed,
+the exit code will be non\-zero.
+If the \fB<spec>\fP matches both a @\fI\%<module\-spec>\fP and
+a @\fI\%<group\-spec>\fP, only the module is installed.
+.sp
+When \fI\%<package\-spec>\fP to specify the exact version
+of the package is given, DNF will install the desired version, no matter which
+version of the package is already installed. The former version of the package
+will be removed in the case of non\-installonly package.
+.sp
+On the other hand if \fI\%<package\-spec>\fP specifies only a name,
+DNF also takes into account packages obsoleting it when picking which package to install.
+This behaviour is specific to the install command.
+Note that this can lead to seemingly unexpected results if a package has multiple versions and
+some older version is being obsoleted. It creates a split in the upgrade\-path and both ways
+are considered correct, the resulting package is picked simply by lexicographical order.
+.sp
+There are also a few specific install commands \fBinstall\-n\fP, \fBinstall\-na\fP and
+\fBinstall\-nevra\fP that allow the specification of an exact argument in the NEVRA format.
+.sp
+See also \fI\%Configuration Files Replacement Policy\fP\&.
+.UNINDENT
+.SS Install Examples
+.INDENT 0.0
+.TP
+.B \fBdnf install tito\fP
+Install the \fBtito\fP package (tito is the package name).
+.TP
+.B \fBdnf install ~/Downloads/tito\-0.6.2\-1.fc22.noarch.rpm\fP
+Install a local rpm file tito\-0.6.2\-1.fc22.noarch.rpm from the ~/Downloads/
+directory.
+.TP
+.B \fBdnf install tito\-0.5.6\-1.fc22\fP
+Install the package with a specific version. If the package is already installed it
+will automatically try to downgrade or upgrade to the specific version.
+.TP
+.B \fBdnf \-\-best install tito\fP
+Install the latest available version of the package. If the package is already installed it
+will try to automatically upgrade to the latest version. If the latest version
+of the package cannot be installed, the installation will fail.
+.TP
+.B \fBdnf install vim\fP
+DNF will automatically recognize that vim is not a package name, but
+will look up and install a package that provides vim with all the required
+dependencies. Note: Package name match has precedence over package provides
+match.
+.TP
+.B \fBdnf install https://kojipkgs.fedoraproject.org//packages/tito/0.6.0/1.fc22/noarch/tito\-0.6.0\-1.fc22.noarch.rpm\fP
+Install a package directly from a URL.
+.TP
+.B \fBdnf install \(aq@docker\(aq\fP
+Install all default profiles of module \(aqdocker\(aq and their RPMs. Module streams get enabled accordingly.
+.TP
+.B \fBdnf install \(aq@Web Server\(aq\fP
+Install the \(aqWeb Server\(aq environmental group.
+.TP
+.B \fBdnf install /usr/bin/rpmsign\fP
+Install a package that provides the /usr/bin/rpmsign file.
+.TP
+.B \fBdnf \-y install tito \-\-setopt=install_weak_deps=False\fP
+Install the \fBtito\fP package (tito is the package name) without weak deps. Weak deps are not required for
+core functionality of the package, but they enhance the original package (like extended
+documentation, plugins, additional functions, etc.).
+.TP
+.B \fBdnf install \-\-advisory=FEDORA\-2018\-b7b99fe852 \e*\fP
+Install all packages that belong to the "FEDORA\-2018\-b7b99fe852" advisory.
+.UNINDENT
+.SS List Command
+.nf
+Command: \fBlist\fP
+Aliases: \fBls\fP
+.fi
+.sp
+.sp
+Prints lists of packages depending on the packages\(aq relation to the
+system. A package is \fBinstalled\fP if it is present in the RPMDB, and it is \fBavailable\fP
+if it is not installed but is present in a repository that DNF knows about.
+.sp
+The list command also limits the displayed packages according to specific criteria,
+e.g. to only those that update an installed package (respecting the repository
+priority). The exclude option in the configuration file can influence the
+result, but if the \-\fI\%\-disableexcludes\fP command line
+option is used, it ensures that all installed packages will be listed.
+.INDENT 0.0
+.TP
+.B \fBdnf [options] list [\-\-all] [<package\-file\-spec>...]\fP
+Lists all packages, present in the RPMDB, in a repository or both.
+.TP
+.B \fBdnf [options] list \-\-installed [<package\-file\-spec>...]\fP
+Lists installed packages.
+.TP
+.B \fBdnf [options] list \-\-available [<package\-file\-spec>...]\fP
+Lists available packages.
+.TP
+.B \fBdnf [options] list \-\-extras [<package\-file\-spec>...]\fP
+Lists extras, that is packages installed on the system that are not
+available in any known repository.
+.TP
+.B \fBdnf [options] list \-\-obsoletes [<package\-file\-spec>...]\fP
+List packages installed on the system that are obsoleted by packages in
+any known repository.
+.TP
+.B \fBdnf [options] list \-\-recent [<package\-file\-spec>...]\fP
+List packages recently added into the repositories.
+.TP
+.B \fBdnf [options] list \-\-upgrades [<package\-file\-spec>...]\fP
+List upgrades available for the installed packages.
+.TP
+.B \fBdnf [options] list \-\-autoremove\fP
+List packages which will be removed by the \fBdnf autoremove\fP command.
+.UNINDENT
+.sp
+This command by default does not force a sync of expired metadata. See also \fI\%Metadata Synchronization\fP\&.
+.SS Makecache Command
+.nf
+Command: \fBmakecache\fP
+Aliases: \fBmc\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] makecache\fP
+Downloads and caches metadata for enabled repositories. Tries to
+avoid downloading whenever possible (e.g. when the local metadata hasn\(aqt
+expired yet or when the metadata timestamp hasn\(aqt changed).
+.TP
+.B \fBdnf [options] makecache \-\-timer\fP
+Like plain \fBmakecache\fP, but instructs DNF to be more resource\-aware,
+meaning it will not do anything if running on battery power and will terminate
+immediately if it\(aqs too soon after the last successful \fBmakecache\fP run
+(see \fBdnf.conf(5)\fP, metadata_timer_sync).
+.UNINDENT
+.SS Mark Command
+.nf
+Command: \fBmark\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf mark install <package\-spec>...\fP
+Marks the specified packages as installed by user. This can be useful if any package was installed as a dependency and is desired to stay on the system when \fI\%Autoremove Command\fP or \fI\%Remove Command\fP along with \fIclean_requirements_on_remove\fP configuration option set to \fBTrue\fP is executed.
+.TP
+.B \fBdnf mark remove <package\-spec>...\fP
+Unmarks the specified packages as installed by user. Whenever you as a user don\(aqt need a specific package you can mark it for removal. The package stays installed on the system but will be removed when \fI\%Autoremove Command\fP or \fI\%Remove Command\fP along with \fIclean_requirements_on_remove\fP configuration option set to \fBTrue\fP is executed. You should use this operation instead of \fI\%Remove Command\fP if you\(aqre not sure whether the package is a requirement of other user installed packages on the system.
+.TP
+.B \fBdnf mark group <package\-spec>...\fP
+Marks the specified packages as installed by group. This can be useful if any package was
+installed as a dependency or a user and is desired to be protected and handled as a group
+member like during group remove.
+.UNINDENT
+.SS Module Command
+.nf
+Command: \fBmodule\fP
+.fi
+.sp
+.sp
+Modularity overview is available at man page dnf.modularity(7)\&.
+Module subcommands take \fI\%<module\-spec>\fP\&... arguments that specify modules or profiles.
+.INDENT 0.0
+.TP
+.B \fBdnf [options] module install <module\-spec>...\fP
+Install module profiles, including their packages.
+In case no profile was provided, all default profiles get installed.
+Module streams get enabled accordingly.
+.sp
+This command cannot be used for switching module streams. Use the
+\fI\%dnf module switch\-to\fP command for that.
+.TP
+.B \fBdnf [options] module update <module\-spec>...\fP
+Update packages associated with an active module stream, optionally restricted to a profile.
+If the \fIprofile_name\fP is provided, only the packages referenced by that profile will be updated.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdnf [options] module switch\-to <module\-spec>...\fP
+Switch to or enable a module stream, change versions of installed packages to versions provided
+by the new stream, and remove packages from the old stream that are no longer available. It also
+updates installed profiles if they are available for the new stream. When a profile was
+provided, it installs that profile and does not update any already installed profiles.
+.sp
+This command can be used as a stronger version of the
+\fI\%dnf module enable\fP command, which not only enables modules,
+but also does a \fIdistrosync\fP to all modular packages in the enabled modules.
+.sp
+It can also be used as a stronger version of the
+\fI\%dnf module install\fP command, but it requires to specify
+profiles that are supposed to be installed, because \fIswitch\-to\fP command does not use \fIdefault
+profiles\fP\&. The \fIswitch\-to\fP command doesn\(aqt only install profiles, it also makes a \fIdistrosync\fP
+to all modular packages in the installed module.
+.TP
+.B \fBdnf [options] module remove <module\-spec>...\fP
+Remove installed module profiles, including packages that were installed with the
+\fI\%dnf module install\fP command. Will not remove packages
+required by other installed module profiles or by other user\-installed packages.
+In case no profile was provided, all installed profiles get removed.
+.TP
+.B \fBdnf [options] module remove \-\-all <module\-spec>...\fP
+Remove installed module profiles, including packages that were installed with the
+\fI\%dnf module install\fP command.
+With \-\-all option it additionally removes all packages whose names are provided by specified
+modules. Packages required by other installed module profiles and packages whose names are also
+provided by any other module are not removed.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdnf [options] module enable <module\-spec>...\fP
+Enable a module stream and make the stream RPMs available in the package set.
+.sp
+Modular dependencies are resolved, dependencies checked and also recursively enabled. In case
+of modular dependency issue the operation will be rejected. To perform the action anyway please use
+\-\fI\%\-skip\-broken\fP option.
+.sp
+This command cannot be used for switching module streams. Use the
+\fI\%dnf module switch\-to\fP command for that.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdnf [options] module disable <module\-name>...\fP
+Disable a module. All related module streams will become unavailable.
+Consequently, all installed profiles will be removed and the module RPMs
+will become unavailable in the package set. In case of modular
+dependency issue the operation will be rejected. To perform the action anyway please use \-\fI\%\-skip\-broken\fP option.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdnf [options] module reset <module\-name>...\fP
+Reset module state so it\(aqs no longer enabled or disabled.
+Consequently, all installed profiles will be removed and
+only RPMs from the default stream will be available in the package set.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdnf [options] module provides <package\-name\-spec>...\fP
+Lists all modular packages matching \fB<package\-name\-spec>\fP from all modules (including disabled), along with the modules and streams they belong to.
+.TP
+.B \fBdnf [options] module list [\-\-all] [module_name...]\fP
+Lists all module streams, their profiles and states (enabled, disabled, default).
+.TP
+.B \fBdnf [options] module list \-\-enabled [module_name...]\fP
+Lists module streams that are enabled.
+.TP
+.B \fBdnf [options] module list \-\-disabled [module_name...]\fP
+Lists module streams that are disabled.
+.TP
+.B \fBdnf [options] module list \-\-installed [module_name...]\fP
+List module streams with installed profiles.
+.TP
+.B \fBdnf [options] module info <module\-spec>...\fP
+Print detailed information about given module stream.
+.TP
+.B \fBdnf [options] module info \-\-profile <module\-spec>...\fP
+Print detailed information about given module profiles.
+.TP
+.B \fBdnf [options] module repoquery <module\-spec>...\fP
+List all available packages belonging to selected modules.
+.TP
+.B \fBdnf [options] module repoquery \-\-available <module\-spec>...\fP
+List all available packages belonging to selected modules.
+.TP
+.B \fBdnf [options] module repoquery \-\-installed <module\-spec>...\fP
+List all installed packages with same name like packages belonging to selected modules.
+.UNINDENT
+.SS Provides Command
+.nf
+Command: \fBprovides\fP
+Aliases: \fBprov\fP, \fBwhatprovides\fP, \fBwp\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] provides <provide\-spec>\fP
+Finds the packages providing the given \fB<provide\-spec>\fP\&. This is useful
+when one knows a filename and wants to find what package (installed or not)
+provides this file.
+The \fB<provide\-spec>\fP is gradually looked for at following locations:
+.INDENT 7.0
+.IP 1. 3
+The \fB<provide\-spec>\fP is matched with all file provides of any available package:
+.INDENT 3.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+$ dnf provides /usr/bin/gzip
+gzip\-1.9\-9.fc29.x86_64 : The GNU data compression program
+Matched from:
+Filename    : /usr/bin/gzip
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.IP 2. 3
+Then all provides of all available packages are searched:
+.INDENT 3.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+$ dnf provides "gzip(x86\-64)"
+gzip\-1.9\-9.fc29.x86_64 : The GNU data compression program
+Matched from:
+Provide     : gzip(x86\-64) = 1.9\-9.fc29
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.IP 3. 3
+DNF assumes that the \fB<provide\-spec>\fP is a system command, prepends it with \fB/usr/bin/\fP, \fB/usr/sbin/\fP prefixes (one at a time) and does the file provides search again. For legacy reasons (packages that didn\(aqt do UsrMove) also \fB/bin\fP and \fB/sbin\fP prefixes are being searched:
+.INDENT 3.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+$ dnf provides zless
+gzip\-1.9\-9.fc29.x86_64 : The GNU data compression program
+Matched from:
+Filename    : /usr/bin/zless
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.IP 4. 3
+If this last step also fails, DNF returns "Error: No Matches found".
+.UNINDENT
+.sp
+This command by default does not force a sync of expired metadata. See also \fI\%Metadata Synchronization\fP\&.
+.UNINDENT
+.SS Reinstall Command
+.nf
+Command: \fBreinstall\fP
+Aliases: \fBrei\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] reinstall <package\-spec>...\fP
+Installs the specified packages, fails if some of the packages are either
+not installed or not available (i.e. there is no repository where to
+download the same RPM).
+.UNINDENT
+.SS Remove Command
+.nf
+Command: \fBremove\fP
+Aliases: \fBrm\fP
+Aliases for \fI\%explicit NEVRA matching\fP: \fBremove\-n\fP, \fBremove\-na\fP, \fBremove\-nevra\fP
+Deprecated aliases: \fBerase\fP, \fBerase\-n\fP, \fBerase\-na\fP, \fBerase\-nevra\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] remove <package\-spec>...\fP
+Removes the specified packages from the system along with any packages depending on the packages being removed. Each \fB<spec>\fP can be either a \fB<package\-spec>\fP, which specifies a package directly, or a \fB@<group\-spec>\fP, which specifies an (environment) group which contains it. If \fBclean_requirements_on_remove\fP is enabled (the default), also removes any dependencies that are no longer needed.
+.TP
+.B \fBdnf [options] remove \-\-duplicates\fP
+Removes older versions of duplicate packages. To ensure the integrity of the system it
+reinstalls the newest package. In some cases the command cannot resolve conflicts. In such cases
+the \fI\%dnf shell\fP command with \fBremove \-\-duplicates\fP and \fBupgrade\fP
+dnf\-shell sub\-commands could help.
+.TP
+.B \fBdnf [options] remove \-\-oldinstallonly\fP
+Removes old installonly packages, keeping only latest versions and version of running kernel.
+.sp
+There are also a few specific remove commands \fBremove\-n\fP, \fBremove\-na\fP and \fBremove\-nevra\fP
+that allow the specification of an exact argument in the NEVRA format.
+.UNINDENT
+.SS Remove Examples
+.INDENT 0.0
+.TP
+.B \fBdnf remove acpi tito\fP
+Remove the \fBacpi\fP and \fBtito\fP packages.
+.TP
+.B \fBdnf remove $(dnf repoquery \-\-extras \-\-exclude=tito,acpi)\fP
+Remove packages not present in any repository, but don\(aqt remove the \fBtito\fP
+and \fBacpi\fP packages (they still might be removed if they depend on some of the removed packages).
+.UNINDENT
+.sp
+Remove older versions of duplicated packages (an equivalent of yum\(aqs \fIpackage\-cleanup \-\-cleandups\fP):
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf remove \-\-duplicates
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS Repoinfo Command
+.nf
+Command: \fBrepoinfo\fP
+.fi
+.sp
+.INDENT 0.0
+.INDENT 3.5
+An alias for the \fI\%repolist\fP command
+that provides more detailed information like \fBdnf repolist \-v\fP\&.
+.UNINDENT
+.UNINDENT
+.SS Repolist Command
+.nf
+Command: \fBrepolist\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] repolist [\-\-enabled|\-\-disabled|\-\-all]\fP
+Depending on the exact command lists enabled, disabled or all known
+repositories. Lists all enabled repositories by default. Provides more
+detailed information when \fB\-v\fP option is used.
+.UNINDENT
+.sp
+This command by default does not force a sync of expired metadata. See also \fI\%Metadata Synchronization\fP\&.
+.SS Repoquery Command
+.nf
+Command: \fBrepoquery\fP
+Aliases: \fBrq\fP
+Aliases for \fI\%explicit NEVRA matching\fP: \fBrepoquery\-n\fP, \fBrepoquery\-na\fP, \fBrepoquery\-nevra\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] repoquery [<select\-options>] [<query\-options>] [<package\-file\-spec>]\fP
+Searches available DNF repositories for selected packages and displays the requested information about them. It
+is an equivalent of \fBrpm \-q\fP for remote repositories.
+.TP
+.B \fBdnf [options] repoquery \-\-groupmember <package\-spec>...\fP
+List groups that contain <package\-spec>.
+.TP
+.B \fBdnf [options] repoquery \-\-querytags\fP
+Provides the list of tags recognized by the \-\fI\%\-queryformat\fP repoquery option.
+.sp
+There are also a few specific repoquery commands \fBrepoquery\-n\fP, \fBrepoquery\-na\fP and \fBrepoquery\-nevra\fP
+that allow the specification of an exact argument in the NEVRA format (does not affect arguments of options like \-\-whatprovides <arg>, ...).
+.UNINDENT
+.SS Select Options
+.sp
+Together with \fB<package\-file\-spec>\fP, control what packages are displayed in the output. If \fB<package\-file\-spec>\fP is given, limits the resulting set of
+packages to those matching the specification. All packages are considered if no \fB<package\-file\-spec>\fP is specified.
+.INDENT 0.0
+.TP
+.B \fB<package\-file\-spec>\fP
+Package specification in the NEVRA format (name[\-[epoch:]version[\-release]][.arch]), a package provide or a file provide. See \fI\%Specifying Packages\fP\&.
+.TP
+.B \fB\-a\fP, \fB\-\-all\fP
+Query all packages (for rpmquery compatibility, also a shorthand for repoquery \(aq*\(aq or repoquery
+without arguments).
+.TP
+.B \fB\-\-arch <arch>[,<arch>...], \-\-archlist <arch>[,<arch>...]\fP
+Limit the resulting set only to packages of selected architectures (default is all
+architectures). In some cases the result is affected by the basearch of the running system, therefore
+to run repoquery for an arch incompatible with your system use the \fB\-\-forcearch=<arch>\fP
+option to change the basearch.
+.TP
+.B \fB\-\-duplicates\fP
+Limit the resulting set to installed duplicate packages (i.e. more package versions
+for the same name and architecture). Installonly packages are excluded from this set.
+.TP
+.B \fB\-\-unneeded\fP
+Limit the resulting set to leaves packages that were installed as dependencies so they are no longer needed. This
+switch lists packages that are going to be removed after executing the \fBdnf autoremove\fP command.
+.TP
+.B \fB\-\-available\fP
+Limit the resulting set to available packages only (set by default).
+.TP
+.B \fB\-\-disable\-modular\-filtering\fP
+Disables filtering of modular packages, so that packages of inactive module streams are included in the result.
+.TP
+.B \fB\-\-extras\fP
+Limit the resulting set to packages that are not present in any of the available repositories.
+.TP
+.B \fB\-f <file>\fP, \fB\-\-file <file>\fP
+Limit the resulting set only to the package that owns \fB<file>\fP\&.
+.TP
+.B \fB\-\-installed\fP
+Limit the resulting set to installed packages only. The exclude option in the configuration file
+might influence the result, but if the command line option  \-\fI\%\-disableexcludes\fP is used, it ensures that all installed packages will be listed.
+.TP
+.B \fB\-\-installonly\fP
+Limit the resulting set to installed installonly packages.
+.TP
+.B \fB\-\-latest\-limit <number>\fP
+Limit the resulting set to <number> of latest packages for every package name and architecture.
+If <number> is negative, skip <number> of latest packages. For a negative <number> use the
+\fB\-\-latest\-limit=<number>\fP syntax.
+.TP
+.B \fB\-\-recent\fP
+Limit the resulting set to packages that were recently edited.
+.TP
+.B \fB\-\-repo <repoid>\fP
+Limit the resulting set only to packages from a repository identified by \fB<repoid>\fP\&.
+Can be used multiple times with accumulative effect.
+.TP
+.B \fB\-\-unsatisfied\fP
+Report unsatisfied dependencies among installed packages (i.e. missing requires and
+existing conflicts).
+.TP
+.B \fB\-\-upgrades\fP
+Limit the resulting set to packages that provide an upgrade for some already installed package.
+.TP
+.B \fB\-\-userinstalled\fP
+Limit the resulting set to packages installed by the user. The exclude option
+in the configuration file might influence the result, but if the command line option  \-\fI\%\-disableexcludes\fP is used, it ensures that all installed packages will be listed.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-whatdepends <capability>[,<capability>...]\fP
+Limit the resulting set only to packages that require, enhance, recommend, suggest or
+supplement any of \fB<capabilities>\fP\&.
+.TP
+.B \fB\-\-whatconflicts <capability>[,<capability>...]\fP
+Limit the resulting set only to packages that conflict with any of \fB<capabilities>\fP\&.
+.TP
+.B \fB\-\-whatenhances <capability>[,<capability>...]\fP
+Limit the resulting set only to packages that enhance any of \fB<capabilities>\fP\&. Use \-\fI\%\-whatdepends\fP if you want to list all depending packages.
+.TP
+.B \fB\-\-whatobsoletes <capability>[,<capability>...]\fP
+Limit the resulting set only to packages that obsolete any of \fB<capabilities>\fP\&.
+.TP
+.B \fB\-\-whatprovides <capability>[,<capability>...]\fP
+Limit the resulting set only to packages that provide any of \fB<capabilities>\fP\&.
+.TP
+.B \fB\-\-whatrecommends <capability>[,<capability>...]\fP
+Limit the resulting set only to packages that recommend any of \fB<capabilities>\fP\&. Use \-\fI\%\-whatdepends\fP if you want to list all depending packages.
+.TP
+.B \fB\-\-whatrequires <capability>[,<capability>...]\fP
+Limit the resulting set only to packages that require any of \fB<capabilities>\fP\&. Use \-\fI\%\-whatdepends\fP if you want to list all depending packages.
+.TP
+.B \fB\-\-whatsuggests <capability>[,<capability>...]\fP
+Limit the resulting set only to packages that suggest any of \fB<capabilities>\fP\&. Use \-\fI\%\-whatdepends\fP if you want to list all depending packages.
+.TP
+.B \fB\-\-whatsupplements <capability>[,<capability>...]\fP
+Limit the resulting set only to packages that supplement any of \fB<capabilities>\fP\&. Use \-\fI\%\-whatdepends\fP if you want to list all depending packages.
+.TP
+.B \fB\-\-alldeps\fP
+This option is stackable with \fB\-\-whatrequires\fP or \-\fI\%\-whatdepends\fP only. Additionally it adds all packages requiring
+the package features to the result set (used as default).
+.TP
+.B \fB\-\-exactdeps\fP
+This option is stackable with \fB\-\-whatrequires\fP or \-\fI\%\-whatdepends\fP only. Limit the resulting set only to packages
+that require \fB<capability>\fP specified by \-\-whatrequires.
+.TP
+.B \fB\-\-srpm\fP
+Operate on the corresponding source RPM.
+.UNINDENT
+.SS Query Options
+.sp
+Set what information is displayed about each package.
+.sp
+The following are mutually exclusive, i.e. at most one can be specified. If no query option is given, matching packages
+are displayed in the standard NEVRA notation.
+.INDENT 0.0
+.TP
+.B \fB\-i, \-\-info\fP
+Show detailed information about the package.
+.TP
+.B \fB\-l, \-\-list\fP
+Show the list of files in the package.
+.TP
+.B \fB\-s, \-\-source\fP
+Show the package source RPM name.
+.TP
+.B \fB\-\-changelogs\fP
+Print the package changelogs.
+.TP
+.B \fB\-\-conflicts\fP
+Display capabilities that the package conflicts with. Same as \fB\-\-qf "%{conflicts}\fP\&.
+.TP
+.B \fB\-\-depends\fP
+Display capabilities that the package depends on, enhances, recommends, suggests or
+supplements.
+.TP
+.B \fB\-\-enhances\fP
+Display capabilities enhanced by the package. Same as \fB\-\-qf "%{enhances}""\fP\&.
+.TP
+.B \fB\-\-location\fP
+Show a location where the package could be downloaded from.
+.TP
+.B \fB\-\-obsoletes\fP
+Display capabilities that the package obsoletes. Same as \fB\-\-qf "%{obsoletes}"\fP\&.
+.TP
+.B \fB\-\-provides\fP
+Display capabilities provided by the package. Same as \fB\-\-qf "%{provides}"\fP\&.
+.TP
+.B \fB\-\-recommends\fP
+Display capabilities recommended by the package. Same as \fB\-\-qf "%{recommends}"\fP\&.
+.TP
+.B \fB\-\-requires\fP
+Display capabilities that the package depends on. Same as \fB\-\-qf "%{requires}"\fP\&.
+.TP
+.B \fB\-\-requires\-pre\fP
+Display capabilities that the package depends on for running a \fB%pre\fP script.
+Same as \fB\-\-qf "%{requires\-pre}"\fP\&.
+.TP
+.B \fB\-\-suggests\fP
+Display capabilities suggested by the package. Same as \fB\-\-qf "%{suggests}"\fP\&.
+.TP
+.B \fB\-\-supplements\fP
+Display capabilities supplemented by the package. Same as \fB\-\-qf "%{supplements}"\fP\&.
+.TP
+.B \fB\-\-tree\fP
+Display a recursive tree of packages with capabilities specified by one of the following supplementary options:
+\fB\-\-whatrequires\fP, \fB\-\-requires\fP, \fB\-\-conflicts\fP, \fB\-\-enhances\fP, \fB\-\-suggests\fP, \fB\-\-provides\fP,
+\fB\-\-supplements\fP, \fB\-\-recommends\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-deplist\fP
+Produce a list of all direct dependencies and what packages provide those
+dependencies for the given packages. The result only shows the newest
+providers (which can be changed by using \-\-verbose).
+.TP
+.B \fB\-\-nvr\fP
+Show found packages in the name\-version\-release format. Same as
+\fB\-\-qf "%{name}\-%{version}\-%{release}"\fP\&.
+.TP
+.B \fB\-\-nevra\fP
+Show found packages in the name\-epoch:version\-release.architecture format. Same as
+\fB\-\-qf "%{name}\-%{epoch}:%{version}\-%{release}.%{arch}"\fP (default).
+.TP
+.B \fB\-\-envra\fP
+Show found packages in the epoch:name\-version\-release.architecture format. Same as
+\fB\-\-qf "%{epoch}:%{name}\-%{version}\-%{release}.%{arch}"\fP
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fB\-\-qf <format>\fP, \fB\-\-queryformat <format>\fP
+Custom display format. \fB<format>\fP is the string to output for each matched package. Every occurrence of
+\fB%{<tag>}\fP within is replaced by the corresponding attribute of the package. The list of recognized tags can be displayed
+by running \fBdnf repoquery \-\-querytags\fP\&.
+.TP
+.B \fB\-\-recursive\fP
+Query packages recursively. Has to be used with \fB\-\-whatrequires <REQ>\fP
+(optionally with \fB\-\-alldeps\fP, but not with \fB\-\-exactdeps\fP) or with
+\fB\-\-requires <REQ> \-\-resolve\fP\&.
+.TP
+.B \fB\-\-resolve\fP
+resolve capabilities to originating package(s).
+.UNINDENT
+.SS Examples
+.sp
+Display NEVRAs of all available packages matching \fBlight*\fP:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery \(aqlight*\(aq
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Display NEVRAs of all available packages matching name \fBlight*\fP and architecture \fBnoarch\fP (accepts only arguments in the "<name>.<arch>" format):
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery\-na \(aqlight*.noarch\(aq
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Display requires of all lighttpd packages:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery \-\-requires lighttpd
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Display packages providing the requires of python packages:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery \-\-requires python \-\-resolve
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Display source rpm of ligttpd package:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery \-\-source lighttpd
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Display package name that owns the given file:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery \-\-file /etc/lighttpd/lighttpd.conf
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Display name, architecture and the containing repository of all lighttpd packages:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery \-\-queryformat \(aq%{name}.%{arch} : %{reponame}\(aq lighttpd
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Display all available packages providing "webserver":
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery \-\-whatprovides webserver
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Display all available packages providing "webserver" but only for "i686" architecture:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery \-\-whatprovides webserver \-\-arch i686
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Display duplicate packages:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery \-\-duplicates
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Display source packages that require a <provide> for a build:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf repoquery \-\-disablerepo="*" \-\-enablerepo="*\-source" \-\-arch=src \-\-whatrequires <provide>
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS Repository\-Packages Command
+.nf
+Command: \fBrepository\-packages\fP
+Deprecated aliases: \fBrepo\-pkgs\fP, \fBrepo\-packages\fP, \fBrepository\-pkgs\fP
+.fi
+.sp
+.sp
+The repository\-packages command allows the user to run commands on top of all packages in the repository named \fB<repoid>\fP\&. However, any dependency resolution takes into account packages from all enabled repositories. The \fB<package\-file\-spec>\fP and \fB<package\-spec>\fP specifications further limit the candidates to only those packages matching at least one of them.
+.sp
+The \fBinfo\fP subcommand lists description and summary information about packages depending on the packages\(aq relation to the repository. The \fBlist\fP subcommand just prints lists of those packages.
+.INDENT 0.0
+.TP
+.B \fBdnf [options] repository\-packages <repoid> check\-update [<package\-file\-spec>...]\fP
+Non\-interactively checks if updates of the specified packages in the repository are available. DNF exit code will be 100 when there are updates available and a list of the updates will be printed.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> info [\-\-all] [<package\-file\-spec>...]\fP
+List all related packages.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> info \-\-installed [<package\-file\-spec>...]\fP
+List packages installed from the repository.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> info \-\-available [<package\-file\-spec>...]\fP
+List packages available in the repository but not currently installed on the system.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> info \-\-extras [<package\-file\-specs>...]\fP
+List packages installed from the repository that are not available in any repository.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> info \-\-obsoletes [<package\-file\-spec>...]\fP
+List packages in the repository that obsolete packages installed on the system.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> info \-\-recent [<package\-file\-spec>...]\fP
+List packages recently added into the repository.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> info \-\-upgrades [<package\-file\-spec>...]\fP
+List packages in the repository that upgrade packages installed on the system.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> install [<package\-spec>...]\fP
+Install packages matching \fB<package\-spec>\fP from the repository. If \fB<package\-spec>\fP isn\(aqt specified at all, install all packages from the repository.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> list [\-\-all] [<package\-file\-spec>...]\fP
+List all related packages.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> list \-\-installed [<package\-file\-spec>...]\fP
+List packages installed from the repository.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> list \-\-available [<package\-file\-spec>...]\fP
+List packages available in the repository but not currently installed on the system.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> list \-\-extras [<package\-file\-spec>...]\fP
+List packages installed from the repository that are not available in any repository.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> list \-\-obsoletes [<package\-file\-spec>...]\fP
+List packages in the repository that obsolete packages installed on the system.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> list \-\-recent [<package\-file\-spec>...]\fP
+List packages recently added into the repository.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> list \-\-upgrades [<package\-file\-spec>...]\fP
+List packages in the repository that upgrade packages installed on the system.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> move\-to [<package\-spec>...]\fP
+Reinstall all those packages that are available in the repository.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> reinstall [<package\-spec>...]\fP
+Run the \fBreinstall\-old\fP subcommand. If it fails, run the \fBmove\-to\fP subcommand.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> reinstall\-old [<package\-spec>...]\fP
+Reinstall all those packages that were installed from the repository and simultaneously are available in the repository.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> remove [<package\-spec>...]\fP
+Remove all packages installed from the repository along with any packages depending on the packages being removed. If \fBclean_requirements_on_remove\fP is enabled (the default) also removes any dependencies that are no longer needed.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> remove\-or\-distro\-sync [<package\-spec>...]\fP
+Select all packages installed from the repository. Upgrade, downgrade or keep those of them that are available in another repository to match the latest version available there and remove the others along with any packages depending on the packages being removed. If \fBclean_requirements_on_remove\fP is enabled (the default) also removes any dependencies that are no longer needed.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> remove\-or\-reinstall [<package\-spec>...]\fP
+Select all packages installed from the repository. Reinstall those of them that are available in another repository and remove the others along with any packages depending on the packages being removed. If \fBclean_requirements_on_remove\fP is enabled (the default) also removes any dependencies that are no longer needed.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> upgrade [<package\-spec>...]\fP
+Update all packages to the highest resolvable version available in the repository.
+When versions are specified in the \fB<package\-spec>\fP, update to these versions.
+.TP
+.B \fBdnf [options] repository\-packages <repoid> upgrade\-to [<package\-specs>...]\fP
+A deprecated alias for the upgrade subcommand.
+.UNINDENT
+.SS Search Command
+.nf
+Command: \fBsearch\fP
+Aliases: \fBse\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] search [\-\-all] <keywords>...\fP
+Search package metadata for keywords. Keywords are matched as case\-insensitive substrings, globbing is supported.
+By default lists packages that match all requested keys (AND operation). Keys are searched in package names and summaries.
+If the "\-\-all" option is used, lists packages that match at least one of the keys (an OR operation).
+In addition the keys are searched in the package descriptions and URLs.
+The result is sorted from the most relevant results to the least.
+.UNINDENT
+.sp
+This command by default does not force a sync of expired metadata. See also \fI\%Metadata Synchronization\fP\&.
+.SS Shell Command
+.nf
+Command: \fBshell\fP
+Aliases: \fBsh\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] shell [filename]\fP
+Open an interactive shell for conducting multiple commands during a single execution of DNF. These commands can be issued manually
+or passed to DNF from a file. The commands are much the same as the normal DNF command line options. There are a few additional
+commands documented below.
+.INDENT 7.0
+.TP
+.B \fBconfig [conf\-option] [value]\fP
+.INDENT 7.0
+.IP \(bu 2
+Set a configuration option to a requested value. If no value is given it prints the current value.
+.UNINDENT
+.TP
+.B \fBrepo [list|enable|disable] [repo\-id]\fP
+.INDENT 7.0
+.IP \(bu 2
+list: list repositories and their status
+.IP \(bu 2
+enable: enable repository
+.IP \(bu 2
+disable: disable repository
+.UNINDENT
+.TP
+.B \fBtransaction [list|reset|solve|run]\fP
+.INDENT 7.0
+.IP \(bu 2
+list: resolve and list the content of the transaction
+.IP \(bu 2
+reset: reset the transaction
+.IP \(bu 2
+run: resolve and run the transaction
+.UNINDENT
+.UNINDENT
+.sp
+Note that all local packages must be used in the first shell transaction subcommand (e.g.
+\fIinstall /tmp/nodejs\-1\-1.x86_64.rpm /tmp/acpi\-1\-1.noarch.rpm\fP) otherwise an error will occur.
+Any \fIdisable\fP, \fIenable\fP, and \fIreset\fP module operations (e.g. \fImodule enable nodejs\fP) must also
+be performed before any other shell transaction subcommand is used.
+.UNINDENT
+.SS Swap Command
+.nf
+Command: \fBswap\fP
+.fi
+.sp
+.sp
+\fBdnf [options] swap <remove\-spec> <install\-spec>\fP
+.INDENT 0.0
+.INDENT 3.5
+Remove spec and install spec in one transaction. Each \fB<spec>\fP can be either a
+\fI\%<package\-spec>\fP, which specifies a package directly, or a
+\fB@<group\-spec>\fP, which specifies an (environment) group which contains it. Automatic
+conflict solving is provided in DNF by the \-\-allowerasing option that provides the functionality of the swap
+command automatically.
+.UNINDENT
+.UNINDENT
+.SS Updateinfo Command
+.nf
+Command: \fBupdateinfo\fP
+Aliases: \fBupif\fP
+Deprecated aliases: \fBlist\-updateinfo\fP, \fBlist\-security\fP, \fBlist\-sec\fP, \fBinfo\-updateinfo\fP, \fBinfo\-security\fP, \fBinfo\-sec\fP, \fBsummary\-updateinfo\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] updateinfo [\-\-summary|\-\-list|\-\-info] [<availability>] [<spec>...]\fP
+Display information about update advisories.
+.sp
+Depending on the output type, DNF displays just counts of advisory types
+(omitted or \fB\-\-summary\fP), list of advisories (\fB\-\-list\fP) or detailed
+information (\fB\-\-info\fP). The \fB\-v\fP option extends the output. When
+used with \fB\-\-info\fP, the information is even more detailed. When used
+with \fB\-\-list\fP, an additional column with date of the last advisory update
+is added.
+.sp
+\fB<availability>\fP specifies whether advisories about newer versions of
+installed packages (omitted or \fB\-\-available\fP), advisories about equal and
+older versions of installed packages (\fB\-\-installed\fP), advisories about
+newer versions of those installed packages for which a newer version is
+available (\fB\-\-updates\fP) or advisories about any versions of installed
+packages (\fB\-\-all\fP) are taken into account. Most of the time, \fB\-\-available\fP
+and \fB\-\-updates\fP displays the same output. The outputs differ only in the
+cases when an advisory refers to a newer version but there is no enabled
+repository which contains any newer version.
+.sp
+Note, that \fB\-\-available\fP takes only the latest installed versions of
+packages into account. In case of the kernel packages (when multiple
+version could be installed simultaneously) also packages of the currently
+running version of kernel are added.
+.sp
+To print only advisories referencing a CVE or a bugzilla use \fB\-\-with\-cve\fP or
+\fB\-\-with\-bz\fP options. When these switches are used also the output
+of the \fB\-\-list\fP is altered \- the ID of the CVE or the bugzilla is printed
+instead of the one of the advisory.
+.sp
+If given and if neither ID, type (\fBbugfix\fP, \fBenhancement\fP,
+\fBsecurity\fP/\fBsec\fP) nor a package name of an advisory matches
+\fB<spec>\fP, the advisory is not taken into account. The matching is
+case\-sensitive and in the case of advisory IDs and package names, globbing
+is supported.
+.sp
+Output of the \fB\-\-summary\fP option is affected by the autocheck_running_kernel configuration option.
+.UNINDENT
+.SS Upgrade Command
+.nf
+Command: \fBupgrade\fP
+Aliases: \fBup\fP
+Deprecated aliases: \fBupdate\fP, \fBupgrade\-to\fP, \fBupdate\-to\fP, \fBlocalupdate\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] upgrade\fP
+Updates each package to the latest version that is both available and
+resolvable.
+.TP
+.B \fBdnf [options] upgrade <package\-spec>...\fP
+Updates each specified package to the latest available version. Updates
+dependencies as necessary. When versions are specified in the
+\fB<package\-spec>\fP, update to these versions.
+.TP
+.B \fBdnf [options] upgrade @<spec>...\fP
+Alias for the \fIdnf module update\fP command.
+.UNINDENT
+.sp
+If the main \fBobsoletes\fP configure option is true or the \fB\-\-obsoletes\fP flag
+is present, dnf will include package obsoletes in its calculations.
+For more information see obsoletes\&.
+.sp
+See also \fI\%Configuration Files Replacement Policy\fP\&.
+.SS Upgrade\-Minimal Command
+.nf
+Command: \fBupgrade\-minimal\fP
+Aliases: \fBup\-min\fP
+Deprecated aliases: \fBupdate\-minimal\fP
+.fi
+.sp
+.INDENT 0.0
+.TP
+.B \fBdnf [options] upgrade\-minimal\fP
+Updates each package to the latest available version that provides a bugfix, enhancement
+or a fix for a security issue (security).
+.TP
+.B \fBdnf [options] upgrade\-minimal <package\-spec>...\fP
+Updates each specified package to the latest available version that provides
+a bugfix, enhancement or a fix for security issue (security). Updates
+dependencies as necessary.
+.UNINDENT
+.SH SPECIFYING PACKAGES
+.sp
+Many commands take a \fB<package\-spec>\fP parameter that selects a package for
+the operation. The \fB<package\-spec>\fP argument is matched against package
+NEVRAs, provides and file provides.
+.sp
+\fB<package\-file\-spec>\fP is similar to \fB<package\-spec>\fP, except provides
+matching is not performed. Therefore, \fB<package\-file\-spec>\fP is matched only
+against NEVRAs and file provides.
+.sp
+\fB<package\-name\-spec>\fP is matched against NEVRAs only.
+.SS Globs
+.sp
+Package specification supports the same glob pattern matching that shell does,
+in all three above mentioned packages it matches against (NEVRAs, provides and
+file provides).
+.sp
+The following patterns are supported:
+.INDENT 0.0
+.TP
+.B \fB*\fP
+Matches any number of characters.
+.TP
+.B \fB?\fP
+Matches any single character.
+.TP
+.B \fB[]\fP
+Matches any one of the enclosed characters. A pair of characters separated
+by a hyphen denotes a range expression; any character that falls between
+those two characters, inclusive, is matched. If the first character
+following the \fB[\fP is a \fB!\fP or a \fB^\fP then any character not enclosed
+is matched.
+.UNINDENT
+.sp
+Note: Curly brackets (\fB{}\fP) are not supported. You can still use them in
+shells that support them and let the shell do the expansion, but if quoted or
+escaped, dnf will not expand them.
+.SS NEVRA Matching
+.sp
+When matching against NEVRAs, partial matching is supported. DNF tries to match
+the spec against the following list of NEVRA forms (in decreasing order of
+priority):
+.INDENT 0.0
+.IP \(bu 2
+\fBname\-[epoch:]version\-release.arch\fP
+.IP \(bu 2
+\fBname.arch\fP
+.IP \(bu 2
+\fBname\fP
+.IP \(bu 2
+\fBname\-[epoch:]version\-release\fP
+.IP \(bu 2
+\fBname\-[epoch:]version\fP
+.UNINDENT
+.sp
+Note that \fBname\fP can in general contain dashes (e.g. \fBpackage\-with\-dashes\fP).
+.sp
+The first form that matches any packages is used and the remaining forms are
+not tried. If none of the forms match any packages, an attempt is made to match
+the \fB<package\-spec>\fP against full package NEVRAs. This is only relevant
+if globs are present in the \fB<package\-spec>\fP\&.
+.sp
+\fB<package\-spec>\fP matches NEVRAs the same way \fB<package\-name\-spec>\fP does,
+but in case matching NEVRAs fails, it attempts to match against provides and
+file provides of packages as well.
+.sp
+You can specify globs as part of any of the five NEVRA components. You can also
+specify a glob pattern to match over multiple NEVRA components (in other words,
+to match across the NEVRA separators). In that case, however, you need to write
+the spec to match against full package NEVRAs, as it is not possible to split
+such spec into NEVRA forms.
+.SS Specifying NEVRA Matching Explicitly
+.sp
+Some commands (\fBautoremove\fP, \fBinstall\fP, \fBremove\fP and \fBrepoquery\fP) also
+have aliases with suffixes \fB\-n\fP, \fB\-na\fP and \fB\-nevra\fP that allow to
+explicitly specify how to parse the arguments:
+.INDENT 0.0
+.IP \(bu 2
+Command \fBinstall\-n\fP only matches against \fBname\fP\&.
+.IP \(bu 2
+Command \fBinstall\-na\fP only matches against \fBname.arch\fP\&.
+.IP \(bu 2
+Command \fBinstall\-nevra\fP only matches against \fBname\-[epoch:]version\-release.arch\fP\&.
+.UNINDENT
+.SH SPECIFYING PROVIDES
+.sp
+\fB<provide\-spec>\fP in command descriptions means the command operates on
+packages providing the given spec. This can either be an explicit provide, an
+implicit provide (i.e. name of the package) or a file provide. The selection is
+case\-sensitive and globbing is supported.
+.SS Specifying File Provides
+.sp
+If a spec starts with either \fB/\fP or \fB*/\fP, it is considered as a potential file provide.
+.SH SPECIFYING GROUPS
+.sp
+\fB<group\-spec>\fP allows one to select (environment) groups a particular operation should work
+on. It is a case insensitive string (supporting globbing characters) that is
+matched against a group\(aqs ID, canonical name and name translated into the
+current LC_MESSAGES locale (if possible).
+.SH SPECIFYING MODULES
+.sp
+\fB<module\-spec>\fP allows one to select modules or profiles a particular operation should work
+on.
+.sp
+It is in the form of \fBNAME:STREAM:VERSION:CONTEXT:ARCH/PROFILE\fP and supported partial forms are the following:
+.INDENT 0.0
+.IP \(bu 2
+\fBNAME\fP
+.IP \(bu 2
+\fBNAME:STREAM\fP
+.IP \(bu 2
+\fBNAME:STREAM:VERSION\fP
+.IP \(bu 2
+\fBNAME:STREAM:VERSION:CONTEXT\fP
+.IP \(bu 2
+all above combinations with \fB::ARCH\fP (e.g. \fBNAME::ARCH\fP)
+.IP \(bu 2
+\fBNAME:STREAM:VERSION:CONTEXT:ARCH\fP
+.IP \(bu 2
+all above combinations with \fB/PROFILE\fP (e.g. \fBNAME/PROFILE\fP)
+.UNINDENT
+.sp
+In case stream is not specified, the enabled or the default stream is used, in this order. In case profile is not specified, the system default profile or the \(aqdefault\(aq profile is used.
+.SH SPECIFYING TRANSACTIONS
+.sp
+\fB<transaction\-spec>\fP can be in one of several forms. If it is an integer, it
+specifies a transaction ID. Specifying \fBlast\fP is the same as specifying the ID
+of the most recent transaction. The last form is \fBlast\-<offset>\fP, where
+\fB<offset>\fP is a positive integer. It specifies offset\-th transaction preceding
+the most recent transaction.
+.SH PACKAGE FILTERING
+.sp
+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.
+.SS Exclude Filtering
+.sp
+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 \-\fI\%\-disableexcludes\fP
+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 \-\fI\%\-disableplugin\fP command line option.
+.sp
+To disable all excludes for e.g. the install command you can use the following combination
+of command line options:
+.sp
+\fBdnf \-\-disableexcludes=all \-\-disableplugin="*" install bash\fP
+.SS Modular Filtering
+.sp
+Please see the modularity documentation for details on how Modular
+Filtering works.
+.sp
+With modularity, only RPM packages from \fBactive\fP module streams are included in the available
+package set. RPM packages from \fBinactive\fP module streams, as well as non\-modular packages with
+the same name or provides as a package from an \fBactive\fP module stream, are filtered out. Modular
+filtering is not applied to packages added from the command line, installed packages, or packages
+from repositories with \fBmodule_hotfixes=true\fP in their \fB\&.repo\fP file.
+.sp
+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
+\fBmodule_hotfixes=true\fP in the \fB\&.repo\fP file or use \fB\-\-setopt=<repo_id>.module_hotfixes=true\fP\&.
+.sp
+To discover the module which contains an excluded package use
+\fI\%dnf module provides\fP\&.
+.SH METADATA SYNCHRONIZATION
+.sp
+Correct operation of DNF depends on having access to up\-to\-date data from all enabled repositories but contacting remote mirrors on every operation considerably slows it down and costs bandwidth for both the client and the repository provider. The metadata_expire (see \fBdnf.conf(5)\fP) repository configuration option is used by DNF to determine whether a particular local copy of repository data is due to be re\-synced. It is crucial that the repository providers set the option well, namely to a value where it is guaranteed that if particular metadata was available in time \fBT\fP on the server, then all packages it references will still be available for download from the server in time \fBT + metadata_expire\fP\&.
+.sp
+To further reduce the bandwidth load, some of the commands where having up\-to\-date metadata is not critical (e.g. the \fBlist\fP command) do not look at whether a repository is expired and whenever any version of it is locally available to the user\(aqs account, it will be used. For non\-root use, see also the \fB\-\-cacheonly\fP switch. Note that in all situations the user can force synchronization of all enabled repositories with the \fB\-\-refresh\fP switch.
+.SH CONFIGURATION FILES REPLACEMENT POLICY
+.sp
+The updated packages could replace the old modified configuration files
+with the new ones or keep the older files. Neither of the files are actually replaced.
+To the conflicting ones RPM gives additional suffix to the origin name. Which file
+should maintain the true name after transaction is not controlled by package manager
+but is specified by each package itself, following packaging guideline.
+.SH FILES
+.INDENT 0.0
+.TP
+.B \fBCache Files\fP
+/var/cache/dnf
+.TP
+.B \fBMain Configuration\fP
+/etc/dnf/dnf.conf
+.TP
+.B \fBRepository\fP
+/etc/yum.repos.d/
+.UNINDENT
+.SH SEE ALSO
+.INDENT 0.0
+.IP \(bu 2
+\fBdnf.conf(5)\fP, DNF Configuration Reference
+.IP \(bu 2
+\fBdnf\-PLUGIN(8)\fP for documentation on DNF plugins.
+.IP \(bu 2
+\fBdnf.modularity(7)\fP, Modularity overview\&.
+.IP \(bu 2
+\fBdnf\-transaction\-json(5)\fP, Stored Transaction JSON Format Specification\&.
+.IP \(bu 2
+\fI\%DNF\fP project homepage (\fI\%https://github.com/rpm\-software\-management/dnf/\fP)
+.IP \(bu 2
+How to report a bug (\fI\%https://github.com/rpm\-software\-management/dnf/wiki/Bug\-Reporting\fP)
+.IP \(bu 2
+\fI\%YUM\fP project homepage (\fI\%http://yum.baseurl.org/\fP)
+.UNINDENT
+.SH AUTHOR
+See AUTHORS in DNF source distribution.
+.SH COPYRIGHT
+2012-2022, Red Hat, Licensed under GPLv2+
+.\" Generated by docutils manpage writer.
+.
diff --git a/yum.conf.5 b/yum.conf.5
new file mode 100644
index 0000000..24b05c5
--- /dev/null
+++ b/yum.conf.5
@@ -0,0 +1,1312 @@
+.\" Man page generated from reStructuredText.
+.
+.
+.nr rst2man-indent-level 0
+.
+.de1 rstReportMargin
+\\$1 \\n[an-margin]
+level \\n[rst2man-indent-level]
+level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
+-
+\\n[rst2man-indent0]
+\\n[rst2man-indent1]
+\\n[rst2man-indent2]
+..
+.de1 INDENT
+.\" .rstReportMargin pre:
+. RS \\$1
+. nr rst2man-indent\\n[rst2man-indent-level] \\n[an-margin]
+. nr rst2man-indent-level +1
+.\" .rstReportMargin post:
+..
+.de UNINDENT
+. RE
+.\" indent \\n[an-margin]
+.\" old: \\n[rst2man-indent\\n[rst2man-indent-level]]
+.nr rst2man-indent-level -1
+.\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
+.in \\n[rst2man-indent\\n[rst2man-indent-level]]u
+..
+.TH "YUM.CONF" "5" "Apr 29, 2022" "4.12.0" "DNF"
+.SH NAME
+yum.conf \- redirecting to DNF Configuration Reference
+.SH DESCRIPTION
+.sp
+\fI\%DNF\fP by default uses the global configuration file at \fB/etc/dnf/dnf.conf\fP and
+all *.repo files found under \fB/etc/yum.repos.d\fP\&. The latter is typically used
+for repository configuration and takes precedence over global configuration.
+.sp
+The configuration file has INI format consisting of section declaration and
+\fBname=value\fP options below each on separate line. There are two types of sections
+in the configuration files: main and repository. Main section defines all global
+configuration options and should be only one.
+.sp
+The repository sections define the configuration for each (remote or local)
+repository. The section name of the repository in brackets serve as repo ID reference
+and should be unique across configuration files. The allowed characters of repo ID
+string are lower and upper case alphabetic letters, digits, \fB\-\fP, \fB_\fP, \fB\&.\fP
+and \fB:\fP\&. The minimal repository configuration file should aside from repo ID
+consists of \fI\%baseurl\fP, \fI\%metalink\fP
+or \fI\%mirrorlist\fP option definition.
+.SH DISTRIBUTION-SPECIFIC CONFIGURATION
+.sp
+Configuration options, namely \fI\%best\fP and
+\fI\%skip_if_unavailable\fP, can be set in the DNF
+configuration file by your distribution to override the DNF defaults.
+.SH [MAIN] OPTIONS
+.INDENT 0.0
+.TP
+.B \fBallow_vendor_change\fP
+\fI\%boolean\fP
+.sp
+If disabled dnf will stick to vendor when upgrading or downgrading rpms.
+Default is \fBTrue\fP
+.sp
+\fBWARNING:\fP
+.INDENT 7.0
+.INDENT 3.5
+This option is currently not supported for \fIdowngrade\fP and \fIdistro\-sync\fP commands
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBarch\fP
+\fI\%string\fP
+.sp
+The architecture used for installing packages. By default this is auto\-detected. Often used
+together with \fI\%ignorearch\fP option.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBassumeno\fP
+\fI\%boolean\fP
+.sp
+If enabled dnf will assume \fBNo\fP where it would normally prompt for
+confirmation from user input. Default is \fBFalse\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBassumeyes\fP
+\fI\%boolean\fP
+.sp
+If enabled dnf will assume \fBYes\fP where it would normally prompt for
+confirmation from user input (see also \fI\%defaultyes\fP). Default is \fBFalse\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBautocheck_running_kernel\fP
+\fI\%boolean\fP
+.sp
+Automatic check whether there is installed newer kernel module with security update than currently running kernel. Default is \fBTrue\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBbasearch\fP
+\fI\%string\fP
+.sp
+The base architecture used for installing packages. By default this is auto\-detected.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBbest\fP
+\fI\%boolean\fP
+.sp
+\fBTrue\fP instructs the solver to either use a package with the highest available
+version or fail. On \fBFalse\fP, do not fail if the latest version cannot be
+installed and go with the lower version. The default is \fBFalse\fP\&.  Note
+this option in particular \fI\%can be set in your configuration file by
+your distribution\fP\&. Also note that the
+use of the highest available version is only guaranteed for the packages
+directly requested and not for their dependencies.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBcachedir\fP
+\fI\%string\fP
+.sp
+Path to a directory used by various DNF subsystems for storing cache data.
+Has a reasonable root\-writable default depending on the distribution. DNF
+needs to be able to create files and directories at this location.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBcacheonly\fP
+\fI\%boolean\fP
+.sp
+If set to \fBTrue\fP DNF will run entirely from system cache, will not update
+the cache and will use it even in case it is expired. Default is \fBFalse\fP\&.
+.sp
+API Notes: Must be set before repository objects are created. Plugins must set
+this in the pre_config hook. Later changes are ignored.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBcheck_config_file_age\fP
+\fI\%boolean\fP
+.sp
+Specifies whether dnf should automatically expire metadata of repos, which are older than
+their corresponding configuration file (usually the dnf.conf file and the foo.repo file).
+Default is \fBTrue\fP (perform the check). Expire of metadata is also affected by metadata age.
+See also \fI\%metadata_expire\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBclean_requirements_on_remove\fP
+\fI\%boolean\fP
+.sp
+Remove dependencies that are no longer used during \fBdnf remove\fP\&. A package
+only qualifies for removal via \fBclean_requirements_on_remove\fP if it was
+installed through DNF but not on explicit user request, i.e. it was
+pulled in as a dependency. The default is True.
+(\fI\%installonlypkgs\fP are never automatically removed.)
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBconfig_file_path\fP
+\fI\%string\fP
+.sp
+Path to the default main configuration file. Default is \fB/etc/dnf/dnf.conf\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdebuglevel\fP
+\fI\%integer\fP
+.sp
+Debug messages output level, in the range 0 to 10. The higher the number the
+more debug output is put to stdout. Default is 2.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdebug_solver\fP
+\fI\%boolean\fP
+.sp
+Controls whether the libsolv debug files should be created when solving the
+transaction. The debug files are created in the \fI\&./debugdata\fP directory.
+Default is \fBFalse\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdefaultyes\fP
+\fI\%boolean\fP
+.sp
+If enabled the default answer to user confirmation prompts will be \fBYes\fP\&. Not
+to be confused with \fI\%assumeyes\fP which will not prompt at all. Default is \fBFalse\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdiskspacecheck\fP
+\fI\%boolean\fP
+.sp
+Controls whether rpm should check available disk space during the transaction.
+Default is \fBTrue\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBerrorlevel\fP
+\fI\%integer\fP
+.sp
+Error messages output level, in the range 0 to 10. The higher the number the
+more error output is put to stderr. Default is 3. This is deprecated in DNF
+and overwritten by \-\-verbose commandline
+option.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBexclude_from_weak\fP
+\fI\%list\fP
+.sp
+Prevent installing packages as weak dependencies (recommends or supplements). The packages can be specified
+by a name or a glob and separated by a comma. Defaults to \fB[]\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBexclude_from_weak_autodetect\fP
+\fI\%boolean\fP
+.sp
+If enabled, dnf will autodetect unmet weak dependencies (recommends or supplements) of packages installed on the
+system. Providers of these weak dependencies will not be installed by dnf as weak dependencies any more (they will
+still be installed if pulled in as a regular dependency). Defaults to \fBtrue\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBexit_on_lock\fP
+\fI\%boolean\fP
+.sp
+Should the dnf client exit immediately when something else has the lock. Default is \fBFalse\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBgpgkey_dns_verification\fP
+\fI\%boolean\fP
+.sp
+Should the dnf attempt to automatically verify GPG verification keys using the DNS
+system. This option requires the unbound python module (python3\-unbound) to
+be installed on the client system. This system has two main features. The first
+one is to check if any of the already installed keys have been revoked. Automatic
+removal of the key is not yet available, so it is up to the user, to remove
+revoked keys from the system. The second feature is automatic verification
+of new keys when a repository is added to the system. In interactive mode, the
+result is written to the output as a suggestion to the user. In
+non\-interactive mode (i.e. when \-y is used), this system will automatically
+accept keys that are available in the DNS and are correctly signed using
+DNSSEC. It will also accept keys that do not exist in the DNS system and
+their NON\-existence is cryptographically proven using DNSSEC. This is mainly to
+preserve backward compatibility.
+Default is \fBFalse\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBgroup_package_types\fP
+\fI\%list\fP
+.sp
+List of the following: optional, default, mandatory. Tells dnf which type of packages in groups will
+be installed when \(aqgroupinstall\(aq is called. Default is: \fBdefault, mandatory\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBignorearch\fP
+\fI\%boolean\fP
+.sp
+If set to \fBTrue\fP, RPM will allow attempts to install packages incompatible with the CPU\(aqs
+architecture. Defaults to \fBFalse\fP\&. Often used together with
+\fI\%arch\fP option.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBinstallonlypkgs\fP
+\fI\%list\fP
+.sp
+List of provide names of packages that should only ever be installed, never
+upgraded. Kernels in particular fall into this category.
+These packages are never removed by \fBdnf autoremove\fP even if they were
+installed as dependencies (see
+\fI\%clean_requirements_on_remove\fP
+for auto removal details).
+This option append the list values to the default installonlypkgs list used
+by DNF. The number of kept package versions is regulated
+by \fI\%installonly_limit\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBinstallonly_limit\fP
+\fI\%integer\fP
+.sp
+Number of \fI\%installonly packages\fP allowed to be installed
+concurrently. Defaults to 3. The minimal number of installonly packages is 2. Value 0 means
+unlimited number of installonly packages. Value 1 is explicitly not allowed since it
+complicates kernel upgrades due to protection of the running kernel from removal.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBinstallroot\fP
+\fI\%string\fP
+.sp
+The root of the filesystem for all packaging operations. It requires an absolute path. See also \fI\%\-\-installroot commandline option\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBinstall_weak_deps\fP
+\fI\%boolean\fP
+.sp
+When this option is set to True and a new package is about to be
+installed, all packages linked by weak dependency relation (Recommends or Supplements flags) with this package will be pulled into the transaction.
+Default is \fBTrue\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBkeepcache\fP
+\fI\%boolean\fP
+.sp
+Keeps downloaded packages in the cache when set to True. Even if it is set to False and packages have not been
+installed they will still persist until next successful transaction. The default
+is \fBFalse\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBlogdir\fP
+\fI\%string\fP
+.sp
+Directory where the log files will be stored. Default is \fB/var/log\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBlogfilelevel\fP
+\fI\%integer\fP
+.sp
+Log file messages output level, in the range 0 to 10. The higher the number the
+more debug output is put to logs. Default is 9.
+.sp
+This option controls dnf.log, dnf.librepo.log and hawkey.log. Although dnf.librepo.log
+and hawkey.log are affected only by setting the logfilelevel to 10.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBlog_compress\fP
+\fI\%boolean\fP
+.sp
+When set to \fBTrue\fP, log files are compressed when they are rotated. Default is \fBFalse\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBlog_rotate\fP
+\fI\%integer\fP
+.sp
+Log files are rotated \fBlog_rotate\fP times before being removed. If \fBlog_rotate\fP
+is \fB0\fP, the rotation is not performed.
+Default is \fB4\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBlog_size\fP
+storage size
+.sp
+Log  files are rotated when they grow bigger than log_size bytes. If
+log_size is 0, the rotation is not performed. The default is 1 MB. Valid
+units are \(aqk\(aq, \(aqM\(aq, \(aqG\(aq.
+.sp
+The size applies for individual log files, not the sum of all log files.
+See also \fI\%log_rotate\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBmetadata_timer_sync\fP
+time in seconds
+.sp
+The minimal period between two consecutive \fBmakecache timer\fP runs. The
+command will stop immediately if it\(aqs less than this time period since its
+last run. Does not affect simple \fBmakecache\fP run. Use \fB0\fP to completely
+disable automatic metadata synchronizing. The default corresponds to three
+hours. The value is rounded to the next commenced hour.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBmodule_obsoletes\fP
+\fI\%boolean\fP
+.sp
+This option controls whether dnf should apply modular obsoletes when possible. Default is \fBFalse\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBmodule_platform_id\fP
+\fI\%string\fP
+.sp
+Set this to $name:$stream to override PLATFORM_ID detected from \fB/etc/os\-release\fP\&.
+It is necessary to perform a system upgrade and switch to a new platform.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBmodule_stream_switch\fP
+\fI\%boolean\fP
+.sp
+This option controls whether it\(aqs possible to switch enabled streams of a module. Default is \fBFalse\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBmultilib_policy\fP
+\fI\%string\fP
+.sp
+Controls how multilib packages are treated during install operations. Can either be \fB"best"\fP (the default) for
+the depsolver to prefer packages which best match the system\(aqs architecture, or \fB"all"\fP to install packages for
+all available architectures.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBobsoletes\fP
+\fI\%boolean\fP
+.sp
+This option only has affect during an install/update. It enables
+dnf\(aqs obsoletes processing logic, which means it makes dnf check whether
+any dependencies of given package are no longer required and removes them.
+Useful when doing distribution level upgrades.
+Default is \(aqtrue\(aq.
+.sp
+Command\-line option: \-\-obsoletes
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBpersistdir\fP
+\fI\%string\fP
+.sp
+Directory where DNF stores its persistent data between runs. Default is \fB"/var/lib/dnf"\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBpluginconfpath\fP
+\fI\%list\fP
+.sp
+List of directories that are searched for plugin configurations to load. All
+configuration files found in these directories, that are named same as a
+plugin, are parsed. The default path is \fB/etc/dnf/plugins\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBpluginpath\fP
+\fI\%list\fP
+.sp
+List of directories that are searched for plugins to load. Plugins found in \fIany of the directories\fP in this configuration option are used. The default contains a Python version\-specific path.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBplugins\fP
+\fI\%boolean\fP
+.sp
+Controls whether the plugins are enabled. Default is \fBTrue\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBprotected_packages\fP
+\fI\%list\fP
+.sp
+List of packages that DNF should never completely remove. They are protected via Obsoletes as well as user/plugin removals.
+.sp
+The default is: \fBdnf\fP, \fBglob:/etc/yum/protected.d/*.conf\fP and \fBglob:/etc/dnf/protected.d/*.conf\fP\&. So any packages which should be protected can do so by including a file in \fB/etc/dnf/protected.d\fP with their package name in it.
+.sp
+DNF will protect also the package corresponding to the running version of the kernel. See also \fI\%protect_running_kernel\fP option.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBprotect_running_kernel\fP
+\fI\%boolean\fP
+.sp
+Controls whether the package corresponding to the running version of kernel is protected from removal. Default is \fBTrue\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBreleasever\fP
+\fI\%string\fP
+.sp
+Used for substitution of \fB$releasever\fP in the repository configuration.
+See also \fI\%repo variables\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBreposdir\fP
+\fI\%list\fP
+.sp
+DNF searches for repository configuration files in the paths specified by
+\fBreposdir\fP\&. The behavior of \fBreposdir\fP could differ when it is used
+along with \-\fI\%\-installroot\fP option.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBrpmverbosity\fP
+\fI\%string\fP
+.sp
+RPM debug scriptlet output level. One of: \fBcritical\fP, \fBemergency\fP,
+\fBerror\fP, \fBwarn\fP, \fBinfo\fP or \fBdebug\fP\&. Default is \fBinfo\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBstrict\fP
+\fI\%boolean\fP
+.sp
+If disabled, all unavailable packages or packages with broken dependencies given to DNF command will be skipped without raising the error causing the whole operation to fail. Currently works for install command only. The default is True.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBtsflags\fP
+\fI\%list\fP
+.sp
+List of strings adding extra flags for the RPM transaction.
+.TS
+center;
+|l|l|.
+_
+T{
+tsflag value
+T}	T{
+RPM Transaction Flag
+T}
+_
+T{
+noscripts
+T}	T{
+RPMTRANS_FLAG_NOSCRIPTS
+T}
+_
+T{
+test
+T}	T{
+RPMTRANS_FLAG_TEST
+T}
+_
+T{
+notriggers
+T}	T{
+RPMTRANS_FLAG_NOTRIGGERS
+T}
+_
+T{
+nodocs
+T}	T{
+RPMTRANS_FLAG_NODOCS
+T}
+_
+T{
+justdb
+T}	T{
+RPMTRANS_FLAG_JUSTDB
+T}
+_
+T{
+nocontexts
+T}	T{
+RPMTRANS_FLAG_NOCONTEXTS
+T}
+_
+T{
+nocaps
+T}	T{
+RPMTRANS_FLAG_NOCAPS
+T}
+_
+T{
+nocrypto
+T}	T{
+RPMTRANS_FLAG_NOFILEDIGEST
+T}
+_
+.TE
+.sp
+The \fBnocrypto\fP option will also set the \fB_RPMVSF_NOSIGNATURES\fP and
+\fB_RPMVSF_NODIGESTS\fP VS flags. The \fBtest\fP option provides a transaction check
+without performing the transaction. It includes downloading of packages, gpg keys check
+(including permanent import of additional keys if necessary), and rpm check to prevent
+file conflicts.
+The \fBnocaps\fP is supported with rpm\-4.14 or later. When \fBnocaps\fP is used but rpm
+doesn\(aqt support it, DNF only reports it as an invalid tsflag.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBupgrade_group_objects_upgrade\fP
+\fI\%boolean\fP
+.sp
+Set this to False to disable the automatic running of \fBgroup upgrade\fP when running the \fBupgrade\fP command. Default is \fBTrue\fP (perform the operation).
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBvarsdir\fP
+\fI\%list\fP
+.sp
+List of directories where variables definition files are looked for. Defaults to
+\fB"/etc/dnf/vars", "/etc/yum/vars"\fP\&. See \fI\%variable files\fP
+in Configuration reference.
+.TP
+.B \fBzchunk\fP
+\fI\%boolean\fP
+.sp
+Enables or disables the use of repository metadata compressed using the zchunk format (if available). Default is \fBTrue\fP\&.
+.UNINDENT
+.SH [MAIN] OPTIONS - COLORS
+.INDENT 0.0
+.TP
+.B \fBcolor\fP
+\fI\%string\fP
+.sp
+Controls if DNF uses colored output on the command line.
+Possible values: "auto", "never", "always". Default is "auto".
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBcolor_list_available_downgrade\fP
+\fI\%color\fP
+.sp
+Color of available packages that are older than installed packages.
+The option is used during list operations. Default is magenta.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBcolor_list_available_install\fP
+\fI\%color\fP
+.sp
+Color of packages that are available for installation and none of their versions in installed.
+The option is used during list operations. Default is bold,cyan.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBcolor_list_available_reinstall\fP
+\fI\%color\fP
+.sp
+Color of available packages that are identical to installed versions and are available for reinstalls. Default is bold,underline,green.
+The option is used during list operations.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBcolor_list_available_upgrade\fP
+\fI\%color\fP
+.sp
+Color of available packages that are newer than installed packages. Default is bold,blue.
+The option is used during list operations.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBcolor_list_installed_extra\fP
+\fI\%color\fP
+.sp
+Color of installed packages that do not have any version among available packages.
+The option is used during list operations. Default is bold,red.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBcolor_list_installed_newer\fP
+\fI\%color\fP
+.sp
+Color of installed packages that are newer than any version among available packages.
+The option is used during list operations. Default is bold,yellow.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBcolor_list_installed_older\fP
+\fI\%color\fP
+.sp
+Color of installed packages that are older than any version among available packages.
+The option is used during list operations. Default is yellow.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBcolor_list_installed_reinstall\fP
+\fI\%color\fP
+.sp
+Color of installed packages that are among available packages and can be reinstalled.
+The option is used during list operations. Default is cyan.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBcolor_search_match\fP
+\fI\%color\fP
+.sp
+Color of patterns matched in search output. Default is bold,magenta.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBcolor_update_installed\fP
+\fI\%color\fP
+.sp
+Color of removed packages. Default is red.
+This option is used during displaying transactions.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBcolor_update_local\fP
+\fI\%color\fP
+.sp
+Color of local packages that are installed from the @commandline repository.
+This option is used during displaying transactions. Default is green.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBcolor_update_remote\fP
+\fI\%color\fP
+.sp
+Color of packages that are installed/upgraded/downgraded from remote repositories.
+This option is used during displaying transactions. Default is bold,green.
+.UNINDENT
+.SH REPO OPTIONS
+.INDENT 0.0
+.TP
+.B \fBbaseurl\fP
+\fI\%list\fP
+.sp
+List of URLs for the repository. Defaults to \fB[]\fP\&.
+.sp
+URLs are tried in the listed order (equivalent to yum\(aqs "failovermethod=priority" behaviour).
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBcost\fP
+\fI\%integer\fP
+.sp
+The relative cost of accessing this repository, defaulting to 1000. This
+value is compared when the priorities of two repositories are the same. The
+repository with \fIthe lowest cost\fP is picked. It is useful to make the
+library prefer on\-disk repositories to remote ones.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBenabled\fP
+\fI\%boolean\fP
+.sp
+Include this repository as a package source. The default is True.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBgpgkey\fP
+\fI\%list\fP of strings
+.sp
+URLs of a GPG key files that can be used for signing metadata and packages of this repository, empty by default. If a file can not be verified using the already imported keys, import of keys from this option is attempted and the keys are then used for verification.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBmetalink\fP
+\fI\%string\fP
+.sp
+URL of a metalink for the repository. Defaults to \fBNone\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBmirrorlist\fP
+\fI\%string\fP
+.sp
+URL of a mirrorlist for the repository. Defaults to \fBNone\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBmodule_hotfixes\fP
+\fI\%boolean\fP
+.sp
+Set this to True to disable module RPM filtering and make all RPMs from the repository available. The default is False.
+This allows user to create a repository with cherry\-picked hotfixes that are included in a package set on a modular system.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBname\fP
+\fI\%string\fP
+.sp
+A human\-readable name of the repository. Defaults to the ID of the repository.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBpriority\fP
+\fI\%integer\fP
+.sp
+The priority value of this repository, default is 99. If there is more than one candidate package for a particular operation, the one from a repo with \fIthe lowest priority value\fP is picked, possibly despite being less convenient otherwise (e.g. by being a lower version).
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBtype\fP
+\fI\%string\fP
+.sp
+Type of repository metadata. Supported values are: \fBrpm\-md\fP\&.
+Aliases for \fBrpm\-md\fP: \fBrpm\fP, \fBrepomd\fP, \fBrpmmd\fP, \fByum\fP, \fBYUM\fP\&.
+.UNINDENT
+.SH REPO VARIABLES
+.sp
+Right side of every repo option can be enriched by the following variables:
+.sp
+\fB$arch\fP
+.INDENT 0.0
+.INDENT 3.5
+Refers to the system’s CPU architecture e.g, aarch64, i586, i686 and x86_64.
+.UNINDENT
+.UNINDENT
+.sp
+\fB$basearch\fP
+.INDENT 0.0
+.INDENT 3.5
+Refers to the base architecture of the system. For example, i686 and i586 machines
+both have a base architecture of i386, and AMD64 and Intel64 machines have a base architecture of x86_64.
+.UNINDENT
+.UNINDENT
+.sp
+\fB$releasever\fP
+.INDENT 0.0
+.INDENT 3.5
+Refers to the release version of operating system which DNF derives from information available in RPMDB.
+.UNINDENT
+.UNINDENT
+.sp
+In addition to these hard coded variables, user\-defined ones can also be used. They can be defined either via \fI\%variable files\fP, or by using special environmental variables. The names of these variables must be prefixed with DNF_VAR_ and they can only consist of alphanumeric characters and underscores:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+$ DNF_VAR_MY_VARIABLE=value
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+To use such variable in your repository configuration remove the prefix. E.g.:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+[myrepo]
+baseurl=https://example.site/pub/fedora/$MY_VARIABLE/releases/$releasever
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Note that it is not possible to override the \fBarch\fP and \fBbasearch\fP variables using either variable files or environmental variables.
+.sp
+Although users are encouraged to use named variables, the numbered environmental variables \fBDNF0\fP \- \fBDNF9\fP are still supported:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+$ DNF1=value
+
+[myrepo]
+baseurl=https://example.site/pub/fedora/$DNF1/releases/$releasever
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SH OPTIONS FOR BOTH [MAIN] AND REPO
+.sp
+Some options can be applied in either the main section, per repository, or in a
+combination. The value provided in the main section is used for all repositories
+as the default value, which repositories can then override in their
+configuration.
+.INDENT 0.0
+.TP
+.B \fBbandwidth\fP
+storage size
+.sp
+Total bandwidth available for downloading. Meaningful when used with the \fI\%throttle option\fP\&. Storage size is in bytes by default but can be specified with a unit of storage. Valid units are \(aqk\(aq, \(aqM\(aq, \(aqG\(aq.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBcountme\fP
+\fI\%boolean\fP
+.sp
+Determines whether a special flag should be added to a single, randomly
+chosen metalink/mirrorlist query each week.
+This allows the repository owner to estimate the number of systems
+consuming it, by counting such queries over a week\(aqs time, which is much
+more accurate than just counting unique IP addresses (which is subject to
+both overcounting and undercounting due to short DHCP leases and NAT,
+respectively).
+.sp
+The flag is a simple "countme=N" parameter appended to the metalink and
+mirrorlist URL, where N is an integer representing the "longevity" bucket
+this system belongs to.
+The following 4 buckets are defined, based on how many full weeks have
+passed since the beginning of the week when this system was installed: 1 =
+first week, 2 = first month (2\-4 weeks), 3 = six months (5\-24 weeks) and 4
+= more than six months (> 24 weeks).
+This information is meant to help distinguish short\-lived installs from
+long\-term ones, and to gather other statistics about system lifecycle.
+.sp
+Default is False.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdeltarpm\fP
+\fI\%boolean\fP
+.sp
+When enabled, DNF will save bandwidth by downloading much smaller delta RPM
+files, rebuilding them to RPM locally. However, this is quite CPU and I/O
+intensive. Default is True.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBdeltarpm_percentage\fP
+\fI\%integer\fP
+.sp
+When the relative size of delta vs pkg is larger than this, delta is not used.  Default value is 75
+(Deltas must be at least 25% smaller than the pkg).  Use \fI0\fP to turn off delta rpm processing. Local repositories (with
+\fI\%file://\fP baseurl) have delta rpms turned off by default.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBenablegroups\fP
+\fI\%boolean\fP
+.sp
+Determines whether DNF will allow the use of package groups for this repository. Default is True (package groups are allowed).
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBexcludepkgs\fP
+\fI\%list\fP
+.sp
+Exclude packages of this repository, specified by a name or a glob and
+separated by a comma, from all operations.
+Can be disabled using \fB\-\-disableexcludes\fP command line switch.
+Defaults to \fB[]\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBfastestmirror\fP
+\fI\%boolean\fP
+.sp
+If enabled a metric is used to find the fastest available mirror. This overrides the order provided by the mirrorlist/metalink file itself. This file is often dynamically generated by the server to provide the best download speeds and enabling fastestmirror overrides this. The default is False.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBgpgcheck\fP
+\fI\%boolean\fP
+.sp
+Whether to perform GPG signature check on packages found in this repository.
+The default is False.
+.sp
+This option can only be used to strengthen the active RPM security policy set with the \fB%_pkgverify_level\fP macro (see the \fB/usr/lib/rpm/macros\fP file for details).
+That means, if the macro is set to \(aqsignature\(aq or \(aqall\(aq and this option is False, it will be overridden to True during DNF runtime, and a warning will be printed.
+To squelch the warning, make sure this option is True for every enabled repository, and also enable \fI\%localpkg_gpgcheck\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBincludepkgs\fP
+\fI\%list\fP
+.sp
+Include packages of this repository, specified by a name or a glob and separated by a comma, in all operations.
+Inverse of \fI\%excludepkgs\fP, DNF will exclude any package in the repository that doesn\(aqt match this list. This works in conjunction with \fBexcludepkgs\fP and doesn\(aqt override it, so if you \(aqexcludepkgs=*.i386\(aq and \(aqincludepkgs=python*\(aq then only packages starting with python that do not have an i386 arch will be seen by DNF in this repo.
+Can be disabled using \fB\-\-disableexcludes\fP command line switch.
+Defaults to \fB[]\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBip_resolve\fP
+IP address type
+.sp
+Determines how DNF resolves host names. Set this to \(aq4\(aq/\(aqIPv4\(aq or \(aq6\(aq/\(aqIPv6\(aq to resolve to IPv4 or IPv6 addresses only. By default, DNF resolves to either addresses.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBlocalpkg_gpgcheck\fP
+\fI\%boolean\fP
+.sp
+Whether to perform a GPG signature check on local packages (packages in a file, not in a repository).
+The default is False.
+This option is subject to the active RPM security policy (see \fI\%gpgcheck\fP for more details).
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBmax_parallel_downloads\fP
+\fI\%integer\fP
+.sp
+Maximum number of simultaneous package downloads. Defaults to 3. Maximum of 20.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBmetadata_expire\fP
+time in seconds
+.sp
+The period after which the remote repository is checked for metadata update and in the positive
+case the local metadata cache is updated. The default corresponds to 48 hours. Set this to
+\fB\-1\fP or \fBnever\fP to make the repo never considered expired. Expire of metadata can be also
+triggered by change of timestamp of configuration files (\fBdnf.conf\fP, \fB<repo>.repo\fP). See
+also \fI\%check_config_file_age\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBminrate\fP
+storage size
+.sp
+This sets the low speed threshold in bytes per second. If the server is sending data at the same or slower speed than this value for at least \fI\%timeout option\fP seconds, DNF aborts the connection. The default is 1000. Valid units are \(aqk\(aq, \(aqM\(aq, \(aqG\(aq.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBpassword\fP
+\fI\%string\fP
+.sp
+The password to use for connecting to a repository with basic HTTP authentication. Empty by default.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBproxy\fP
+\fI\%string\fP
+.sp
+URL of a proxy server to connect through. Set to an empty string in the repository configuration to disable proxy setting inherited from the main section. The expected format of this option is \fB<scheme>://<ip\-or\-hostname>[:port]\fP\&.
+(For backward compatibility, \(aq_none_\(aq can be used instead of the empty string.)
+.sp
+Note: The curl environment variables (such as \fBhttp_proxy\fP) are effective if this option is unset (or \(aq_none_\(aq is set in the repository configuration). See the \fBcurl\fP man page for details.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBproxy_username\fP
+\fI\%string\fP
+.sp
+The username to use for connecting to the proxy server. Empty by default.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBproxy_password\fP
+\fI\%string\fP
+.sp
+The password to use for connecting to the proxy server. Empty by default.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBproxy_auth_method\fP
+\fI\%string\fP
+.sp
+The authentication method used by the proxy server. Valid values are
+.TS
+center;
+|l|l|.
+_
+T{
+method
+T}	T{
+meaning
+T}
+_
+T{
+basic
+T}	T{
+HTTP Basic authentication
+T}
+_
+T{
+digest
+T}	T{
+HTTP Digest authentication
+T}
+_
+T{
+negotiate
+T}	T{
+HTTP Negotiate (SPNEGO) authentication
+T}
+_
+T{
+ntlm
+T}	T{
+HTTP NTLM authentication
+T}
+_
+T{
+digest_ie
+T}	T{
+HTTP Digest authentication with an IE flavor
+T}
+_
+T{
+ntlm_wb
+T}	T{
+NTLM delegating to winbind helper
+T}
+_
+T{
+none
+T}	T{
+None auth method
+T}
+_
+T{
+any
+T}	T{
+All suitable methods
+T}
+_
+.TE
+.sp
+Defaults to \fBany\fP
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBproxy_sslcacert\fP
+\fI\%string\fP
+.sp
+Path to the file containing the certificate authorities to verify proxy SSL certificates.
+Empty by default \- uses system default.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBproxy_sslverify\fP
+\fI\%boolean\fP
+.sp
+When enabled, proxy SSL certificates are verified. If the client can not be authenticated, connecting fails and the repository is not used any further. If \fBFalse\fP, SSL connections can be used, but certificates are not verified. Default is \fBTrue\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBproxy_sslclientcert\fP
+\fI\%string\fP
+.sp
+Path to the SSL client certificate used to connect to proxy server.
+Empty by default.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBproxy_sslclientkey\fP
+\fI\%string\fP
+.sp
+Path to the SSL client key used to connect to proxy server.
+Empty by default.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBrepo_gpgcheck\fP
+\fI\%boolean\fP
+.sp
+Whether to perform GPG signature check on this repository\(aqs metadata. The default is False.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBretries\fP
+\fI\%integer\fP
+.sp
+Set the number of total retries for downloading packages. The number is
+accumulative, so e.g. for \fIretries=10\fP, dnf will fail after any package
+download fails for eleventh time. Setting this to \fI0\fP makes dnf try
+forever. Default is \fI10\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBskip_if_unavailable\fP
+\fI\%boolean\fP
+.sp
+If enabled, DNF will continue running and disable the repository that couldn\(aqt be synchronized
+for any reason. This option doesn\(aqt affect skipping of unavailable packages after dependency
+resolution. To check inaccessibility of repository use it in combination with
+refresh command line option\&. The default is \fBFalse\fP\&.
+Note this option in particular \fI\%can be set in your configuration file
+by your distribution\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBsslcacert\fP
+\fI\%string\fP
+.sp
+Path to the file containing the certificate authorities to verify SSL certificates.
+Empty by default \- uses system default.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBsslverify\fP
+\fI\%boolean\fP
+.sp
+When enabled, remote SSL certificates are verified. If the client can not be authenticated, connecting fails and the repository is not used any further. If \fBFalse\fP, SSL connections can be used, but certificates are not verified. Default is \fBTrue\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBsslverifystatus\fP
+\fI\%boolean\fP
+.sp
+When enabled, revocation status of the server certificate is verified using the "Certificate Status Request" TLS extension (aka. OCSP stapling). Default is \fBFalse\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBsslclientcert\fP
+\fI\%string\fP
+.sp
+Path to the SSL client certificate used to connect to remote sites.
+Empty by default.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBsslclientkey\fP
+\fI\%string\fP
+.sp
+Path to the SSL client key used to connect to remote sites.
+Empty by default.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBthrottle\fP
+storage size
+.sp
+Limits the downloading speed. It might be an absolute value or a percentage, relative to the value of the \fI\%bandwidth option\fP option. \fB0\fP means no throttling (the default). The absolute value is in bytes by default but can be specified with a unit of storage. Valid units are \(aqk\(aq, \(aqM\(aq, \(aqG\(aq.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBtimeout\fP
+time in seconds
+.sp
+Number of seconds to wait for a connection before timing out. Used in combination with \fI\%minrate option\fP option. Defaults to 30 seconds.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBusername\fP
+\fI\%string\fP
+.sp
+The username to use for connecting to repo with basic HTTP authentication. Empty by default.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBuser_agent\fP
+\fI\%string\fP
+.sp
+The User\-Agent string to include in HTTP requests sent by DNF.
+Defaults to
+.INDENT 7.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+libdnf (NAME VERSION_ID; VARIANT_ID; OS.BASEARCH)
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+where NAME, VERSION_ID and VARIANT_ID are OS identifiers read from the
+\fBos\-release(5)\fP file, and OS and BASEARCH are the canonical OS
+name and base architecture, respectively.
+Example:
+.INDENT 7.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+libdnf (Fedora 31; server; Linux.x86_64)
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.SH TYPES OF OPTIONS
+.INDENT 0.0
+.TP
+.B \fBboolean\fP
+This is a data type with only two possible values.
+.sp
+One of following options can be used: 1, 0, True, False, yes, no
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBinteger\fP
+It is a whole number that can be written without a fractional component.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBlist\fP
+It is an option that could represent one or more strings separated by space or comma characters.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBstring\fP
+It is a sequence of symbols or digits without any whitespace character.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBcolor\fP
+A string describing color and modifiers separated with a comma, for example "red,bold".
+.INDENT 7.0
+.IP \(bu 2
+Colors: black, blue, cyan, green, magenta, red, white, yellow
+.IP \(bu 2
+Modifiers: bold, blink, dim, normal, reverse, underline
+.UNINDENT
+.UNINDENT
+.SH FILES
+.INDENT 0.0
+.TP
+.B \fBCache Files\fP
+/var/cache/dnf
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBMain Configuration File\fP
+/etc/dnf/dnf.conf
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBRepository\fP
+/etc/yum.repos.d/
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \fBVariables\fP
+Any properly named file in /etc/dnf/vars is turned into a variable named after the filename (or
+overrides any of the above variables but those set from commandline). Filenames may contain only
+alphanumeric characters and underscores and be in lowercase.
+Variables are also read from /etc/yum/vars for YUM compatibility reasons.
+.UNINDENT
+.SH SEE ALSO
+.INDENT 0.0
+.IP \(bu 2
+\fBdnf(8)\fP, DNF Command Reference
+.UNINDENT
+.SH AUTHOR
+See AUTHORS in DNF source distribution.
+.SH COPYRIGHT
+2012-2022, Red Hat, Licensed under GPLv2+
+.\" Generated by docutils manpage writer.
+.
diff --git a/yum2dnf.8 b/yum2dnf.8
new file mode 100644
index 0000000..6aa9688
--- /dev/null
+++ b/yum2dnf.8
@@ -0,0 +1,717 @@
+.\" Man page generated from reStructuredText.
+.
+.
+.nr rst2man-indent-level 0
+.
+.de1 rstReportMargin
+\\$1 \\n[an-margin]
+level \\n[rst2man-indent-level]
+level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
+-
+\\n[rst2man-indent0]
+\\n[rst2man-indent1]
+\\n[rst2man-indent2]
+..
+.de1 INDENT
+.\" .rstReportMargin pre:
+. RS \\$1
+. nr rst2man-indent\\n[rst2man-indent-level] \\n[an-margin]
+. nr rst2man-indent-level +1
+.\" .rstReportMargin post:
+..
+.de UNINDENT
+. RE
+.\" indent \\n[an-margin]
+.\" old: \\n[rst2man-indent\\n[rst2man-indent-level]]
+.nr rst2man-indent-level -1
+.\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
+.in \\n[rst2man-indent\\n[rst2man-indent-level]]u
+..
+.TH "YUM2DNF" "8" "Apr 29, 2022" "4.12.0" "DNF"
+.SH NAME
+yum2dnf \- Changes in DNF compared to YUM
+.SH --SKIP-BROKEN
+.sp
+For install command:
+.sp
+The \fB\-\-skip\-broken\fP option is an alias for \fB\-\-setopt=strict=0\fP\&. Both options could be used
+with DNF to skip all unavailable packages or packages with broken dependencies given to DNF
+without raising an error causing the whole operation to fail. This behavior can be set as default
+in dnf.conf file. See strict conf option\&.
+.sp
+For upgrade command:
+.sp
+The semantics that were supposed to trigger in YUM with \fB\-\-skip\-broken\fP are now set for plain
+\fBdnf update\fP as a default. There is no need to use \fB\-\-skip\-broken\fP with the \fBdnf upgrade\fP
+command. To use only the latest versions of packages in transactions, there is the \fB\-\-best\fP
+command line switch.
+.SH UPDATE AND UPGRADE COMMANDS ARE THE SAME
+.sp
+Invoking \fBdnf update\fP or \fBdnf upgrade\fP, in all their forms, has the same
+effect in DNF, with the latter being preferred. In YUM \fByum upgrade\fP was
+exactly like \fByum \-\-obsoletes update\fP\&.
+.SH CLEAN_REQUIREMENTS_ON_REMOVE ON BY DEFAULT
+.sp
+The clean_requirements_on_remove
+switch is on by default in DNF. It can thus be confusing to compare the "remove"
+operation results between DNF and YUM as by default DNF is often going to remove
+more packages.
+.SH NO RESOLVEDEP COMMAND
+.sp
+The YUM version of this command is maintained for legacy reasons only. The user
+can just use \fBdnf provides\fP to find out what package provides a particular file.
+.SH NO DEPLIST COMMAND
+.sp
+An alternative to the YUM \fBdeplist\fP command to find out dependencies of a package
+is \fBdnf repoquery \-\-deplist\fP using repoquery command\&.
+.sp
+\fBNOTE:\fP
+.INDENT 0.0
+.INDENT 3.5
+Alternatively there is a YUM compatibility support where
+\fByum deplist\fP is alias for \fBdnf repoquery \-\-deplist\fP command
+.UNINDENT
+.UNINDENT
+.SH EXCLUDES AND REPO EXCLUDES APPLY TO ALL OPERATIONS
+.sp
+YUM only respects excludes during installs and upgrades. DNF extends this to all
+operations, among others erasing and listing. If you e.g. want to see a list of
+all installed \fBpython\-f*\fP packages but not any of the Flask packages, the
+following will work:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf \-x \(aq*flask*\(aq list installed \(aqpython\-f*\(aq
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SH THE INCLUDE OPTION HAS BEEN REMOVED
+.sp
+Inclusion of other configuration files in the main configuration file is no longer supported.
+.SH DNF PROVIDES /BIN/<FILE> IS NOT FULLY SUPPORTED
+.sp
+After \fI\%UsrMove\fP there\(aqs no
+directory \fB/bin\fP on Fedora systems and no files get installed there,
+\fB/bin\fP is only a symlink created by the \fBfilesystem\fP package to point to
+\fB/usr/bin\fP\&. Resolving the symlinks to their real path would only give the
+user a false sense that this works, while in fact provides requests using globs
+such as:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf provides /b*/<file>
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+will fail still (as they do in YUM now). To find what provides a particular
+binary, use the actual path for binaries on Fedora:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf provides /usr/bin/<file>
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Also see related Fedora bugzillas \fI\%982947\fP and \fI\%982664\fP\&.
+.SH SKIP_IF_UNAVAILABLE COULD BE ENABLED BY DEFAULT
+.sp
+In some distributions DNF is shipped with \fBskip_if_unavailable=True\fP in
+the DNF configuration file\&. The reason for the change
+is that third\-party repositories can often be unavailable. Without this setting
+in the relevant repository configuration file YUM immediately stops on a
+repository synchronization error, confusing and bothering the user.
+.sp
+See the related \fI\%Fedora bug 984483\fP\&.
+.SH OVERWRITE_GROUPS DROPPED, COMPS FUNCTIONS ACTING AS IF ALWAYS DISABLED
+.sp
+This config option has been dropped. When DNF sees several groups with the same
+group ID it merges the groups\(aq contents together.
+.SH MIRRORLIST_EXPIRE DROPPED
+.sp
+To simplify things for the user, DNF uses \fBmetadata_expire\fP for both expiring
+metadata and the mirrorlist file (which is a kind of metadata itself).
+.SH METALINK NOT RECOGNIZED IN THE MIRRORLIST REPO OPTION
+.sp
+The following part of \fByum.conf(5)\fP no longer applies for the \fBmirrorlist\fP
+option:
+.INDENT 0.0
+.INDENT 3.5
+As a special hack if the mirrorlist URL contains the word "metalink" then
+the value of mirrorlist is copied to metalink (if metalink is not set).
+.UNINDENT
+.UNINDENT
+.sp
+The relevant repository configuration files have been fixed to respect this, see
+the related \fI\%Fedora bug 948788\fP\&.
+.SH ALWAYSPROMPT DROPPED
+.sp
+Unsupported to simplify the configuration.
+.SH UPGRADE_REQUIREMENTS_ON_INSTALL DROPPED
+.sp
+Dropping this config option with blurry semantics simplifies the
+configuration. DNF behaves as if this was disabled. If the user wanted to
+upgrade everything to the latest version she\(aqd simply use \fBdnf upgrade\fP\&.
+.SH DNF HISTORY ROLLBACK CHECK DROPPED
+.sp
+Since DNF tolerates the use of other package managers, it is possible that not
+all changes to the RPMDB are stored in the history of transactions. Therefore, DNF
+does not fail if such a situation is encountered and thus the \fBforce\fP option
+is not needed anymore.
+.SH PACKAGES REPLACEMENT WITHOUT YUM SWAP
+.sp
+Time after time one needs to remove an installed package and replace it with a different one, providing the same capabilities while other packages depending on these capabilities stay installed. Without (transiently) breaking consistency of the package database this can be done by performing the remove and the install in one transaction. The common way to set up such a transaction in DNF is to use \fBdnf shell\fP or use the \fB\-\-allowerasing\fP switch.
+.sp
+E.g. say you want to replace \fBA\fP (providing \fBP\fP)  with B (also providing \fBP\fP, conflicting with \fBA\fP) without deleting \fBC\fP (which requires \fBP\fP) in the process. Use:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf \-\-allowerasing install B
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+This command is equal to \fByum swap A B\fP\&.
+.sp
+DNF provides swap command but only \fBdnf swap A B\fP syntax is supported
+.SH DEPENDENCY PROCESSING DETAILS ARE NOT SHOWN IN THE CLI
+.sp
+During its depsolving phase, YUM outputs lines similar to:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+\-\-\-> Package rubygem\-rhc.noarch 0:1.16.9\-1.fc19 will be an update
+\-\-> Processing Dependency: rubygem\-net\-ssh\-multi >= 1.2.0 for package: rubygem\-rhc\-1.16.9\-1.fc19.noarch
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+DNF does not output information like this. The technical reason is that depsolver below DNF always considers all dependencies for update candidates and the output would be very long. Secondly, even in YUM this output gets confusing very quickly especially for large transactions and so does more harm than good.
+.sp
+See the related \fI\%Fedora bug 1044999\fP\&.
+.SH DNF PROVIDES COMPLIES WITH THE YUM DOCUMENTATION OF THE COMMAND
+.sp
+When one executes:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+yum provides sandbox
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+YUM applies extra heuristics to determine what the user meant by \fBsandbox\fP, for instance it sequentially prepends entries from the \fBPATH\fP environment variable to it to see if it matches a file provided by some package. This is an undocumented behavior that DNF does not emulate. Just typically use:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf provides /usr/bin/sandbox
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+or even:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dnf provides \(aq*/sandbox\(aq
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+to obtain similar results.
+.SH BANDWIDTH LIMITING
+.sp
+DNF supports the \fBthrottle\fP and \fBbandwidth\fP options familiar from YUM.
+Contrary to YUM, when multiple downloads run simultaneously the total
+downloading speed is throttled. This was not possible in YUM since
+downloaders ran in different processes.
+.SH INSTALLONLYPKGS CONFIG OPTION
+.sp
+Compared to YUM, DNF appends list values from the \fBinstallonlypkgs\fP config option to DNF defaults, where YUM overwrites the defaults by option values.
+.SH THE USAGE OF DELTA RPM FILES
+.sp
+The boolean \fBdeltarpm\fP option controls whether delta RPM files are used. Compared to YUM, DNF does not support \fBdeltarpm_percentage\fP and instead chooses some optimal value of DRPM/RPM ratio to decide whether using deltarpm makes sense in the given case.
+.SH HANDLING .SRPM FILES AND NON-EXISTENT PACKAGES
+.sp
+DNF will terminate early with an error if a command is executed requesting an installing operation on a local \fB\&.srpm\fP file:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+$ dnf install fdn\-0.4.17\-1.fc20.src.rpm tour\-4\-6.noarch.rpm
+Error: Will not install a source rpm package (fdn\-0.4.17\-1.fc20.src).
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+The same applies for package specifications that do not match any available package.
+.sp
+YUM will only issue a warning in this case and continue installing the "tour" package. The rationale behind the result in DNF is that a program should terminate with an error if it can not fulfill the CLI command in its entirety.
+.SH PROMOTING PACKAGE TO INSTALL TO A PACKAGE THAT OBSOLETES IT
+.sp
+DNF will not magically replace a request for installing package \fBX\fP to installing package \fBY\fP if \fBY\fP obsoletes \fBX\fP\&. YUM does this if its \fBobsoletes\fP config option is enabled but the behavior is not properly documented and can be harmful.
+.sp
+See the related \fI\%Fedora bug 1096506\fP and \fI\%guidelines for renaming and obsoleting packages in Fedora\fP\&.
+.SH BEHAVIOR OF --INSTALLROOT OPTION
+.sp
+DNF offers more predictable behavior of installroot. DNF handles the path differently
+from the \fB\-\-config\fP command\-line option, where this path is always related to the host
+system (YUM combines this path with installroot). Reposdir is also handled slightly
+differently, if one path of the reposdirs exists inside of installroot, then
+repos are strictly taken from installroot (YUM tests each path from reposdir
+separately and use installroot path if existed). See the detailed description for
+\-\-installroot option.
+.SH DIFFERENT PROMPT AFTER TRANSACTION TABLE
+.sp
+DNF doesn\(aqt provide download functionality after displaying transaction table. It only asks user whether to continue with transaction or not.
+If one wants to download packages, they can use the \(aqdownload\(aq command.
+.SH LIST COMMAND SHOWS ALL REPO ALTERNATIVES
+.sp
+DNF lists all packages from all repos, which means there can be duplicates package names (with different repo name). This is due to providing users
+possibility to choose preferred repo.
+.SH YUM-LANGPACKS SUBCOMMANDS HAVE BEEN REMOVED
+.sp
+Translations became part of core DNF and it is no longer
+necessary to manage individual language packs.
+.sp
+Following sub\-commands were removed:
+.INDENT 0.0
+.IP \(bu 2
+langavailable
+.IP \(bu 2
+langinstall
+.IP \(bu 2
+langremove
+.IP \(bu 2
+langlist
+.IP \(bu 2
+langinfo
+.UNINDENT
+.TS
+center;
+|l|l|l|.
+_
+T{
+Original YUM tool
+T}	T{
+DNF command/option
+T}	T{
+Package
+T}
+_
+T{
+\fByum check\fP
+T}	T{
+dnf repoquery \fB\-\-unsatisfied\fP
+T}	T{
+\fBdnf\fP
+T}
+_
+T{
+\fByum\-langpacks\fP
+T}	T{
+T}	T{
+\fBdnf\fP
+T}
+_
+T{
+\fByum\-plugin\-aliases\fP
+T}	T{
+dnf alias
+T}	T{
+\fBdnf\fP
+T}
+_
+T{
+\fByum\-plugin\-auto\-update\-debug\-info\fP
+T}	T{
+option in \fBdebuginfo\-install.conf\fP
+T}	T{
+\fBdnf\-plugins\-core\fP
+T}
+_
+T{
+\fByum\-plugin\-changelog\fP
+T}	T{
+T}	T{
+\fBdnf\-plugins\-core\fP
+T}
+_
+T{
+\fByum\-plugin\-copr\fP
+T}	T{
+\fI\%dnf copr\fP
+T}	T{
+\fBdnf\-plugins\-core\fP
+T}
+_
+T{
+\fByum\-plugin\-fastestmirror\fP
+T}	T{
+\fBfastestmirror\fP option in \fI\%dnf.conf\fP
+T}	T{
+\fBdnf\fP
+T}
+_
+T{
+\fByum\-plugin\-fs\-snapshot\fP
+T}	T{
+T}	T{
+\fBdnf\-plugins\-extras\-snapper\fP
+T}
+_
+T{
+\fByum\-plugin\-local\fP
+T}	T{
+T}	T{
+\fBdnf\-plugins\-core\fP
+T}
+_
+T{
+\fByum\-plugin\-merge\-conf\fP
+T}	T{
+T}	T{
+\fBdnf\-plugins\-extras\-rpmconf\fP
+T}
+_
+T{
+\fByum\-plugin\-post\-transaction\-actions\fP
+T}	T{
+T}	T{
+\fBdnf\-plugins\-core\fP
+T}
+_
+T{
+\fByum\-plugin\-priorities\fP
+T}	T{
+\fBpriority\fP option in \fI\%dnf.conf\fP
+T}	T{
+\fBdnf\fP
+T}
+_
+T{
+\fByum\-plugin\-remove\-with\-leaves\fP
+T}	T{
+dnf autoremove
+T}	T{
+\fBdnf\fP
+T}
+_
+T{
+\fByum\-plugin\-show\-leaves\fP
+T}	T{
+T}	T{
+\fBdnf\-plugins\-core\fP
+T}
+_
+T{
+\fByum\-plugin\-tmprepo\fP
+T}	T{
+\fB\-\-repofrompath\fP option
+T}	T{
+\fBdnf\fP
+T}
+_
+T{
+\fByum\-plugin\-tsflags\fP
+T}	T{
+\fBtsflags\fP  option in \fI\%dnf.conf\fP
+T}	T{
+\fBdnf\fP
+T}
+_
+T{
+\fByum\-plugin\-versionlock\fP
+T}	T{
+T}	T{
+\fBpython3\-dnf\-plugin\-versionlock\fP
+T}
+_
+T{
+\fByum\-rhn\-plugin\fP
+T}	T{
+T}	T{
+\fBdnf\-plugin\-spacewalk\fP
+T}
+_
+.TE
+.sp
+Plugins that have not been ported yet:
+.sp
+\fByum\-plugin\-filter\-data\fP,
+\fByum\-plugin\-keys\fP,
+\fByum\-plugin\-list\-data\fP,
+\fByum\-plugin\-protectbase\fP,
+\fByum\-plugin\-ps\fP,
+\fByum\-plugin\-puppetverify\fP,
+\fByum\-plugin\-refresh\-updatesd\fP,
+\fByum\-plugin\-rpm\-warm\-cache\fP,
+\fByum\-plugin\-upgrade\-helper\fP,
+\fByum\-plugin\-verify\fP
+.sp
+Feel free to file an \fI\%RFE\fP for missing functionality if you need it.
+.sp
+All ported YUM tools are now implemented as DNF plugins.
+.TS
+center;
+|l|l|l|.
+_
+T{
+Original YUM tool
+T}	T{
+New DNF command
+T}	T{
+Package
+T}
+_
+T{
+\fBdebuginfo\-install\fP
+T}	T{
+\fI\%dnf debuginfo\-install\fP
+T}	T{
+\fBdnf\-plugins\-core\fP
+T}
+_
+T{
+\fBfind\-repos\-of\-install\fP
+T}	T{
+\fI\%dnf list installed\fP
+T}	T{
+\fBdnf\fP
+T}
+_
+T{
+\fBneeds\-restarting\fP
+T}	T{
+\fI\%dnf tracer\fP
+T}	T{
+\fBdnf\-plugins\-extras\-tracer\fP
+T}
+_
+T{
+\fBpackage\-cleanup\fP
+T}	T{
+dnf list,
+dnf repoquery
+T}	T{
+\fBdnf\fP, \fBdnf\-plugins\-core\fP
+T}
+_
+T{
+\fBrepoclosure\fP
+T}	T{
+\fI\%dnf repoclosure\fP
+T}	T{
+\fBdnf\-plugins\-extras\-repoclosure\fP
+T}
+_
+T{
+\fBrepodiff\fP
+T}	T{
+\fI\%dnf repodiff\fP
+T}	T{
+\fBdnf\-plugins\-core\fP
+T}
+_
+T{
+\fBrepo\-graph\fP
+T}	T{
+\fI\%dnf repograph\fP
+T}	T{
+\fBdnf\-plugins\-extras\-repograph\fP
+T}
+_
+T{
+\fBrepomanage\fP
+T}	T{
+\fI\%dnf repomanage\fP
+T}	T{
+\fBdnf\-plugins\-extras\-repomanage\fP
+T}
+_
+T{
+\fBrepoquery\fP
+T}	T{
+dnf repoquery
+T}	T{
+\fBdnf\fP
+T}
+_
+T{
+\fBreposync\fP
+T}	T{
+\fI\%dnf reposync\fP
+T}	T{
+\fBdnf\-plugins\-core\fP
+T}
+_
+T{
+\fBrepotrack\fP
+T}	T{
+\fI\%dnf download\fP \-\-resolve \-\-alldeps
+T}	T{
+\fBdnf\-plugins\-core\fP
+T}
+_
+T{
+\fByum\-builddep\fP
+T}	T{
+\fI\%dnf builddep\fP
+T}	T{
+\fBdnf\-plugins\-core\fP
+T}
+_
+T{
+\fByum\-config\-manager\fP
+T}	T{
+\fI\%dnf config\-manager\fP
+T}	T{
+\fBdnf\-plugins\-core\fP
+T}
+_
+T{
+\fByum\-debug\-dump\fP
+T}	T{
+\fI\%dnf debug\-dump\fP
+T}	T{
+\fBdnf\-plugins\-extras\-debug\fP
+T}
+_
+T{
+\fByum\-debug\-restore\fP
+T}	T{
+\fI\%dnf debug\-restore\fP
+T}	T{
+\fBdnf\-plugins\-extras\-debug\fP
+T}
+_
+T{
+\fByumdownloader\fP
+T}	T{
+\fI\%dnf download\fP
+T}	T{
+\fBdnf\-plugins\-core\fP
+T}
+_
+.TE
+.sp
+Detailed table for \fBpackage\-cleanup\fP replacement:
+.TS
+center;
+|l|l|.
+_
+T{
+\fBpackage\-cleanup \-\-dupes\fP
+T}	T{
+\fBdnf repoquery \-\-duplicates\fP
+T}
+_
+T{
+\fBpackage\-cleanup \-\-leaves\fP
+T}	T{
+\fBdnf repoquery \-\-unneeded\fP
+T}
+_
+T{
+\fBpackage\-cleanup \-\-orphans\fP
+T}	T{
+\fBdnf repoquery \-\-extras\fP
+T}
+_
+T{
+\fBpackage\-cleanup \-\-problems\fP
+T}	T{
+\fBdnf repoquery \-\-unsatisfied\fP
+T}
+_
+T{
+\fBpackage\-cleanup \-\-cleandupes\fP
+T}	T{
+\fBdnf remove \-\-duplicates\fP
+T}
+_
+T{
+\fBpackage\-cleanup \-\-oldkernels\fP
+T}	T{
+\fBdnf remove \-\-oldinstallonly\fP
+T}
+_
+T{
+\fBpackage\-cleanup \-\-oldkernels \-\-keep=2\fP
+T}	T{
+\fBdnf remove $(dnf repoquery \-\-installonly \-\-latest\-limit=\-2)\fP
+T}
+_
+.TE
+.SH YUM-UPDATEONBOOT AND YUM-CRON
+.sp
+DNF does not have a direct replacement of yum\-updateonboot and yum\-cron commands.
+However, the similar result can be achieved by \fBdnf automatic\fP command (see automatic).
+.sp
+You can either use the shortcut:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+$ systemctl enable \-\-now dnf\-automatic\-install.timer
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Or set \fBapply_updates\fP option of \fB/etc/dnf/automatic.conf\fP to True and use generic timer unit:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+$ systemctl enable \-\-now dnf\-automatic.timer
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+The timer in both cases is activated 1 hour after the system was booted up and then repetitively once every 24 hours. There is also a random delay on these timers set to 5 minutes. These values can be tweaked via \fBdnf\-automatic*.timer\fP config files located in the \fB/usr/lib/systemd/system/\fP directory.
+.SH UTILITIES THAT HAVE NOT BEEN PORTED YET
+.sp
+\fBrepo\-rss\fP,
+\fBshow\-changed\-rco\fP,
+\fBshow\-installed\fP,
+\fBverifytree\fP,
+\fByum\-groups\-manager\fP
+.sp
+Take a look at the \fI\%FAQ\fP about YUM to DNF migration. Feel free to file an \fI\%RFE\fP for missing functionality if you need it.
+.SH AUTHOR
+See AUTHORS in DNF source distribution.
+.SH COPYRIGHT
+2012-2022, Red Hat, Licensed under GPLv2+
+.\" Generated by docutils manpage writer.
+.
-- 
Gitee