1DNF-SYSTEM-UPGRADE(8) dnf-plugins-extras DNF-SYSTEM-UPGRADE(8)
2
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 dnf system-upgrade can be used to upgrade a Fedora system to a new
15 major 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 The system-upgrade command also performes additional actions necessary
20 for the upgrade of the system, for example an upgrade of groups and
21 environments.
22
24 dnf system-upgrade download --releasever VERSION [OPTIONS]
25 On modular system, also set the module_platform_id. For example, for
27 Fedora 30:
28 dnf system-upgrade download --releasever 30 [OPTIONS]
30 dnf system-upgrade reboot
32 dnf system-upgrade clean
34 dnf system-upgrade log
36 dnf system-upgrade log --number=<number>
38 dnf offline-upgrade download [OPTIONS]
40 dnf offline-upgrade reboot
42 dnf offline-upgrade clean
44 dnf offline-upgrade log
46 dnf offline-upgrade log --number=<number>
48 dnf offline-distrosync download [OPTIONS]
50 dnf offline-distrosync reboot
52 dnf offline-distrosync clean
54 dnf offline-distrosync log
56 dnf offline-distrosync log --number=<number>
58
60 download
61 Downloads everything needed to upgrade to a new major release.
62 reboot Prepares the system to perform the upgrade, and reboots to start
64 the upgrade. This can only be used after the download command
65 completes successfully.
66 clean Remove previously-downloaded data. This happens automatically at
68 the end of a successful upgrade.
69 log Used to see a list of boots during which an upgrade was
71 attempted, or show the logs from an upgrade attempt. The logs
72 for one of the boots can be shown by specifying one of the num‐
73 bers in the first column. Negative numbers can be used to number
74 the boots from last to first. For example, log --number=-1 can
75 be used to see the logs for the last upgrade attempt.
76
78 --releasever=VERSION
79 REQUIRED. The version to upgrade to. Sets $releasever in all
80 enabled repos. Usually a number, or rawhide.
81 --downloaddir=<path>
83 Redirect download of packages to provided <path>. By default,
84 packages are downloaded into (per repository created) subdirec‐
85 tories of /var/lib/dnf/system-upgrade.
86 --distro-sync
88 Behave like dnf distro-sync: always install packages from the
89 new release, even if they are older than the currently-installed
90 version. This is the default behavior.
91 --no-downgrade
93 Behave like dnf update: do not install packages from the new
94 release if they are older than what is currently installed. This
95 is the opposite of --distro-sync. If both are specified, the
96 last option will be used. The option cannot be used with the
97 ``
98 offline-distrosync` command.
99 --number
101 Applied with log subcommand will show the log specified by the
102 number.
103
105 dnf system-upgrade reboot does not create a "System Upgrade" boot item.
106 The upgrade will start regardless of which boot item is chosen.
107 The DNF_SYSTEM_UPGRADE_NO_REBOOT environment variable can be set to a
109 non-empty value to disable the actual reboot performed by sys‐
110 tem-upgrade (e.g. for testing purposes).
111 Since this is a DNF plugin, options accepted by dnf are also valid
113 here, such as --allowerasing. See dnf(8) for more information.
114 The fedup command is not provided, not even as an alias for dnf sys‐
116 tem-upgrade.
117
119 Upgrading from install media (e.g. a DVD or .iso file) currently
120 requires the user to manually set up a DNF repo and fstab entry for the
121 media.
122
124 Typical upgrade usage
125 dnf --refresh upgrade
126 dnf system-upgrade download --releasever 26
128 dnf system-upgrade reboot
130 Show logs from last upgrade attempt
132 dnf system-upgrade log --number=-1
133
135 Bugs should be filed here:
136 https://bugzilla.redhat.com/
137 For more info on filing bugs, see the Fedora Project wiki:
139 https://fedoraproject.org/wiki/How_to_file_a_bug_report
140 https://fedoraproject.org/wiki/Bugs_and_feature_requests
142 Please include /var/log/dnf.log and the output of dnf system-upgrade
144 log --number=-1 (if applicable) in your bug reports.
145 Problems with dependency solving during download are best reported to
147 the maintainers of the package(s) with the dependency problems.
148 Similarly, problems encountered on your system after the upgrade com‐
150 pletes should be reported to the maintainers of the affected compo‐
151 nents. In other words: if (for example) KDE stops working, it's best if
152 you report that to the KDE maintainers.
153
155 dnf(8), dnf.conf(5), journalctl(1).
156 Project homepage
158 https://github.com/rpm-software-management/dnf-plugins-extras
159
161 Will Woods <wwoods@redhat.com>
162 Štěpán Smetana <ssmetana@redhat.com>
164
166 See AUTHORS in your Extras DNF Plugins distribution
167
169 2020, Igor Gnatenko, Licensed under GPLv2+
1704.0.13 Dec 03, 2020 DNF-SYSTEM-UPGRADE(8)