From Fedora Project Wiki

(Add rpm-ostree)
(make rpm-ostree more prominent)
Line 12: Line 12:
  
 
== Upgrading with DNF system upgrade plugin ==
 
== Upgrading with DNF system upgrade plugin ==
{{admon/note|Recommended Upgrade Method|This is the recommended method for Fedora upgrades.}}
+
{{admon/note|Recommended Upgrade Method|This is the recommended method for Fedora upgrades that use dnf.}}
 
For instructions on upgrading with the DNF system upgrade plugin, refer to [[DNF system upgrade|the dedicated page]].
 
For instructions on upgrading with the DNF system upgrade plugin, refer to [[DNF system upgrade|the dedicated page]].
 
== Upgrading directly using yum or DNF ==
 
{{admon/warning|Not a recommended upgrade method|This is '''NOT''' an officially recommended method for Fedora upgrades.}}
 
 
Upgrading directly from one release to the next using {{command|dnf}} (or {{command|yum}} for releases before Fedora 22) is not explicitly tested by Fedora QA and issues with it are not considered blockers for a release, but in practice it works for many users, probably due to our packaging guidelines providing detailed information on maintaining upgradability.  To learn more, refer to [[Upgrading Fedora using yum|Upgrading Fedora using dnf or yum]].
 
  
 
== Online rebases for Fedora Atomic Host via rpm-ostree ==
 
== Online rebases for Fedora Atomic Host via rpm-ostree ==
  
At the moment, Fedora uses separate OSTree repositories for each major release.  This makes
+
This path is used for the Fedora Atomic Host edition.  It's crucial to note that at the moment, Fedora uses separate OSTree repositories for each major release.  This makes
 
switching between versions more painful.  For more information, see [https://fedorahosted.org/rel-eng/ticket/6125 this ticket].
 
switching between versions more painful.  For more information, see [https://fedorahosted.org/rel-eng/ticket/6125 this ticket].
 
Let's assume you're running Fedora 22.
 
Let's assume you're running Fedora 22.
Line 36: Line 31:
 
rpm-ostree rebase fedora-23:fedora-atomic/f23/x86_64/docker-host
 
rpm-ostree rebase fedora-23:fedora-atomic/f23/x86_64/docker-host
 
</pre>
 
</pre>
 +
 +
 +
== Upgrading directly using yum or DNF ==
 +
{{admon/warning|Not a recommended upgrade method|This is '''NOT''' an officially recommended method for Fedora upgrades.}}
 +
 +
Upgrading directly from one release to the next using {{command|dnf}} (or {{command|yum}} for releases before Fedora 22) is not explicitly tested by Fedora QA and issues with it are not considered blockers for a release, but in practice it works for many users, probably due to our packaging guidelines providing detailed information on maintaining upgradability.  To learn more, refer to [[Upgrading Fedora using yum|Upgrading Fedora using dnf or yum]].
  
 
== Upgrading from a pre-release (Alpha, Beta, or other development snapshot) to the final release ==
 
== Upgrading from a pre-release (Alpha, Beta, or other development snapshot) to the final release ==

Revision as of 17:18, 22 March 2016

Upgrading Fedora Products (yum/dnf and rpm-ostree)

This section has some notes on upgrading to Fedora products. Fedora 21 introduced three new products: Workstation, Server and Cloud. If you are unfamiliar with them, you may wish to refer to Fedora.next first. Currently, Workstation, Server, and the Cloud Base image are managed via dnf. There is a Cloud Atomic image which is managed via Changes/RpmOstree and designed for containers. For more information on that, see below.

Do I need to specify or worry about products when upgrading from Fedora 21 or newer?

No, you don't need to specify a product for upgrades of Fedora 21 or later. Since the products were introduced in Fedora 21, all Fedora 21+ installs have a product identifier (even if that's 'nonproduct'). You only need to specify this when upgrading from a release older than Fedora 21 (which is no longer supported).

Upgrading with DNF system upgrade plugin

Note.png
Recommended Upgrade Method
This is the recommended method for Fedora upgrades that use dnf.

For instructions on upgrading with the DNF system upgrade plugin, refer to the dedicated page.

Online rebases for Fedora Atomic Host via rpm-ostree

This path is used for the Fedora Atomic Host edition. It's crucial to note that at the moment, Fedora uses separate OSTree repositories for each major release. This makes switching between versions more painful. For more information, see this ticket. Let's assume you're running Fedora 22. First, you'll need to add a remote for the new major version:

ostree remote add fedora-23 --set=gpg-verify=false https://dl.fedoraproject.org/pub/fedora/linux/atomic/23

Then, rebase to it:

rpm-ostree rebase fedora-23:fedora-atomic/f23/x86_64/docker-host


Upgrading directly using yum or DNF

Warning.png
Not a recommended upgrade method
This is NOT an officially recommended method for Fedora upgrades.

Upgrading directly from one release to the next using dnf (or yum for releases before Fedora 22) is not explicitly tested by Fedora QA and issues with it are not considered blockers for a release, but in practice it works for many users, probably due to our packaging guidelines providing detailed information on maintaining upgradability. To learn more, refer to Upgrading Fedora using dnf or yum.

Upgrading from a pre-release (Alpha, Beta, or other development snapshot) to the final release

If you are using a pre-release of Fedora, and want to know more about upgrading to the final release, refer to Upgrading from pre-release to final.

Tips

  • Ensure you have a good backup of your data.
  • Ensure you read the Release Notes carefully before attempting an upgrade.

Rawhide

Rawhide is a development version of Fedora that is updated daily. It is suitable for people who are developing or testing Fedora before broad public release.

Warning.png
Rawhide is not for casual use!
Packages in rawhide aren't inherently unstable, but interactions and dependencies between packages there can be unpredictable. The testing performed in release branches to prevent these conflicts isn't there in rawhide - or, more correctly, it happens in rawhide so that the release branches can benefit. Do not use Rawhide just for newer versions of a package; use it when you are an experienced user that wants to actively contribute to a stable rawhide.