| 1 |
.\" Man page generated from reStructuredText. |
| 2 |
. |
| 3 |
. |
| 4 |
.nr rst2man-indent-level 0 |
| 5 |
. |
| 6 |
.de1 rstReportMargin |
| 7 |
\\$1 \\n[an-margin] |
| 8 |
level \\n[rst2man-indent-level] |
| 9 |
level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] |
| 10 |
- |
| 11 |
\\n[rst2man-indent0] |
| 12 |
\\n[rst2man-indent1] |
| 13 |
\\n[rst2man-indent2] |
| 14 |
.. |
| 15 |
.de1 INDENT |
| 16 |
.\" .rstReportMargin pre: |
| 17 |
. RS \\$1 |
| 18 |
. nr rst2man-indent\\n[rst2man-indent-level] \\n[an-margin] |
| 19 |
. nr rst2man-indent-level +1 |
| 20 |
.\" .rstReportMargin post: |
| 21 |
.. |
| 22 |
.de UNINDENT |
| 23 |
. RE |
| 24 |
.\" indent \\n[an-margin] |
| 25 |
.\" old: \\n[rst2man-indent\\n[rst2man-indent-level]] |
| 26 |
.nr rst2man-indent-level -1 |
| 27 |
.\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] |
| 28 |
.in \\n[rst2man-indent\\n[rst2man-indent-level]]u |
| 29 |
.. |
| 30 |
.TH "DNF4-SYSTEM-UPGRADE" "8" "Sep 27, 2025" "4.10.1" "dnf-plugins-core" |
| 31 |
.SH NAME |
| 32 |
dnf4-system-upgrade \- DNF system-upgrade Plugin |
| 33 |
.SH DESCRIPTION |
| 34 |
.sp |
| 35 |
DNF system\-upgrades plugin provides three commands: \fBsystem\-upgrade\fP, \fBoffline\-upgrade\fP, and |
| 36 |
\fBoffline\-distrosync\fP\&. Only \fBsystem\-upgrade\fP command requires increase of distribution major |
| 37 |
version (\fB\-\-releasever\fP) compared to installed version. |
| 38 |
.sp |
| 39 |
\fBdnf system\-upgrade\fP is a recommended way to upgrade a system to a new major release. |
| 40 |
It replaces fedup (the old Fedora Upgrade tool). Before you proceed ensure that your system |
| 41 |
is fully upgraded (\fBdnf \-\-refresh upgrade\fP). |
| 42 |
.sp |
| 43 |
The \fBsystem\-upgrade\fP command also performes additional actions necessary for the upgrade of the |
| 44 |
system, for example an upgrade of groups and environments. |
| 45 |
.SH SYNOPSIS |
| 46 |
.sp |
| 47 |
\fBdnf system\-upgrade download \-\-releasever VERSION [OPTIONS]\fP |
| 48 |
.sp |
| 49 |
\fBdnf system\-upgrade reboot\fP |
| 50 |
.sp |
| 51 |
\fBdnf system\-upgrade reboot \-\-poweroff\fP |
| 52 |
.sp |
| 53 |
\fBdnf system\-upgrade clean\fP |
| 54 |
.sp |
| 55 |
\fBdnf system\-upgrade log\fP |
| 56 |
.sp |
| 57 |
\fBdnf system\-upgrade log \-\-number=<number>\fP |
| 58 |
.sp |
| 59 |
\fBdnf offline\-upgrade download [OPTIONS]\fP |
| 60 |
.sp |
| 61 |
\fBdnf offline\-upgrade reboot\fP |
| 62 |
.sp |
| 63 |
\fBdnf offline\-upgrade reboot \-\-poweroff\fP |
| 64 |
.sp |
| 65 |
\fBdnf offline\-upgrade clean\fP |
| 66 |
.sp |
| 67 |
\fBdnf offline\-upgrade log\fP |
| 68 |
.sp |
| 69 |
\fBdnf offline\-upgrade log \-\-number=<number>\fP |
| 70 |
.sp |
| 71 |
\fBdnf offline\-distrosync download [OPTIONS]\fP |
| 72 |
.sp |
| 73 |
\fBdnf offline\-distrosync reboot\fP |
| 74 |
.sp |
| 75 |
\fBdnf offline\-distrosync reboot \-\-poweroff\fP |
| 76 |
.sp |
| 77 |
\fBdnf offline\-distrosync clean\fP |
| 78 |
.sp |
| 79 |
\fBdnf offline\-distrosync log\fP |
| 80 |
.sp |
| 81 |
\fBdnf offline\-distrosync log \-\-number=<number>\fP |
| 82 |
.SH SUBCOMMANDS |
| 83 |
.INDENT 0.0 |
| 84 |
.TP |
| 85 |
.B \fBdownload\fP |
| 86 |
Downloads everything needed to upgrade to a new major release. |
| 87 |
.TP |
| 88 |
.B \fBreboot\fP |
| 89 |
Prepares the system to perform the upgrade, and reboots to start the upgrade. |
| 90 |
This can only be used after the \fBdownload\fP command completes successfully. |
| 91 |
.TP |
| 92 |
.B \fBclean\fP |
| 93 |
Remove previously\-downloaded data. This happens automatically at the end of |
| 94 |
a successful upgrade. |
| 95 |
.TP |
| 96 |
.B \fBlog\fP |
| 97 |
Used to see a list of boots during which an upgrade was attempted, or show |
| 98 |
the logs from an upgrade attempt. The logs for one of the boots can be shown |
| 99 |
by specifying one of the numbers in the first column. Negative numbers can |
| 100 |
be used to number the boots from last to first. For example, \fBlog \-\-number=\-1\fP can |
| 101 |
be used to see the logs for the last upgrade attempt. |
| 102 |
.UNINDENT |
| 103 |
.SH OPTIONS |
| 104 |
.INDENT 0.0 |
| 105 |
.TP |
| 106 |
.B \fB\-\-releasever=VERSION\fP |
| 107 |
REQUIRED. The version to upgrade to. Sets \fB$releasever\fP in all enabled |
| 108 |
repos. Usually a number, or \fBrawhide\fP\&. |
| 109 |
.TP |
| 110 |
.B \fB\-\-downloaddir=<path>\fP |
| 111 |
Redirect download of packages to provided \fB<path>\fP\&. By default, packages |
| 112 |
are downloaded into (per repository created) subdirectories of |
| 113 |
/var/lib/dnf/system\-upgrade. |
| 114 |
.TP |
| 115 |
.B \fB\-\-distro\-sync\fP |
| 116 |
Behave like \fBdnf distro\-sync\fP: always install packages from the new |
| 117 |
release, even if they are older than the currently\-installed version. This |
| 118 |
is the default behavior. |
| 119 |
.TP |
| 120 |
.B \fB\-\-no\-downgrade\fP |
| 121 |
Behave like \fBdnf update\fP: do not install packages from the new release |
| 122 |
if they are older than what is currently installed. This is the opposite of |
| 123 |
\fB\-\-distro\-sync\fP\&. If both are specified, the last option will be used. The option cannot be |
| 124 |
used with the \fBoffline\-distrosync\fP command. |
| 125 |
.TP |
| 126 |
.B \fB\-\-poweroff\fP |
| 127 |
When applied with the \fBreboot\fP subcommand, the system will power off after |
| 128 |
upgrades are completed, instead of restarting. |
| 129 |
.TP |
| 130 |
.B \fB\-\-number\fP |
| 131 |
Applied with \fBlog\fP subcommand will show the log specified by the number. |
| 132 |
.UNINDENT |
| 133 |
.SH NOTES |
| 134 |
.sp |
| 135 |
\fBdnf system\-upgrade reboot\fP does not create a “System Upgrade” boot item. The |
| 136 |
upgrade will start regardless of which boot item is chosen. |
| 137 |
.sp |
| 138 |
The \fBDNF_SYSTEM_UPGRADE_NO_REBOOT\fP environment variable can be set to a |
| 139 |
non\-empty value to disable the actual reboot performed by \fBsystem\-upgrade\fP |
| 140 |
(e.g. for testing purposes). |
| 141 |
.sp |
| 142 |
Since this is a DNF plugin, options accepted by \fBdnf\fP are also valid here, |
| 143 |
such as \fB\-\-allowerasing\fP\&. |
| 144 |
See \fBdnf(8)\fP for more information. |
| 145 |
.sp |
| 146 |
The \fBfedup\fP command is not provided, not even as an alias for |
| 147 |
\fBdnf system\-upgrade\fP\&. |
| 148 |
.SH BUGS |
| 149 |
.sp |
| 150 |
Upgrading from install media (e.g. a DVD or .iso file) currently requires the |
| 151 |
user to manually set up a DNF repo and fstab entry for the media. |
| 152 |
.SH EXAMPLES |
| 153 |
.SS Typical upgrade usage |
| 154 |
.sp |
| 155 |
\fBdnf \-\-refresh upgrade\fP |
| 156 |
.sp |
| 157 |
\fBdnf system\-upgrade download \-\-releasever 26\fP |
| 158 |
.sp |
| 159 |
\fBdnf system\-upgrade reboot\fP |
| 160 |
.SS Show logs from last upgrade attempt |
| 161 |
.sp |
| 162 |
\fBdnf system\-upgrade log \-\-number=\-1\fP |
| 163 |
.SH REPORTING BUGS |
| 164 |
.sp |
| 165 |
Bugs should be filed here: |
| 166 |
.INDENT 0.0 |
| 167 |
.INDENT 3.5 |
| 168 |
\X'tty: link https://bugzilla.redhat.com/'\fI\%https://bugzilla.redhat.com/\fP\X'tty: link' |
| 169 |
.UNINDENT |
| 170 |
.UNINDENT |
| 171 |
.sp |
| 172 |
For more info on filing bugs, see the Fedora Project wiki: |
| 173 |
.INDENT 0.0 |
| 174 |
.INDENT 3.5 |
| 175 |
\X'tty: link https://fedoraproject.org/wiki/How_to_file_a_bug_report'\fI\%https://fedoraproject.org/wiki/How_to_file_a_bug_report\fP\X'tty: link' |
| 176 |
.sp |
| 177 |
\X'tty: link https://fedoraproject.org/wiki/Bugs_and_feature_requests'\fI\%https://fedoraproject.org/wiki/Bugs_and_feature_requests\fP\X'tty: link' |
| 178 |
.UNINDENT |
| 179 |
.UNINDENT |
| 180 |
.sp |
| 181 |
Please include \fB/var/log/dnf.log\fP and the output of |
| 182 |
\fBdnf system\-upgrade log \-\-number=\-1\fP (if applicable) in your bug reports. |
| 183 |
.sp |
| 184 |
Problems with dependency solving during download are best reported to the |
| 185 |
maintainers of the package(s) with the dependency problems. |
| 186 |
.sp |
| 187 |
Similarly, problems encountered on your system after the upgrade completes |
| 188 |
should be reported to the maintainers of the affected components. In other |
| 189 |
words: if (for example) KDE stops working, it’s best if you report that to |
| 190 |
the KDE maintainers. |
| 191 |
.SH SEE ALSO |
| 192 |
.sp |
| 193 |
\fBdnf(8)\fP, |
| 194 |
\fBdnf.conf(5)\fP, |
| 195 |
\fBjournalctl(1)\fP\&. |
| 196 |
.SS Project homepage |
| 197 |
.sp |
| 198 |
\X'tty: link https://github.com/rpm-software-management/dnf-plugins-core'\fI\%https://github.com/rpm\-software\-management/dnf\-plugins\-core\fP\X'tty: link' |
| 199 |
.SH AUTHORS |
| 200 |
.sp |
| 201 |
Will Woods <\X'tty: link mailto:[email protected]'\fI\%[email protected]\fP\X'tty: link'> |
| 202 |
.sp |
| 203 |
Štěpán Smetana <\X'tty: link mailto:[email protected]'\fI\%[email protected]\fP\X'tty: link'> |
| 204 |
.SH AUTHOR |
| 205 |
See AUTHORS in your Core DNF Plugins distribution |
| 206 |
.SH COPYRIGHT |
| 207 |
2014, Red Hat, Licensed under GPLv2+ |
| 208 |
.\" Generated by docutils manpage writer. |
| 209 |
. |