Rawhide é o nome dado à versão atual de desenvolvimento do Fedora. Este consiste num repositório de pacotes chamado "rawhide" e contém a compilação mais recente de todos os pacotes do Fedora atualizados diariamente. Diariamente, é feita uma tentativa para criar um conjunto completo 'que pode entregar-se' (imagens de instalação e assim por diante), e todos os que compõem com sucesso são incluídos na árvore Rawhide para esse dia.
Rawhide é às vezes chamado de "development" ou "master" (como é o ramo "master" nos repositórios do pacote git).
Metas
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.
- To allow a place where certain low-level packages (approved by FESCo), including (but not limited to) glibc and gcc, can gain real-world testing of pre-release versions.
Audiência
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 isolate when a bug appeared and what package(s) are responsible.
- 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 dnf 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.
- Be willing to reboot frequently 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 to bugzilla as you find them and help maintainers gather information to fix them.
If the above doesn't match you, you may wish to instead follow the Branched release (depending on the point in the release cycle) or use regular stable Fedora releases.
Using Rawhide
This section discusses how to use Rawhide, as a live system or permanently installed.
Using a test system
If you are not able or wanting to run Rawhide 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 Rawhide 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 Rawhide.
For PXE installations, the relevant files can be found in the pub/fedora/linux/development/rawhide/Everything/(arch)/os/images/pxeboot directory.
Using nightlies in the past was a fragile way to install Rawhide, 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 Rawhide
You can sometimes install Rawhide by using a stable install media and pointing it to the Rawhide repositories for packages to install. In the past this was sometimes considered a more reliable method than using a Rawhide 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 Rawhide 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 Rawhide), or broken dependencies.
Discussão de Rawhide
There are a number of ways to communicate with other Rawhide users:
IRC
Rawhide discussion is on topic and welcome in both the #fedora-devel[?] and #fedora-qa[?] IRC channels.
Listas de Endereços (Discussão)
Rawhide discussion is on topic and welcome in both the test and devel lists.
Bugzilla
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.
Produção do Rawhide
Package owners must build for rawhide using koji just like you would any other build; you do not go through the bodhi process and the build becomes available almost immediately.
The Rawhide repository is composed every day starting at 05:15UTC. All rawhide builds in the buildsystem at that time are included in the compose attempt. The compose process also attempts to build all the standard Fedora 'deliverables' (live and install images, ARM and Cloud disk images, Docker images and so on). If any release-blocking image fails to build as part of the compose, the compose is considered to have failed. If the compose completes successfully, the compose will be 'synced out' to the mirror system. (A system where the sync only happens if a set of automated tests run on it passes is planned, but not yet fully implemented). 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 'pungi' tool called from a script maintained by Fedora Release engineering. 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.
Perguntas e Respostas
Q: Doesn't rawhide eat babies / kill pets / burn down houses / break constantly?
A: No. Please stop telling everyone 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. Most users should still stick to stable Fedora releases, but Rawhide is a viable option for enthusiasts to experiment with.
Q: I'm using a Stable Fedora release, but I want a newer package version that's only available in Rawhide. Can I just dnf install it?
A: No. Mixing releases like this is a very bad idea. Better options are:
- Ask the Fedora maintainer in a bug report to update the stable version if permitted by policy.
- If not, there may be a COPR that provides the updated version. See the COPR page for more details.
- Obtain the src.rpm for the package you wish and try and rpmbuild --rebuild it (which may or may not work depending on dependencies).
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 if the Rawhide kernel goes wrong. Simply download and dnf install the package. However, note that Rawhide kernels often have debugging code enabled, which results in them performing noticeably worse than 'release' kernels (they will be slower and consume more memory).
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?
A: Check the for the reports sent to the test and the devel lists, or watch fedmsg for the org.fedoraproject.prod.pungi.compose.status.change topic.
Q: How do I get out of Rawhide again? I want to switch to the Branched release or a stable release.
A: Remove the 
fedora-repos-rawhidesu -c 'dnf config-manager --set-disabled rawhide'), enable the 'fedora' and optionally 'updates' and 'updates-testing' repositories (su -c 'dnf config-manager --set-enabled fedora(,updates,updates-testing)') and perhaps run su -c 'dnf --releasever=(version) distro-sync'. The farther the branch to which you want to switch is behind Rawhide, the more trouble you might have with this.
A possible problem is that you might miss the branching point, and your system has already a bunch of post-branch Rawhide packages installed. In that case, the dnf distro-sync will help you to get everything back on the right track.
Q: As a package maintainer do I have to build rawhide packages or does the nightly compose take care of that?
A: No. You must build for Rawhide using koji. The nightly compose only collects packages already built and marked with the appropriate target (rawhide) in koji.
Q: Os pacotes Rawhide estão assinados?
A: They are. All of them are now signed. Make sure you have gpgcheck=1 set in your repo file to take advantage of this.
Dicas e Sugestões
- Your package management system can be of great help in diagnosing and working around issues you find. Do read up and understand:
dnf downgradednf historydnf update --skip-brokenkoji 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 often built with varying degrees of debugging code enabled, which will result in worse performance and increased resource usage. See KernelDebugStrategy for details on exactly what debugging code is enabled for which kernel builds. You can disable SLUB debugging for those builds for which it is enabled by passing "slub_debug=-" to your kernel command line in
/etc/default/grub(and re-generating your grub config, or just adding it directly). 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.
Histórico
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 No_Frozen_Rawhide_Proposal and Branched process which we now follow.