Upgrading

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Can I upgrade to Fedora 21 without moving to using one of the products?: wikilink, product parameter)
 
(16 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
{{autolang|base=yes}}
 
{{autolang|base=yes}}
  
{{admon/note|Upgrading to Fedora 18 and Later| All currently supported Fedora releases, starting with Fedora 18, can be upgraded with [[FedUp]].  previous releases used PreUpgrade or the installation DVD, but users of older releases should back up their systems and perform a clean installation for best results.}}
+
== Upgrading Fedora Products ==
  
== Upgrading with FedUp ==
+
This section has some notes on upgrading to Fedora products.  Fedora 21 introduces three new products including workstation, server and cloudIf you are unfamiliar with them, refer to [[fedora.next]] page first. 
Recommended Upgrade Method (for upgrading ''to'' Fedora 18 and newer)| This is the recommended method to upgrade your Fedora system to Fedora 18 and newerNote that FedUp is only available in Fedora 17 and laterFor instructions on upgrading, refer to the [http://docs.fedoraproject.org/en-US/Fedora/19/html/Installation_Guide/ch-upgrade-x86.html| Installation Guide] or [[FedUp]]
+
  
=== Using the DVD to upgrade ===
+
=== Can I upgrade to Fedora 21 without moving to using one of the products? ===
{{admon/note | Recommended Upgrade Method (when upgrading to Fedora 17 or earlier releases) | This was the recommended method for upgrading to releases up to Fedora 17. DVD upgrades are not available for later releases; instead, please use [[FedUp]]
+
  
For upgrading to all releases up to Fedora 17, the process of using Anaconda installer to upgrade is the recommended and supported method and detailed in the [http://docs.fedoraproject.org/en-US/Fedora/17/html/Installation_Guide/index.html Fedora Installation Guide]. However, for best results when migrating from unsupported versions to newer versions, back up your user and configuration data and perform a fresh installation.
+
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 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 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 from a pre-release (alpha, beta, release candidate or other development snapshot) to the final 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 20: Line 33:
 
== Tips ==
 
== Tips ==
  
* It's a good idea to have a backup of your system before performing an upgrade. Keeping {{filename|/home}} in a separate logical volume or partition makes backing up user data easier, because the home partition can be reused when upgrading or reinstalling. This is the default from Fedora 13 onwards.
+
* Ensure you have a good backup of your data.
 
+
* Doing a clean installation and then restoring user data from backups may work better for some users. Future releases may include features to assist in this process. Refer to [[Anaconda/WorkItems#upgrade|  AnacondaWorkItems]]  for more information.
+
  
* Make sure you read the [http://docs.fedoraproject.org/en-US/Fedora/{{FedoraVersionNumber}}/html/Release_Notes/ Release Notes] carefully before attempting an upgrade.
+
* Ensure you read the [http://docs.fedoraproject.org/en-US/Fedora/{{FedoraVersionNumber}}/html/Release_Notes/ Release Notes] carefully before attempting an upgrade.
  
 
== Rawhide ==
 
== Rawhide ==

Latest revision as of 19:23, 2 January 2015

Contents

[edit] Upgrading Fedora Products

This section has some notes on upgrading to Fedora products. Fedora 21 introduces three new products including workstation, server and cloud. If you are unfamiliar with them, refer to fedora.next page first.

[edit] 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.

[edit] How do I upgrade to one of the products?

Upgrade using fedup. It has support for upgrading to a product directly.

[edit] 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.

[edit] 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.

[edit] Upgrading with FedUp

Note.png
Recommended Upgrade Method
This is the recommended method to upgrade your Fedora system. For instructions on upgrading, refer to the FedUp page.

[edit] 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.

[edit] 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.

[edit] Tips

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

[edit] 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 (medium size).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.