(goddamn whitespace) |
Michael-wzq (talk | contribs) m (Fixed rawhide link as per https://docs.fedoraproject.org/en-US/quick-docs/fedora-repositories/#the-rawhide-repository) |
||
| (16 intermediate revisions by 6 users not shown) | |||
| Line 1: | Line 1: | ||
== Using {{{release|$RELEASE}}} == | |||
Each successful compose is tested by [https://openqa.fedoraproject.org openQA] and a mail summarizing the results is sent to the {{fplist|devel}} and {{fplist|test}} mailing lists, so you can check the openQA interface or the 'compose check report' emails to check whether that day's compose is installable. You may also use the [https:// | This section discusses how to use {{{release|$RELEASE}}}, as a live system or permanently installed. | ||
=== Using a test system === | |||
If you are not able or wanting to run {{{release|$RELEASE}}} as your primary system you could instead run it: | |||
* As a live environment only | |||
* In a virtual machine (VM) instance | |||
* On a secondary system | |||
* On a multiboot system, alongside a stable release of Fedora or another operating system | |||
This allows you to test {{{release|$RELEASE}}} without any impact to your day-to-day workflow. | |||
=== Install from nightly composes === | |||
Each day (or sometimes more than once per day) {{#ifeq:{{{release|}}}|Branched|that Branched exists|}}, a full 'compose' of the tree is attempted. This will usually result in the creation of all or most of the usual install, live and disk images, installer trees and so forth. Successful composes are synced to the {{filename|/fedora/linux/development/}} directory on the mirrors, and you can find the images there. | |||
Each successful compose is tested by [https://openqa.fedoraproject.org openQA] and a mail summarizing the results is sent to the {{fplist|devel}} and {{fplist|test}} mailing lists, so you can check the openQA interface or the 'compose check report' emails to check whether that day's compose is installable. You may also use the [https://openqa.fedoraproject.org/nightlies.html nightly image finder] tool maintained and hosted by a [[User:Adamwill|Fedora QA team member]], which conveniently offers the last completed build for each image and the last that passed all tests, for openQA or [https://apps.fedoraproject.org/autocloud/jobs/ Autocloud]-tested images. | |||
At least the Server and Everything network install images should ''always'' be present, as composes are considered to have failed if creation of those images fails. However, at present they are not guaranteed to be ''working'' every day. | |||
Follow the [https://docs.fedoraproject.org/en-US/fedora/rawhide/install-guide/ normal installation procedure] to install {{{release|$RELEASE}}}. | |||
For PXE installations, the relevant files can be found in the {{filename|pub/fedora/linux/development/{{#ifeq:{{{release|}}}|Rawhide|rawhide|{{FedoraVersionNumber|next}}}}/Everything/(arch)/os/images/pxeboot}} directory. | |||
Using nightlies in the past was a fragile way to install {{{release|'''$RELEASE'''}}}, but with improved compose processes since Fedora 24 and automated testing since Fedora 23, their quality has improved substantially and this will often result in the best experience. | Using nightlies in the past was a fragile way to install {{{release|'''$RELEASE'''}}}, but with improved compose processes since Fedora 24 and automated testing since Fedora 23, their quality has improved substantially and this will often result in the best experience. | ||
{{#ifeq:{{{release|}}}|Branched| | |||
=== Install a pre-release === | |||
If the Branched release has already spawned an Alpha or Beta release, you can simply install that. It should be available from [https://getfedora.org/ the Fedora download page] - if an Alpha or Beta is available, you should see mentions of it around the site. Install and then update as usual. Installing a pre-release and following normal update procedures will result in your installation tracking the Branched release. | |||
Pre-releases undergo somewhat more intensive testing than nightly composes, but on the other hand, a nightly compose a few days before the Beta release may well work much better than the Alpha release did. Alpha releases can be expected to meet the Alpha [[Fedora Release Criteria]], and Beta releases to meet the Beta criteria. | |||
Before each of the above milestones, [[QA:SOP_compose_request|'candidate' compose]] images are sometimes available. These are produced as part of the [[QA:Release_validation_test_plan|process of validating releases]]. These images may or may not install correctly, but you can usually find the [http://qa.fedoraproject.org/blockerbugs/current list of known blockers] to see if they affect you. You can also refer to the validation results page for the compose to see how well it works, according to the QA testers. | |||
|}} | |||
=== Point installer to {{{release|$RELEASE}}} === | |||
You can sometimes install {{{release|$RELEASE}}} by using a stable install media and pointing it to the {{{release|$RELEASE}}} repositories for packages to install. In the past this was sometimes considered a more reliable method than using a {{{release|$RELEASE}}} compose, but with improvements to the compose and test process in the last few years this is rarely likely to be a good choice any longer. If you wish to try it, however, you can: | |||
# Download the latest stable or branched install media (network install or offline ("DVD") installer image) | |||
# Copy to local media ([https://docs.fedoraproject.org/en-US/quick-docs/creating-and-using-a-live-installation-image/index.html USB] or [https://docs.fedoraproject.org/en-US/fedora/f{{FedoraVersionNumber}}/install-guide/install/Preparing_for_Installation/#_creating_a_boot_cd_or_dvd DVD or CD]) | |||
# Boot media and go to the 'Installation Source' screen and manually enter: {{filename|https://download.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/}} (or i386 for 32-bit) | |||
# Finish the install as normal. | |||
For this method to work, there should be no major changes in {{{release|$RELEASE}}} that the installer is not ready for, such as packages it depends on being retired or other similar situations. | |||
=== Upgrade from existing stable install === | |||
You may use [[DNF_system_upgrade]] to upgrade from the most recent stable release. You will need to have such an install in place and should likely update to the newest updates before starting. As an exception, if you are using Fedora Silverblue, you may use <code>rpm-ostree rebase</code> to perform the upgrade, see [https://docs.fedoraproject.org/en-US/fedora-silverblue/updates-upgrades-rollbacks/#upgrading Fedora Docs] for more details. | |||
This method may fail if there are upgrade path issues (newer packages in stable or than {{{release|$RELEASE}}}), or broken dependencies. | |||
Latest revision as of 11:39, 16 May 2024
Using $RELEASE
This section discusses how to use $RELEASE, as a live system or permanently installed.
Using a test system
If you are not able or wanting to run $RELEASE as your primary system you could instead run it:
- As a live environment only
- In a virtual machine (VM) instance
- On a secondary system
- On a multiboot system, alongside a stable release of Fedora or another operating system
This allows you to test $RELEASE without any impact to your day-to-day workflow.
Install from nightly composes
Each day (or sometimes more than once per day) , a full 'compose' of the tree is attempted. This will usually result in the creation of all or most of the usual install, live and disk images, installer trees and so forth. Successful composes are synced to the /fedora/linux/development/ directory on the mirrors, and you can find the images there.
Each successful compose is tested by openQA and a mail summarizing the results is sent to the devel and test mailing lists, so you can check the openQA interface or the 'compose check report' emails to check whether that day's compose is installable. You may also use the nightly image finder tool maintained and hosted by a Fedora QA team member, which conveniently offers the last completed build for each image and the last that passed all tests, for openQA or Autocloud-tested images.
At least the Server and Everything network install images should always be present, as composes are considered to have failed if creation of those images fails. However, at present they are not guaranteed to be working every day.
Follow the normal installation procedure to install $RELEASE.
For PXE installations, the relevant files can be found in the pub/fedora/linux/development/42/Everything/(arch)/os/images/pxeboot directory.
Using nightlies in the past was a fragile way to install $RELEASE, but with improved compose processes since Fedora 24 and automated testing since Fedora 23, their quality has improved substantially and this will often result in the best experience.
Point installer to $RELEASE
You can sometimes install $RELEASE by using a stable install media and pointing it to the $RELEASE repositories for packages to install. In the past this was sometimes considered a more reliable method than using a $RELEASE compose, but with improvements to the compose and test process in the last few years this is rarely likely to be a good choice any longer. If you wish to try it, however, you can:
- Download the latest stable or branched install media (network install or offline ("DVD") installer image)
- Copy to local media (USB or DVD or CD)
- Boot media and go to the 'Installation Source' screen and manually enter:
https://download.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/(or i386 for 32-bit) - Finish the install as normal.
For this method to work, there should be no major changes in $RELEASE that the installer is not ready for, such as packages it depends on being retired or other similar situations.
Upgrade from existing stable install
You may use DNF_system_upgrade to upgrade from the most recent stable release. You will need to have such an install in place and should likely update to the newest updates before starting. As an exception, if you are using Fedora Silverblue, you may use rpm-ostree rebase to perform the upgrade, see Fedora Docs for more details.
This method may fail if there are upgrade path issues (newer packages in stable or than $RELEASE), or broken dependencies.