1DNF-SYSTEM-UPGRADE(8) dnf-plugins-extras DNF-SYSTEM-UPGRADE(8)
2
3
4
6 dnf-system-upgrade - DNF system-upgrade Plugin
7
9 DNF system-upgrades plugin provides three commands: system-upgrade,
10 offline-upgrade, and offline-distrosync. Only system-upgrade command
11 requires increase of distribution major version (--releasever) compared
12 to installed version.
13
14 dnf system-upgrade can be used to upgrade a Fedora system to a new ma‐
15 jor release. It replaces fedup (the old Fedora Upgrade tool). Before
16 you proceed ensure that your system is fully upgraded (dnf --refresh
17 upgrade).
18
19 The system-upgrade command also performes additional actions necessary
20 for the upgrade of the system, for example an upgrade of groups and en‐
21 vironments.
22
24 dnf system-upgrade download --releasever VERSION [OPTIONS]
25
26 dnf system-upgrade reboot
27
28 dnf system-upgrade clean
29
30 dnf system-upgrade log
31
32 dnf system-upgrade log --number=<number>
33
34 dnf offline-upgrade download [OPTIONS]
35
36 dnf offline-upgrade reboot
37
38 dnf offline-upgrade clean
39
40 dnf offline-upgrade log
41
42 dnf offline-upgrade log --number=<number>
43
44 dnf offline-distrosync download [OPTIONS]
45
46 dnf offline-distrosync reboot
47
48 dnf offline-distrosync clean
49
50 dnf offline-distrosync log
51
52 dnf offline-distrosync log --number=<number>
53
55 download
56 Downloads everything needed to upgrade to a new major release.
57
58 reboot Prepares the system to perform the upgrade, and reboots to start
59 the upgrade. This can only be used after the download command
60 completes successfully.
61
62 clean Remove previously-downloaded data. This happens automatically at
63 the end of a successful upgrade.
64
65 log Used to see a list of boots during which an upgrade was at‐
66 tempted, or show the logs from an upgrade attempt. The logs for
67 one of the boots can be shown by specifying one of the numbers
68 in the first column. Negative numbers can be used to number the
69 boots from last to first. For example, log --number=-1 can be
70 used to see the logs for the last upgrade attempt.
71
73 --releasever=VERSION
74 REQUIRED. The version to upgrade to. Sets $releasever in all en‐
75 abled repos. Usually a number, or rawhide.
76
77 --downloaddir=<path>
78 Redirect download of packages to provided <path>. By default,
79 packages are downloaded into (per repository created) subdirec‐
80 tories of /var/lib/dnf/system-upgrade.
81
82 --distro-sync
83 Behave like dnf distro-sync: always install packages from the
84 new release, even if they are older than the currently-installed
85 version. This is the default behavior.
86
87 --no-downgrade
88 Behave like dnf update: do not install packages from the new re‐
89 lease if they are older than what is currently installed. This
90 is the opposite of --distro-sync. If both are specified, the
91 last option will be used. The option cannot be used with the
92 offline-distrosync command.
93
94 --number
95 Applied with log subcommand will show the log specified by the
96 number.
97
99 dnf system-upgrade reboot does not create a "System Upgrade" boot item.
100 The upgrade will start regardless of which boot item is chosen.
101
102 The DNF_SYSTEM_UPGRADE_NO_REBOOT environment variable can be set to a
103 non-empty value to disable the actual reboot performed by system-up‐
104 grade (e.g. for testing purposes).
105
106 Since this is a DNF plugin, options accepted by dnf are also valid
107 here, such as --allowerasing. See dnf(8) for more information.
108
109 The fedup command is not provided, not even as an alias for dnf sys‐
110 tem-upgrade.
111
113 Upgrading from install media (e.g. a DVD or .iso file) currently re‐
114 quires the user to manually set up a DNF repo and fstab entry for the
115 media.
116
118 Typical upgrade usage
119 dnf --refresh upgrade
120
121 dnf system-upgrade download --releasever 26
122
123 dnf system-upgrade reboot
124
125 Show logs from last upgrade attempt
126 dnf system-upgrade log --number=-1
127
129 Bugs should be filed here:
130 https://bugzilla.redhat.com/
131
132 For more info on filing bugs, see the Fedora Project wiki:
133 https://fedoraproject.org/wiki/How_to_file_a_bug_report
134
135 https://fedoraproject.org/wiki/Bugs_and_feature_requests
136
137 Please include /var/log/dnf.log and the output of dnf system-upgrade
138 log --number=-1 (if applicable) in your bug reports.
139
140 Problems with dependency solving during download are best reported to
141 the maintainers of the package(s) with the dependency problems.
142
143 Similarly, problems encountered on your system after the upgrade com‐
144 pletes should be reported to the maintainers of the affected compo‐
145 nents. In other words: if (for example) KDE stops working, it's best if
146 you report that to the KDE maintainers.
147
149 dnf(8), dnf.conf(5), journalctl(1).
150
151 Project homepage
152 https://github.com/rpm-software-management/dnf-plugins-extras
153
155 Will Woods <wwoods@redhat.com>
156
157 Štěpán Smetana <ssmetana@redhat.com>
158
160 See AUTHORS in your Extras DNF Plugins distribution
161
163 2022, Igor Gnatenko, Licensed under GPLv2+
164
165
166
167
1684.0.16 Mar 14, 2022 DNF-SYSTEM-UPGRADE(8)