From Fedora Project Wiki

No edit summary
No edit summary
Line 9: Line 9:
# Choose ''Rawhide'' from the list of available upgrade targets.
# Choose ''Rawhide'' from the list of available upgrade targets.
# Click ''Apply''.
# Click ''Apply''.
# A Window may pop up warning how much more free space of /boot is required for completion during the process, see [http://fedoraproject.org/wiki/How_to_use_PreUpgrade#Troubleshooting how to free more space in /boot].   
# A Window may pop up warning how much more free space of /boot is required for completion during the process, see [http://fedoraproject.org/wiki/How_to_use_PreUpgrade#Troubleshooting methods to free more space in /boot].   
# When the process completes, click ''Reboot''.
# When the process completes, click ''Reboot''.
# The system should reboot, perform the upgrade, and reboot into the new system automatically.
# The system should reboot, perform the upgrade, and reboot into the new system automatically.

Revision as of 09:36, 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

  1. Perform an installation of the stable release (e.g. Fedora 41) with default partitioning (no less than 250MB for /boot).
  2. On this system install another two kernels to model real-world users from repositories (stable and updates repo) or from Koji.
  3. Install the newest available version of preupgrade.
  4. Run preupgrade from a command prompt or the Run Application dialog. Provide the requested password for root authorization.
  5. On the "Choose desired release" screen, enable "unstable test releases".
  6. Choose Rawhide from the list of available upgrade targets.
  7. Click Apply.
  8. A Window may pop up warning how much more free space of /boot is required for completion during the process, see methods to free more space in /boot.
  9. When the process completes, click Reboot.
  10. The system should reboot, perform the upgrade, and reboot into the new system automatically.
  11. Log in to upgraded system, open a terminal, file browser, or other system applications.

Expected Results

  1. The upgrade should complete and reboot without user assistance.
  2. The system should be upgraded to new version without error.
  3. The opened terminal, file browser, or other system applications should display and work correctly.