From Fedora Project Wiki
No edit summary |
(unfuck the page (srsly guys, you confused the hell out of Phoronix. stopit. 99% of people don't know what an Atomic host is. Removing all reference to straight DNF upgrades is also not helpful, it is better to address them head on.)) |
||
| Line 1: | Line 1: | ||
{{autolang|base=yes}} | {{autolang|base=yes}} | ||
== Upgrading with DNF system upgrade plugin == | == Upgrading with DNF system upgrade plugin == | ||
{{admon/note|Recommended Upgrade Method|This is the recommended method for upgrades of all Fedora installs except Fedora Atomic Host.}} | |||
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]]. | ||
== Online rebases for Fedora Atomic Host via rpm-ostree == | == Online rebases for Fedora Atomic Host via rpm-ostree == | ||
{{admon/note|Recommended Upgrade Method for Atomic Host|This is the recommended method for upgrades of Fedora Atomic Host installations.}} | |||
For instructions on upgrading Fedora Atomic Host installations between Fedora releases, refer to [[Atomic Host upgrade|the dedicated page]]. | |||
This | == Online upgrade with pure DNF == | ||
{{admon/warning|Not a recommended upgrade method|This is '''NOT''' an officially recommended method for Fedora upgrades.}} | |||
Upgrading from one release to the next using {{command|dnf}} directly, without the DNF system upgrade plugin, 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. To learn more, refer to [[Upgrading Fedora using yum|Upgrading Fedora using dnf]]. | |||
== 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 00:45, 30 March 2016
Upgrading with DNF system upgrade plugin
Recommended Upgrade Method
This is the recommended method for upgrades of all Fedora installs except Fedora Atomic Host.
This is the recommended method for upgrades of all Fedora installs except Fedora Atomic Host.
For instructions on upgrading with the DNF system upgrade plugin, refer to the dedicated page.
Online rebases for Fedora Atomic Host via rpm-ostree
Recommended Upgrade Method for Atomic Host
This is the recommended method for upgrades of Fedora Atomic Host installations.
This is the recommended method for upgrades of Fedora Atomic Host installations.
For instructions on upgrading Fedora Atomic Host installations between Fedora releases, refer to the dedicated page.
Online upgrade with pure DNF
Not a recommended upgrade method
This is NOT an officially recommended method for Fedora upgrades.
This is NOT an officially recommended method for Fedora upgrades.
Upgrading from one release to the next using dnf directly, without the DNF system upgrade plugin, 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. To learn more, refer to Upgrading Fedora using dnf.
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.
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.
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.
- To move from Rawhide to a stable release, refer to Upgrading from pre-release to final.
- To move from a stable release to Rawhide, refer to Releases/Rawhide.