dnf4-system-upgrade - DNF system-upgrade Plugin

       See AUTHORS in your Core DNF Plugins distribution

       Will Woods <wwoods@redhat.com>

       Štěpán Smetana <ssmetana@redhat.com>

       Upgrading  from  install media (e.g. a DVD or .iso file) currently requires the user to manually set up a
       DNF repo and fstab entry for the media.

       2014, Red Hat, Licensed under GPLv2+

4.10.1                                            Jun 20, 2025                            DNF4-SYSTEM-UPGRADE(8)

       DNF    system-upgrades   plugin   provides   three   commands:   system-upgrade,   offline-upgrade,   and
       offline-distrosync.  Only  system-upgrade  command  requires  increase  of  distribution  major   version
       (--releasever) compared to installed version.

       dnfsystem-upgrade  is  a recommended way to upgrade a system to a new major release.  It replaces fedup
       (the old Fedora Upgrade tool). Before you  proceed  ensure  that  your  system  is  fully  upgraded  (dnf--refreshupgrade).

       The system-upgrade command also performes additional actions necessary for the upgrade of the system, for
       example an upgrade of groups and environments.

Typicalupgradeusagednf--refreshupgradednfsystem-upgradedownload--releasever26dnfsystem-upgraderebootShowlogsfromlastupgradeattemptdnfsystem-upgradelog--number=-1

       dnf4-system-upgrade - DNF system-upgrade Plugin

dnfsystem-upgradereboot does not create a “System Upgrade” boot item. The upgrade will start regardless
       of which boot item is chosen.

       The  DNF_SYSTEM_UPGRADE_NO_REBOOT  environment  variable  can  be set to a non-empty value to disable the
       actual reboot performed by system-upgrade (e.g. for testing purposes).

       Since this is a DNF plugin, options accepted by dnf are also valid here,  such  as  --allowerasing.   See
       dnf(8) for more information.

       The fedup command is not provided, not even as an alias for dnfsystem-upgrade.

--releasever=VERSION
              REQUIRED.  The  version to upgrade to. Sets $releasever in all enabled repos. Usually a number, or
              rawhide.

       --downloaddir=<path>
              Redirect download of packages to provided <path>. By default, packages are  downloaded  into  (per
              repository created) subdirectories of /var/lib/dnf/system-upgrade.

       --distro-sync
              Behave  like dnfdistro-sync: always install packages from the new release, even if they are older
              than the currently-installed version. This is the default behavior.

       --no-downgrade
              Behave like dnfupdate: do not install packages from the new release if they are older  than  what
              is  currently  installed.  This  is the opposite of --distro-sync. If both are specified, the last
              option will be used. The option cannot be used with the offline-distrosync command.

       --poweroff
              When applied with the reboot subcommand, the system will power off after upgrades  are  completed,
              instead of restarting.

       --number
              Applied with log subcommand will show the log specified by the number.

       Bugs should be filed here:
          https://bugzilla.redhat.com/

       For more info on filing bugs, see the Fedora Project wiki:
          https://fedoraproject.org/wiki/How_to_file_a_bug_reporthttps://fedoraproject.org/wiki/Bugs_and_feature_requests

       Please include /var/log/dnf.log and the output of dnfsystem-upgradelog--number=-1 (if  applicable)  in
       your bug reports.

       Problems  with  dependency solving during download are best reported to the maintainers of the package(s)
       with the dependency problems.

       Similarly, problems encountered on your system after the upgrade completes  should  be  reported  to  the
       maintainers  of the affected components. In other words: if (for example) KDE stops working, it’s best if
       you report that to the KDE maintainers.

dnf(8), dnf.conf(5), journalctl(1).

   Projecthomepagehttps://github.com/rpm-software-management/dnf-plugins-core

download
              Downloads everything needed to upgrade to a new major release.

       reboot Prepares  the  system  to perform the upgrade, and reboots to start the upgrade.  This can only be
              used after the download command completes successfully.

       clean  Remove previously-downloaded data. This happens automatically at the end of a successful upgrade.

       log    Used to see a list of boots during which an upgrade was  attempted,  or  show  the  logs  from  an
              upgrade  attempt.  The  logs for one of the boots can be shown by specifying one of the numbers in
              the first column. Negative numbers can be used to  number  the  boots  from  last  to  first.  For
              example, log--number=-1 can be used to see the logs for the last upgrade attempt.

dnfsystem-upgradedownload--releaseverVERSION[OPTIONS]dnfsystem-upgraderebootdnfsystem-upgradereboot--poweroffdnfsystem-upgradecleandnfsystem-upgradelogdnfsystem-upgradelog--number=<number>dnfoffline-upgradedownload[OPTIONS]dnfoffline-upgraderebootdnfoffline-upgradereboot--poweroffdnfoffline-upgradecleandnfoffline-upgradelogdnfoffline-upgradelog--number=<number>dnfoffline-distrosyncdownload[OPTIONS]dnfoffline-distrosyncrebootdnfoffline-distrosyncreboot--poweroffdnfoffline-distrosynccleandnfoffline-distrosynclogdnfoffline-distrosynclog--number=<number>