Releases/Rawhide

From FedoraProject

< Releases(Difference between revisions)
Jump to: navigation, search
(Clearly explain that rawhide packages still need to be built through koji.)
(update the 'switch off of Rawhide' question with fedora-repos-rawhide package info and more detail on repo configuration)
 
(21 intermediate revisions by 5 users not shown)
Line 1: Line 1:
 
{{autolang|base=yes}}
 
{{autolang|base=yes}}
  
= Rawhide =
+
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, network install, ARM and Cloud image builds are also available.
 
+
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 is sometimes called "development" or "master" (as it's the "master" branch in Package git repositories).  
Line 16: Line 14:
 
* To identify and fix issues with packages before they reach a stable release of Fedora.
 
* To identify and fix issues with packages before they reach a stable release of Fedora.
  
== Using Rawhide ==
+
== Audience ==
 
+
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.
+
 
+
=== Audience ===
+
  
 
Rawhide is targeted at advanced users, testers and package maintainers.  
 
Rawhide is targeted at advanced users, testers and package maintainers.  
  
As a rawhide consumer, you should:  
+
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 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.
Line 38: Line 32:
 
If the above doesn't match you, you may wish to instead follow the [[Releases/Branched|Branched]] release (depending on the point in the [[Releases/{{FedoraVersion||next}}/Schedule|release cycle]]) or use regular stable Fedora releases.  
 
If the above doesn't match you, you may wish to instead follow the [[Releases/Branched|Branched]] release (depending on the point in the [[Releases/{{FedoraVersion||next}}/Schedule|release cycle]]) or use regular stable Fedora releases.  
  
=== Live media ===
+
== Using Rawhide ==
  
After the release of the previous final release, but before the [[Releases/{{FedoraVersion||next}}|Branch event]], [http://alt.fedoraproject.org/pub/alt/nightly-composes/ 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]].  
+
This section discusses how to use Rawhide, as a live system or permanently installed.
  
=== Virtual instances  ===
+
=== Not recommended for production systems ===
  
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.
+
We do not recommend that you run Rawhide as your primary production operating system. Instead, we suggest you could install and run Rawhide:
  
See the section below on setting up a Rawhide install.
+
* 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
  
=== Getting a Rawhide install ===
+
This allows you to test Rawhide without any impact to your day-to-day workflow.
  
The Rawhide tree is not directly installable so you will often need to install in several steps.
+
=== Nightly images ===
  
==== Install from Live media ====
+
All nightly images are automatically generated, are not tested by QA, and even when compose succeeds, may be broken or buggy.
  
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.  
+
Rawhide live images are automatically composed each night (U.S. time) by [[Koji]]. You can find these live images via the [https://apps.fedoraproject.org/releng-dash/ Release Engineering dashboard], under ''LiveCD Builds''. Clicking on the name of an image will download the most recent successful nightly compose.
  
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.
+
A network install image named {{filename|boot.iso}} is also generated for Rawhide each night, and can be found in the {{filename|pub/fedora/linux/development/rawhide/(arch)/os/images/}} directory on mirrors:
  
==== Point installer to Rawhide ====
+
* [http://download.fedoraproject.org/pub/fedora/linux/development/rawhide/x86_64/os/images/boot.iso x86_64]
 +
* [http://download.fedoraproject.org/pub/fedora/linux/development/rawhide/i386/os/images/boot.iso i386]
  
You can sometimes install Rawhide by using a stable install media and pointing it to the Rawhide repository for packages to install.  
+
Note that if generation of the {{filename|boot.iso}} images fails for a given day, the file will not be present on the mirrors (the last successful compose is not retained). In this case, you just have to wait for a successful compose, or use one of the other images/methods described on this page.
  
# Download the latest stable or branched install media. (netinstall or DVD install)
+
You can attempt to install Rawhide from these images; you are considerably more likely to encounter problems than you would with a stable release, however, as the installer itself and all its dependencies are of course in an unstable state. Follow the [http://docs.fedoraproject.org/en-US/Fedora/{{FedoraVersion}}/html/Installation_Guide/index.html normal installation procedure] to install Rawhide.
# Copy to local media (USB or DVD or CD)
+
 
# Boot media and go to the 'Install Source' section and manually enter:<br />https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/x86_64/os/<br />(or i386 for 32bit)
+
For PXE installations, the relevant files can be found in the {{filename|pub/fedora/linux/development/rawhide/(arch)/os/images/pxeboot}} directory.
 +
 
 +
Nightly [[Architectures/ARM|ARM]] and Cloud disk images can be found on the [https://apps.fedoraproject.org/releng-dash/ Release Engineering dashboard], similar to the nightly live images.
 +
 
 +
=== Point installer to Rawhide repositories ===
 +
 
 +
You can sometimes install Rawhide by using a stable install medium and pointing it to the Rawhide repository for packages to install.
 +
 
 +
# Boot the most recent stable Fedora installer following the [http://docs.fedoraproject.org/en-US/Fedora/{{FedoraVersion}}/html/Installation_Guide/index.html normal procedure]
 +
# Go to the ''Installation Source'' screen, click the ''On the network:'' button, set the dropdown box to ''https://'', and manually enter: ''download.fedoraproject.org/pub/fedora/linux/development/rawhide/(arch)/os/'' (where (arch) is x86_64 or i386 as appropriate) as the address
 
# Finish the install as normal.  
 
# 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.
 
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 ====
+
=== Upgrade from an existing installation ===
  
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.  
+
You may also try to install a non-Rawhide release of Fedora, and then upgrade to Rawhide. It is usually best to use the newest release available, and install all updates for the release itself before attempting to upgrade to Rawhide.
  
See [[Upgrading_Fedora_using_yum#To_rawhide|Upgrading Fedora using yum Rawhide info]]
+
You can attempt the upgrade [[Upgrading_Fedora_using_yum#To_rawhide|with yum]] or with [[FedUp]]. To use fedup, run {{command|fedup --network rawhide --nogpgcheck --instrepo <nowiki>http://download.fedoraproject.org/pub/fedora/linux/development/rawhide/$(uname -i)/os/</nowiki>}}.
  
This method may fail if there are upgrade path issues (newer packages in Stable or Branched than Rawhide), or broken dependencies.  
+
This method may fail if there are upgrade path issues (newer packages in Stable or Branched than Rawhide), or broken dependencies. You may be able to work around the problem by removing the packages that have issues (and reinstalling them at a later date once the issues are fixed).
  
=== Communicating  ===
+
== Discussing Rawhide ==
  
 
There are a number of ways to communicate with other Rawhide users:  
 
There are a number of ways to communicate with other Rawhide users:  
  
==== IRC ====
+
=== IRC ===
  
 
Rawhide discussion is on topic and welcome in both the {{fpchat|#fedora-devel}} and {{fpchat|#fedora-qa}} IRC channels.
 
Rawhide discussion is on topic and welcome in both the {{fpchat|#fedora-devel}} and {{fpchat|#fedora-qa}} IRC channels.
  
==== Mailing Lists ====
+
=== Mailing Lists ===
  
 
Rawhide discussion is on topic and welcome in both the {{fplist|test}} and {{fplist|devel}} lists.
 
Rawhide discussion is on topic and welcome in both the {{fplist|test}} and {{fplist|devel}} lists.
  
==== Bugzilla ====
+
=== Bugzilla ===
  
Rawhide bugs should be reported against the Fedora Product, rawhide version and the affected component.  Please do follow [[BugsAndFeatureRequests|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 [http://bugzilla.redhat.com Bugzilla].
+
Rawhide bugs should be reported against the ''Fedora'' product, ''rawhide'' version and the affected component.  Please do follow [[BugsAndFeatureRequests|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 [http://bugzilla.redhat.com 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.
 
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.
 +
 +
=== Blogs ===
 +
 +
The following blogs are not official communication, but are useful to follow if you are running Rawhide.
 +
 +
* [http://rawhidewatch.wordpress.com/ Rawhide Watch]
 +
* [http://www.scrye.com/wordpress/nirik/category/rawhide/ Kevin's musings / Rawhide]
  
 
== Producing Rawhide ==
 
== Producing Rawhide ==
Line 99: Line 113:
 
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.
 
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 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 [http://mirrors.fedoraproject.org/publiclist/Fedora/development/ on the public mirror list]. Compose time varies depending on number of changes but is typically between 5 and 8 hours.  
+
The Rawhide repository is composed every day starting at 05: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 [http://mirrors.fedoraproject.org/publiclist/Fedora/development/ 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.  
 
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.  
Line 115: Line 129:
 
'''Q:''' Doesn't rawhide eat babies / kill pets / burn down houses / break constantly?  
 
'''Q:''' Doesn't rawhide eat babies / kill pets / burn down houses / break constantly?  
  
A: No. Please stop telling anyone that.  
+
A: No. Please stop telling everyone that.  
  
 
'''Q:''' So Rawhide is very stable and we can all use it?  
 
'''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.  
+
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 the newer package for foo thats only available in Rawhide. Can I just yum install it?
+
'''Q:''' I'm using a Stable Fedora release, but I want a newer package version that's 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:  
+
A: No. Mixing releases like this is a very bad idea. 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.
* Ask the Fedora maintainer in a bug report to update the stable version if permitted by policy.  
+
* If not, there may be a [http://copr.fedoraproject.org/ 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?  
+
'''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.  
+
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 yum 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" ?
 
'''Q:''' Is Rawhide a "rolling release" ?
Line 136: Line 151:
 
A: It depends on how you define that, but yes.
 
A: It depends on how you define that, but yes.
  
'''Q:''' How can I tell when the rawhide compose for the day has finished?
+
'''Q:''' How can I tell when the Rawhide compose for the day has finished?
 +
 
 +
A: Check the [https://apps.fedoraproject.org/releng-dash/ dashboard!] You can also see the reports it sends to the {{fplist|test}} and the {{fplist|devel}} lists, or watch fedmsg for the messages that rawhide compose has finished.
 +
 
 +
'''Q:''' How do I get out of Rawhide again? I want to switch to the [[Branched]] release or a stable release.
  
A: You can see the reports it sends to the {{fplist|test}} and the {{fplist|devel}} lists. You can also watch fedmsg for the messages that rawhide compose has finished.
+
A: Remove the {{package|fedora-repos-rawhide}} package and/or disable the 'rawhide' repository ({{command|su -c 'yum-config-manager --disable rawhide'}}), enable the 'fedora' and optionally 'updates' and 'updates-testing' repositories ({{command|su -c 'yum-config-manager --enable fedora(,updates,updates-testing)'}}) and perhaps run {{command|su -c 'yum --releasever<nowiki>=</nowiki>(version) distro-sync'}}. The farther the branch to which you want to switch is behind Rawhide, the more trouble you might have with this.
  
'''Q:''' How do I get out of Rawhide again ? I want to continue on the branch leading to the next release.
+
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 yum distro-sync will help you to get everything back on the right track.
  
A: You can simply disable the rawhide repository in /etc/yum.repos.d/rawhide.repo.
+
'''Q:''' As a package maintainer do I have to build rawhide packages or does the nightly compose take care of that?
  
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, yum distro-sync will help you to get everything back on the right track.
+
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:''' As a package maintainer do I have to build rawhide packages or does the night compose take care of that?
+
'''Q:''' Why aren't Rawhide packages signed?  
  
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.
+
A: A variety of reasons. There's no gating of packages and signing is manual, so there would always be some that are not signed. Additionally resources like disk space, signing server time and releng time would be impacted.
  
 
== Hints and Tips ==
 
== 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'.
+
* Your package management system can be of great help in diagnosing and working around issues you find. Do read up and understand:
 +
** {{command|yum downgrade}}
 +
** {{command|yum history}}
 +
** {{command|yum update --skip-broken}}
 +
** {{command|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.  
 
* 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.  
Line 160: Line 183:
 
* Follow the {{fplist|test}} and the {{fplist|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.  
 
* Follow the {{fplist|test}} and the {{fplist|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 [[RawhideKernelNodebug|Rawhide Kernel Nodebug]] repo that have all debugging disabled.  
+
* 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 {{filename|/etc/default/grub}} (and re-generating your grub config, or just adding it directly). Additionally, you can run kernels in the [[RawhideKernelNodebug|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.
 
* 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.
Line 172: Line 195:
 
The name might come from [http://en.wikipedia.org/wiki/Rawhide_%28song%29 the song with the same name] that starts with "Rolling, rolling, rolling, ..."
 
The name might come from [http://en.wikipedia.org/wiki/Rawhide_%28song%29 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:
+
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.
[[No_Frozen_Rawhide_Proposal]] and branched process which we now follow.
+

Latest revision as of 23:41, 10 July 2014

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, network install, ARM and Cloud image builds are also available.

Rawhide is sometimes called "development" or "master" (as it's the "master" branch in Package git repositories).

Contents

[edit] Goals

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.

[edit] Audience

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.

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.

[edit] Using Rawhide

This section discusses how to use Rawhide, as a live system or permanently installed.

[edit] Not recommended for production systems

We do not recommend that you run Rawhide as your primary production operating system. Instead, we suggest you could install and run Rawhide:

  • 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.

[edit] Nightly images

All nightly images are automatically generated, are not tested by QA, and even when compose succeeds, may be broken or buggy.

Rawhide live images are automatically composed each night (U.S. time) by Koji. You can find these live images via the Release Engineering dashboard, under LiveCD Builds. Clicking on the name of an image will download the most recent successful nightly compose.

A network install image named boot.iso is also generated for Rawhide each night, and can be found in the pub/fedora/linux/development/rawhide/(arch)/os/images/ directory on mirrors:

Note that if generation of the boot.iso images fails for a given day, the file will not be present on the mirrors (the last successful compose is not retained). In this case, you just have to wait for a successful compose, or use one of the other images/methods described on this page.

You can attempt to install Rawhide from these images; you are considerably more likely to encounter problems than you would with a stable release, however, as the installer itself and all its dependencies are of course in an unstable state. Follow the normal installation procedure to install Rawhide.

For PXE installations, the relevant files can be found in the pub/fedora/linux/development/rawhide/(arch)/os/images/pxeboot directory.

Nightly ARM and Cloud disk images can be found on the Release Engineering dashboard, similar to the nightly live images.

[edit] Point installer to Rawhide repositories

You can sometimes install Rawhide by using a stable install medium and pointing it to the Rawhide repository for packages to install.

  1. Boot the most recent stable Fedora installer following the normal procedure
  2. Go to the Installation Source screen, click the On the network: button, set the dropdown box to https://, and manually enter: download.fedoraproject.org/pub/fedora/linux/development/rawhide/(arch)/os/ (where (arch) is x86_64 or i386 as appropriate) as the address
  3. 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.

[edit] Upgrade from an existing installation

You may also try to install a non-Rawhide release of Fedora, and then upgrade to Rawhide. It is usually best to use the newest release available, and install all updates for the release itself before attempting to upgrade to Rawhide.

You can attempt the upgrade with yum or with FedUp. To use fedup, run fedup --network rawhide --nogpgcheck --instrepo http://download.fedoraproject.org/pub/fedora/linux/development/rawhide/$(uname -i)/os/.

This method may fail if there are upgrade path issues (newer packages in Stable or Branched than Rawhide), or broken dependencies. You may be able to work around the problem by removing the packages that have issues (and reinstalling them at a later date once the issues are fixed).

[edit] Discussing Rawhide

There are a number of ways to communicate with other Rawhide users:

[edit] IRC

Rawhide discussion is on topic and welcome in both the #fedora-devel[?] and #fedora-qa[?] IRC channels.

[edit] Mailing Lists

Rawhide discussion is on topic and welcome in both the test and devel lists.

[edit] 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.

[edit] Blogs

The following blogs are not official communication, but are useful to follow if you are running Rawhide.

[edit] Producing 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 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.

[edit] Questions and Answers

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 yum 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 yum 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 dashboard! You can also see the reports it sends to the test and the devel lists, or watch fedmsg for the messages that rawhide compose has finished.

Q: How do I get out of Rawhide again? I want to switch to the Branched release or a stable release.

A: Remove the Package-x-generic-16.pngfedora-repos-rawhide package and/or disable the 'rawhide' repository (su -c 'yum-config-manager --disable rawhide'), enable the 'fedora' and optionally 'updates' and 'updates-testing' repositories (su -c 'yum-config-manager --enable fedora(,updates,updates-testing)') and perhaps run su -c 'yum --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 yum 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: Why aren't Rawhide packages signed?

A: A variety of reasons. There's no gating of packages and signing is manual, so there would always be some that are not signed. Additionally resources like disk space, signing server time and releng time would be impacted.

[edit] 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 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.

[edit] History

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.