From Fedora Project Wiki
No edit summary |
No edit summary |
||
Line 3: | Line 3: | ||
|actions= | |actions= | ||
# Perform an installation of the stable release (e.g. {{FedoraVersion|long}}) with default partitioning (no less than 200MB for <code>/boot</code>). | # Perform an installation of the stable release (e.g. {{FedoraVersion|long}}) with default partitioning (no less than 200MB for <code>/boot</code>). | ||
# | # On this system install another two kernels to model real-world users from repositories (stable and updates repo) or download from Koji: http://koji.fedoraproject.org/koji/packageinfo?packageID=8 | ||
# Install the newest available version of {{package|preupgrade}}. | # Install the newest available version of {{package|preupgrade}}. | ||
# Run <code>preupgrade</code> from a command prompt or the ''Run Application'' dialog. Provide the requested password for root authorization. | # Run <code>preupgrade</code> from a command prompt or the ''Run Application'' dialog. Provide the requested password for root authorization. |
Revision as of 09:15, 17 November 2009
Description
This case tests upgrading a Fedora system from the current stable release (Fedora 41) to the development release (Rawhide/Fedora 42) using PreUpgrade.
How to test
- Perform an installation of the stable release (e.g. Fedora 41) with default partitioning (no less than 200MB for
/boot
). - On this system install another two kernels to model real-world users from repositories (stable and updates repo) or download from Koji: http://koji.fedoraproject.org/koji/packageinfo?packageID=8
- Install the newest available version of
preupgrade
. - Run
preupgrade
from a command prompt or the Run Application dialog. Provide the requested password for root authorization. - On the "Choose desired release" screen, enable "unstable test releases".
- Choose Rawhide from the list of available upgrade targets.
- Click Apply.
- When the process completes, click Reboot.
- The system should reboot, perform the upgrade, and reboot into the new system automatically.
- Log in to upgraded system, open a terminal, file browser, or other system applications.
Expected Results
- The upgrade should complete and reboot without user assistance.
- The system should be upgraded to new version without error.
- The opened terminal, file browser, or other system applications should display and work correctly.