From Fedora Project Wiki
(→Upgrading with FedUp: clarify that you can only use FedUp on F17 and later, if you're on earlier release, you have to get F17 before being able to use FedUp) |
(Try and adjust this page somewhat) |
||
| (20 intermediate revisions by 6 users not shown) | |||
| Line 1: | Line 1: | ||
{{autolang|base=yes}} | {{autolang|base=yes}} | ||
== Upgrading Fedora Products == | |||
== | This section has some notes on upgrading to Fedora products. Fedora 21 introduced three new products including workstation, server and cloud. If you are unfamiliar with them, refer to [[fedora.next]] page first. | ||
=== Do I need to specify or worry about products when upgrading from Fedora 21 to 22? === | |||
No, you don't need to specify product for Fedora 21 to Fedora 22 upgrades. Since the products were introduced in Fedora 21, all Fedora 21 installs are a type of product (even if thats 'nonproduct'). You only need to specify this going from Fedora 20 to Fedora 21. | |||
=== Can I upgrade to Fedora 21 without moving to using one of the products? === | |||
Yes. Although we are focusing on the products moving forward, upgrading from the existing official variants including Fedora Spins should continue to work. Use [[FedUp]] with the option <code>--product=nonproduct</code>. After the upgrade, you should have fedora-release-nonproduct package installed. | |||
=== How do I upgrade from Fedora 20 to Fedora 21 and to one of the products? === | |||
Upgrade using fedup. It has support for upgrading to a product directly. | |||
=== If I choose to upgrade to one of the products, can I move to another later? === | |||
Only a transition from cloud to server is supported. Use the script that is part of cloudtoserver package. If you are repurposing your system, a reinstallation is recommended for others. | |||
=== Can I move from non productized installations to one of the products and vice versa? === | |||
This should work either way but not explicitly supported at the moment. | |||
== Upgrading with FedUp == | |||
{{admon/note|Recommended Upgrade Method| This is the recommended method to upgrade your Fedora system. For instructions on upgrading, refer to [[FedUp#How_Can_I_Upgrade_My_System_with_FedUp.3F|the FedUp page]].}} | |||
== Upgrading directly using Yum == | == Upgrading directly using Yum == | ||
Upgrading directly from one release to the next using {{command|yum}} is not explicitly tested by Fedora QA and issues with it are not considered blockers for a release, but in practise 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 directly | == Upgrading directly using DNF == | ||
Like the yum method above this is not tested by Fedora QA, but should work. | |||
== Upgrading from a pre-release ( | == 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]]. | 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]]. | ||
| Line 24: | Line 41: | ||
== Tips == | == Tips == | ||
* | * Ensure you have a good backup of your data. | ||
* | * Ensure you read the [http://docs.fedoraproject.org/en-US/Fedora/{{FedoraVersionNumber}}/html/Release_Notes/ Release Notes] carefully before attempting an upgrade. | ||
== Rawhide == | == 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 a development version of Fedora that is updated daily. It is suitable for people who are developing or testing Fedora before broad public release. | ||
{{Admon/warning | 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. }} | |||
* To move from Rawhide to a stable release, refer to [[Upgrading from pre-release to final]]. | * 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]]. | * To move from a stable release to Rawhide, refer to [[Releases/Rawhide]]. | ||
Revision as of 17:28, 27 May 2015
Upgrading Fedora Products
This section has some notes on upgrading to Fedora products. Fedora 21 introduced three new products including workstation, server and cloud. If you are unfamiliar with them, refer to fedora.next page first.
Do I need to specify or worry about products when upgrading from Fedora 21 to 22?
No, you don't need to specify product for Fedora 21 to Fedora 22 upgrades. Since the products were introduced in Fedora 21, all Fedora 21 installs are a type of product (even if thats 'nonproduct'). You only need to specify this going from Fedora 20 to Fedora 21.
Can I upgrade to Fedora 21 without moving to using one of the products?
Yes. Although we are focusing on the products moving forward, upgrading from the existing official variants including Fedora Spins should continue to work. Use FedUp with the option --product=nonproduct. After the upgrade, you should have fedora-release-nonproduct package installed.
How do I upgrade from Fedora 20 to Fedora 21 and to one of the products?
Upgrade using fedup. It has support for upgrading to a product directly.
If I choose to upgrade to one of the products, can I move to another later?
Only a transition from cloud to server is supported. Use the script that is part of cloudtoserver package. If you are repurposing your system, a reinstallation is recommended for others.
Can I move from non productized installations to one of the products and vice versa?
This should work either way but not explicitly supported at the moment.
Upgrading with FedUp
Recommended Upgrade Method
This is the recommended method to upgrade your Fedora system. For instructions on upgrading, refer to the FedUp page.
This is the recommended method to upgrade your Fedora system. For instructions on upgrading, refer to the FedUp page.
Upgrading directly using Yum
Upgrading directly from one release to the next using yum is not explicitly tested by Fedora QA and issues with it are not considered blockers for a release, but in practise 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 directly using DNF
Like the yum method above this is not tested by Fedora QA, but should work.
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.