m (→Upgrading from a Branched test release: fix header level)
(→Yum update from previous official release: oops, this was not ready for prime time)
|Line 79:||Line 79:|
=== Yum update from previous official release ===
=== Yum update from previous official release ===
== Reference info ==
== Reference info ==
Revision as of 19:06, 9 March 2010
The Branch Freeze Policy describes the process of building packages during this phase. Essentially there are non-rawhide repositories with the version number of the release-to-be (currently 34). New builds go to the "updates-testing" repository; after approval in Bodhi, they are promoted directly to the "stable" repository for that release. (There is no "updates" repository until the final general availability release.)
- 1 Installation options
- 1.1 How to avoid disturbing an existing system
- 1.2 Direct install, upgrade, or no-install testing with a nightly Live build
- 1.3 Installing via Anaconda
- 1.4 Yum update from previous official release
- 2 Reference info
How to avoid disturbing an existing system
There are a few methods to test the Branched release on a machine without disturbing an existing installation:
- Test a Live version from USB or DVD drive.
- Use a virtual machine. See Testing/qemu.
- Install to a separate partition.
Direct install, upgrade, or no-install testing with a nightly Live build
Nightly builds of Live spins are now available. All approved Live spins are posted, but "desktop" is the one that is used and distributed most widely. The Live method is usually the fastest for fresh installs and is how most everyday users will install the final distribution. Using these nightly builds is an ideal way to test the Branched release if you have no spare machine or partition available, or simply do not have the time to maintain a Branched installation. It's a very safe way to test, since it will make no changes to your installed system. You can also later install the Branched release to your hard drive from the Live desktop if the Live image is working well for you.
The basic steps are:
- Download a daily Live image (.iso) from: http://alt.fedoraproject.org/pub/alt/nightly-composes/
- Make a boot disk (see "How do I make a bootable disk from an ISO?" below) and boot from it.
- Start testing.
- If you want to permanently install or upgrade locally, log in and double click on the "Install to Hard Drive" icon on the desktop, then follow the on-screen instructions.
The maximum ISO size is now 1GB, which is larger than can fit on a CD. It is expected that most users will have USB or DVD media available. USB media in particular is advantageous compared to CDs, because it is cheap and highly reusable.
Builds include only package versions from the "stable" repository, so they should in general be usable; please file a bug if you encounter any problems. If there is a bug in the generation toolchain, the images may not be built on a given night; in this case, the last built image will remain available.
If you use a LiveUSB with data persistence, you can run "yum update" to get the latest RPMs (except for the kernel). However, downloading a fresh daily ISOs is recommended instead of this method.
Installing via Anaconda
Anaconda is the Fedora installer. It can be booted directly, rather than run from a Live desktop. Installation options can also be more flexible.
Upgrade from any previous release via Preupgrade and Anaconda
A faster Anaconda installation can be performed from an existing copy of Fedora with PreUpgrade. See How to use PreUpgrade for instructions. During the process, check the box next to "Display unstable test releases" and select "Fedora 34 (Branched)" from the list.
Upgrading from a Branched test release
If a test release or "pre-release" (Alpha or Beta) is currently available, you can download it from: http://fedoraproject.org/get-prerelease
Test releases are configured to update to the latest version of the Branched release which they are building on automatically. To get the latest packages, you can run "yum update" or wait for desktop notification of updates. If you continue to follow updates, you will eventually end up with the same packages and updates as are in the final general availability release.
Direct install using a general release Anaconda ISO
You can use the version of Anaconda distributed with a final public release (the latest being Fedora 33). Using this method, you will be using an older but known-to-be-working installer to install the latest content in the Rawhide repository.
- Option 1 - Use a copy you've already downloaded
If you already have a bootable CD, DVD, USB stick, or hard drive partition containing the *-DVD.iso or *-disc1.iso you can use that to install Rawhide. However, if you need to download new boot media, these files are not recommended because they contain general release versions of Fedora RPMs, and you wish to install Branched RPMs. (See installation guide download page for instructions if you want to download these files anyway.) A general release Live image cannot be used to install Branched, only the general release version of Fedora which it contains.
- Option 2 - Download the minimal installer
If you need to make a bootable CD, DVD, USB stick, or hard drive partition, the best way is to download the minimal boot.iso installer, and load RPMs over the network. This is the same as the *-netinst.iso (e.g. Fedora-12-i386-netinst.iso) which you may find elsewhere. These files are not available by BitTorrent.
To get and use a boot.iso file:
- Go to http://download.fedoraproject.org/ - you will be redirected to a nearby mirror.
- Go to releases/33/Fedora.
- Choose the directory for your architecture (i386, x86_64, or ppc - help available), then find os/images/boot.iso and download it.
- Create a bootable CD, DVD, USB media, or hard drive partition following the instructions at  and using your newly downloaded boot.iso file. You can use the livecd-iso-to-disk method described there even though boot.iso is not a Live image, and it should also work on hard drive partitions, not just USB media.
- Option 3 - Pure network install with no boot media
The Installation Guide documents how to boot the installer directly from the network, in case you cannot or choose not to create local boot media.
- What to do after booting Option 1, 2 or 3
Follow the on-screen instructions from Anaconda, the graphical installer. The installation is very straightforward. You should do a HTTP/FTP install. To get Branched instead of a supported release, for the URL of your 'install tree', use "<mirrorroot>/development/34/<arch>/os/" where <mirrorroot> is the mirror site URL you got from the mirror list and <arch> is your architecture (i386, x86_64, or ppc).
- Option 4 - With no network access at install time
If you have no network access during the install process, you will need to download the Branched (development/34) repository from a development mirror and use the hard drive installation method described in the Installation Guide, or it might be easier to choose a different method to install Branched from another section of this page.
Direct install using daily Branched Anaconda build
Using this method, you will be testing not only the contents of Branched, but also the Branched version of the installer which will become the installer for the next version of Fedora.
Follow the same steps as in "Using a general release Anaconda ISO" above, but get your boot.iso from "development/34/<arch>/os/images/" one of the mirrors listed at: http://mirrors.fedoraproject.org/publiclist/Fedora/development/
Yum update from previous official release
(documentation in progress)
How do I make a bootable disk from an ISO?
- To write to USB media, see How to create and use Live USB.
- To burn a DVD, see the burning ISOs readme.
Where is the Branched release mirrored?
The current Branched release is found under "development/34" on the mirrors. You can find a local mirror from: http://mirrors.fedoraproject.org/publiclist/Fedora/34/