- 1 Rawhide
- 1.1 Goals
- 1.2 Using Rawhide
- 1.3 Producing Rawhide
- 1.4 Questions and Answers
- 1.5 Hints and Tips
- 1.6 History
Rawhide is the name given to the current development version of Fedora. It consists of a package repository called "rawhide" and contains the latest build of all Fedora packages updated on a daily basis. Nightly live image builds are also available during the early portion of the Fedora Release Life Cycle.
Rawhide is sometimes called "development" or "master" (as it's the "master" branch in Package git repositories).
Rawhide has the following Goals:
- To allow package maintainers to integrate the newest usable versions of their packages into Fedora.
- To allow advanced users access to the newest usable packages in a rolling manner.
- To allow incremental changes to packages that are either too minor or major to go to stable Fedora releases.
- To identify and fix issues with packages before they reach a stable release of Fedora.
This section discusses rawhide's target users and how to test Rawhide with Live media, within a virtual installation or on a bare metal installation.
Rawhide is targeted at advanced users, testers and package maintainers.
As a rawhide consumer, you should:
- Be willing to update on an almost daily basis. Rawhide gets hundreds of updates a day, and applying those updates on a regular basis allows you to more easily troubleshoot issues.
- Be willing and able to troubleshoot problems. From time to time there are problems with Rawhide packages, and you will need strong troubleshooting skills and the ability to gather information for bug reports. You need a good understanding of yum and how to downgrade packages, as well as boot time troubleshooting.
- Have time and desire to always be able to learn new interfaces and changes. Rawhide packages stick closely to upstream projects, so interfaces and command-line options are subject to frequent changes.
- Frequent reboots to test new kernel versions and confirm functionality of the boot process. If you can't reboot often, consider using a stable release instead.
- Be willing and able to report bugs as you find them and help maintainers gather information to fix them.
After the release of the previous final release, but before the Branch event, nightly builds will be composed from Rawhide. You may be able to use these automated Live images to boot and test Rawhide. These images are automatically composed and not tested by QA.
You may wish to install and run Rawhide in a virtual machine (VM) instance. This allows you to test Rawhide when not running Linux, or avoid any impact to your day-to-day workflow.
See the section below on setting up a Rawhide install.
Getting a Rawhide install
The Rawhide tree is not directly installable so you will often need to install in several steps.
Install from Live media
If Live media are being composed from Rawhide (see above), you may be able to download the Live media, copy it to local media, boot and install Rawhide.
This is the most fragile way to get a Rawhide install, as Live media is only produced at some points in the cycle, sometimes does not compose, and when it does, may not install correctly.
Point installer to Rawhide
You can sometimes install Rawhide by using a stable install media and pointing it to the Rawhide repository for packages to install.
- Download the latest stable or branched install media. (netinstall or DVD install)
- Copy to local media (USB or DVD or CD)
- Boot media and go to the 'Install Source' section and manually enter:
(or i386 for 32bit)
- Finish the install as normal.
For this method to work, there should be no major changes in Rawhide that the installer is not ready for, such as packages it depends on being retired or other similar situations.
Yum from Existing install
You may use yum to upgrade from the most recent Stable or Branched release. You will need to have such an install in place and should likely update to the newest updates before starting.
This method may fail if there are upgrade path issues (newer packages in Stable or Branched than Rawhide), or broken dependencies.
There are a number of ways to communicate with other Rawhide users:
Rawhide discussion is on topic and welcome in both the #fedora-devel and #fedora-qa IRC channels.
Rawhide bugs should be reported against the Fedora Product, rawhide version and the affected component. Please do follow best practices when filing. Remember that IRC and mailing lists are useful to help narrow down if some behavior is a bug or where to report it, but are themselves not bug reporting channels. Always file bugs in Bugzilla.
Note that broken dependencies are mailed to maintainers for each daily Rawhide compose where a package has such broken dependencies. Therefore, it's usually not worth filing a bug for broken dependencies unless they don't appear in the daily report, or you have a fix or improvement to suggest.
The Rawhide repository is composed every day starting at 08:15UTC. All rawhide builds in the buildsystem at that time are composed and pushed out to mirrors. Rawhide is under "development/rawhide" on the mirrors. You can find a local "development" mirror on the public mirror list. Compose time varies depending on number of changes but is typically between 5 and 8 hours.
Composes are done in a rawhide chroot using the 'mash' tool called from a script maintained by Fedora Release engineering: http://git.fedorahosted.org/cgit/releng/tree/scripts/buildrawhide If the base set of packages in rawhide needed to compose rawhide are broken, the daily compose may fail.
A report for each Rawhide compose is sent to to the test and the devel lists. This report contains output from the 'repodiff' tool from the previous compose as well as a broken dependency report for packages with broken dependencies. Additionally, private email is sent to maintainers with packages containing broken dependencies.
Package maintainers should read and follow the Rawhide updates policy for building any packages in Rawhide.
If needed and approved by FESCo, Mass Rebuilds are done by release-engineering in Rawhide a month or so before the next release branches from it. Typically these are done for a global change over all packages such as a new gcc release, or rpm package format.
Rawhide packages are currently not signed. Work is ongoing to sign at least the majority of them.
Questions and Answers
Q: Doesn't rawhide eat babies / kill pets / burn down houses / break constantly?
A: No. Please stop telling anyone that.
Q: So Rawhide is very stable and we can all use it?
A: No. See audience above. There are things that break from time to time, but if you are able to downgrade or troubleshoot such issues aren't too severe, however most users should stick to Stable Fedora releases.
Q: I'm using a Stable Fedora release, but I want the newer package for foo thats only available in Rawhide. Can I just yum install it?
A: No. Mixing releases like this is a very bad idea. Your better options are:
- Obtain the src.rpm for the package you wish and try and rpmbuild --rebuild it (which may or may not work depending on dependencies)
- Ask the Fedora maintainer in a bug report to update the stable version if permitted by policy.
Q: I want to run the rawhide kernel on my Stable Fedora machine. Can I do that?
A: Sometimes yes. The kernel is more self contained than other rawhide packages and you also can easily boot your older kernel. Simply download and yum install the package.
Q: Is Rawhide a "rolling release" ?
A: It depends on how you define that, but yes.
Q: How can I tell when the rawhide compose for the day has finished?
Hints and Tips
- Your package management system can be of great help in diagnosing and working around issues you find. Do read up and understand: 'yum downgrade' 'yum history' 'yum update --skip-broken' 'koji download-build'.
- You should update frequently (preferably every day). This allows you to more easily narrow down when a problem or issue appeared. If you apply a week of Rawhide updates at once you have many more packages to examine to narrow down issues.
- Reboot often (preferably whenever new kernels arrive). This allows you to test the boot up process and packages related to it, as well as newer kernels. Read and understand the Dracut troubleshooting steps.
- Follow the test and the devel lists for rawhide issues, try and at least skim them before doing your daily Rawhide updates. Look for '[rawhide]' subjects or reports of issues. Additionally if you find a problem and are not sure what to file bugs against you can open a discussion there.
- Rawhide kernels are made with a large amount of debugging enabled. You can often gain a good deal of performance by passing "slub_debug=-" to your kernel boot line in /etc/grub2.cfg. Additionally, you can run kernels in the Rawhide Kernel Nodebug repo that have all debugging disabled.
- If you are using a graphical desktop environment in your Rawhide install, you may wish to install several of them. This allows you to still login and troubleshoot when your primary desktop environment is not working for some reason.
- Have a rescue media handy of the current stable Fedora release for emergencies.
Red Hat Linux "Raw Hide" announcement: on lwn
The name might come from the song with the same name that starts with "Rolling, rolling, rolling, ..."
At one time, rawhide would freeze before release milestones, this was changed with the new: No_Frozen_Rawhide_Proposal and branched process which we now follow.