From Fedora Project Wiki
No edit summary |
(fix url, remove Beta) |
||
Line 9: | Line 9: | ||
#* Be sure to get the latest release, this may involve enabling updates-testing (put <code>--enablerepo=updates-testing</code> between {{command|yum}} and {{command|install}} on the command line) | #* Be sure to get the latest release, this may involve enabling updates-testing (put <code>--enablerepo=updates-testing</code> between {{command|yum}} and {{command|install}} on the command line) | ||
#* '''2013-01-03: Make sure you have at least fedup-0.7.2-1.fc17.''' | #* '''2013-01-03: Make sure you have at least fedup-0.7.2-1.fc17.''' | ||
# Find the URL of the branched TC or RC or updates.img under test. This URL should be of the form <nowiki>http://dl.fedoraproject.org/pub/alt/stage/18 | # Find the URL of the branched TC or RC or updates.img under test. This URL should be of the form <nowiki>http://dl.fedoraproject.org/pub/alt/stage/18-<compose>/Fedora/<arch>/os</nowiki>. The URL needs to point to the initrd.img and vmlinuz, but not necessarily all rpm packages. | ||
#* < | #* <compose> is the name of the compose under test (TC1, RC2 etc.) | ||
#* <arch> is the name of the arch running on the install to be upgraded (i386, x86_64 ...) | #* <arch> is the name of the arch running on the install to be upgraded (i386, x86_64 ...) | ||
# Start the upgrade prep by executing following command | # Start the upgrade prep by executing following command | ||
Line 16: | Line 16: | ||
#* <URL> is the location found in the previous step | #* <URL> is the location found in the previous step | ||
# To utilize a local mirror for the new arch Start the upgrade prep by executing following command | # To utilize a local mirror for the new arch Start the upgrade prep by executing following command | ||
#* sudo fedup-cli --network 18 --debuglog fedupdebug.log --instrepo <URL> --disablerepo=fedora --repourl fedora-local=<URL-LOCAL> | #* {{command|1=sudo fedup-cli --network 18 --debuglog fedupdebug.log --instrepo <URL> --disablerepo=fedora --repourl fedora-local=<URL-LOCAL>}} | ||
#* <URL-LOCAL> is the location of a local fedora repo if needed for faster response speeds | #* <URL-LOCAL> is the location of a local fedora repo if needed for faster response speeds | ||
# Check the {{filename|fedupdebug.log}} file if any errors show up in the output from {{command|fedup-cli}} | # Check the {{filename|fedupdebug.log}} file if any errors show up in the output from {{command|fedup-cli}} |
Revision as of 12:36, 4 January 2013
Description
This case is for upgrading using to upgrade the current release (Fedora 41) to the branched release (Fedora 42) using the Fedup CLI.
How to test
- Perform an installation of the stable release (e.g. Fedora 41) with default partitioning (no less than 500MB for
/boot
), selecting the default package set. - Do a full system update and reboot
- Install
fedup
- Be sure to get the latest release, this may involve enabling updates-testing (put
--enablerepo=updates-testing
betweenyum
andinstall
on the command line) - 2013-01-03: Make sure you have at least fedup-0.7.2-1.fc17.
- Be sure to get the latest release, this may involve enabling updates-testing (put
- Find the URL of the branched TC or RC or updates.img under test. This URL should be of the form http://dl.fedoraproject.org/pub/alt/stage/18-<compose>/Fedora/<arch>/os. The URL needs to point to the initrd.img and vmlinuz, but not necessarily all rpm packages.
- <compose> is the name of the compose under test (TC1, RC2 etc.)
- <arch> is the name of the arch running on the install to be upgraded (i386, x86_64 ...)
- Start the upgrade prep by executing following command
sudo fedup-cli --network 18 --debuglog fedupdebug.log --instrepo <URL>
- <URL> is the location found in the previous step
- To utilize a local mirror for the new arch Start the upgrade prep by executing following command
sudo fedup-cli --network 18 --debuglog fedupdebug.log --instrepo <URL> --disablerepo=fedora --repourl fedora-local=<URL-LOCAL>
- <URL-LOCAL> is the location of a local fedora repo if needed for faster response speeds
- Check the
fedupdebug.log
file if any errors show up in the output fromfedup-cli
- Reboot the system if
fedup-cli
has completed without error. - Once the system reboots, there should be a new entry in the GRUB menu titled
System Upgrade
. - Select the
System Upgrade
option from the GRUB menu- If you want to be able to see progress during the upgrade, append
plymouth.splash=fedup
to the end of the kernel parameters
- If you want to be able to see progress during the upgrade, append
- The system should boot into the upgrade process and a fedup progress screen should be displayed
- Press the <ESC> key, will switch from the graphical progress screen to the textual progress information display
- Once the upgrade process has completed, the system will reboot and an option to boot Fedora 42 will be on the grub menu
- Log in to upgraded system, open a terminal, file browser, or other system applications.
Expected Results
fedup-cli
will run to completion, without error- The upgrade process should complete and reboot without user assistance beyond selecting
System Upgrade
from the GRUB menu - The system should be upgraded to new version without error.
- The opened terminal, file browser, or other system applications should display and work correctly.
- Running through the desktop test cases would be a good for verification.