From Fedora Project Wiki

(Adjust phrasing of low disk dialog ... it should not prompt user)
No edit summary
Line 5: Line 5:
# Install the newest available version of {{package|preupgrade}}.
# Install the newest available version of {{package|preupgrade}}.
# Run {{command|preupgrade}} from a command prompt or the ''Run Application'' dialog. Provide the requested password for root authorization.
# Run {{command|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".
# On the ''Choose desired release'' screen, enable ''unstable test releases''.
# Choose ''Rawhide'' from the list of available upgrade targets, then click ''Apply''.
# Choose ''Rawhide'' from the list of available upgrade targets, then click ''Apply''.
# When the process completes, click ''Reboot''.
# When the process completes, click ''Reboot''.

Revision as of 07:07, 7 January 2010

Description

This case tests upgrading a Fedora system from the previous stable release (Fedora 40) to the development release (Rawhide/Fedora 42) using PreUpgrade.


How to test

  1. Perform an installation of the previous stable release (e.g. Fedora 40) with default partitioning (no less than 200MB for /boot). Ensure there are only 1 kernel installed on the system.
  2. Install the newest available version of preupgrade.
  3. Run preupgrade from a command prompt or the Run Application dialog. Provide the requested password for root authorization.
  4. On the Choose desired release screen, enable unstable test releases.
  5. Choose Rawhide from the list of available upgrade targets, then click Apply.
  6. When the process completes, click Reboot.
  7. The system should reboot, perform the upgrade, and reboot into the new system automatically.
  8. Log in to upgraded system, open a terminal, file browser, or other system applications.

Expected Results

  1. The preupgrade utility will run to completion, without error.
  2. The upgrade should complete and reboot without user assistance.
  3. The user is not prompted to address low disk space in /boot
  4. The system should be upgraded to new version without error.
  5. The opened terminal, file browser, or other system applications should display and work correctly.