From Fedora Project Wiki
m (clarify architecture) |
(add the 'associated criterion' block) |
||
Line 1: | Line 1: | ||
{{Template:Associated_release_criterion|releasecriterion=Fedora_{{FedoraVersionNumber|next}}_Alpha_Release_Criteria#Remote_package_sources}} | |||
{{QA/Test_Case | {{QA/Test_Case | ||
|description=This is to verify that an installation can be performed from a HTTP/FTP repository configured in the [[Anaconda]] GUI. | |description=This is to verify that an installation can be performed from a HTTP/FTP repository configured in the [[Anaconda]] GUI. |
Revision as of 22:37, 25 July 2013
Description
This is to verify that an installation can be performed from a HTTP/FTP repository configured in the Anaconda GUI.
How to test
- Boot the installer using any available non-live means (anything except
Live.iso
) - Change the installation source to point to a custom HTTP/FTP repository
- You can pick one from the list of mirrors or you can use the default redirect http://download.fedoraproject.org/pub/fedora/linux/development/42/x86_64/os (change the architecture to match the architecture of your installation media if needed, e.g. i386).
- Proceed with installation
Expected Results
- The installer accepts the HTTP/FTP repository definition
- The said repository is used for installation. This can be checked by examining the
/tmp/packaging.log
file. Example output:09:34:37,295 DEBUG packaging: adding yum repo anaconda with baseurl http://download.fedoraproject.org/pub/fedora/linux/development/42/x86_64/os and mirrorlist None 09:34:37,313 DEBUG packaging: disabling repo fedora 09:34:37,313 DEBUG packaging: disabling repo updates-testing 09:34:37,314 DEBUG packaging: disabling repo updates
- The installation completes and the new system initiates boot properly