Releases/Rawhide

From FedoraProject

< Releases(Difference between revisions)
Jump to: navigation, search
m (Using a general release Anaconda ISO)
(Clearly explain that rawhide packages still need to be built through koji.)
(31 intermediate revisions by 12 users not shown)
Line 1: Line 1:
Rawhide is the name given to the current development head of Fedora.  It consists of a package repository called "rawhide", which contains the latest build of all Fedora packages, updated daily.  During the early part of the [[Fedora Release Life Cycle]], nightly composes are also available.
+
{{autolang|base=yes}}
  
== Who should use Rawhide? ==
+
= Rawhide =
  
No-one should use Rawhide as their main day-to-day workstation. As Rawhide is a development branch, many changes are not heavily tested (or tested at all) before being released to Rawhide, and packages in Rawhide can and do break without warning. It is even possible that bugs in Rawhide could cause data loss. However, testing Rawhide is a very valuable activity which helps to direct Fedora development and ensure the quality of stable releases is high. It's also a fun way to try out the latest software almost as soon as it comes out. Testing Rawhide is a great way to contribute to Fedora development. You can try out Rawhide or [[Releases/Branched|Branched]] (depending on the point in the [[Releases/{{FedoraVersion||next}}/Schedule|release cycle]]) from the [http://alt.fedoraproject.org/pub/alt/nightly-composes/ nightly live builds] without needing to install it at all. Otherwise, you can install it if you have a spare system, or are willing to install Rawhide to spare space on an existing system and dual boot, or use a virtual machine.
+
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]].
  
== Nightly live builds ==
+
Rawhide is sometimes called "development" or "master" (as it's the "master" branch in Package git repositories).
  
After the go ahead for 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 of Rawhide pacakges.  These are built automatically without manual tweaking or testing, so they will sometimes be beyond the size of a single CD, and sometimes may not work at all. 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. Using these nightly builds is an ideal way to test Rawhide if you have no spare machine or partition available, or simply do not have the time to maintain a Rawhide installation. It's a very safe way to test, since it will make no changes to your installed system.  You can also later install Rawhide to your hard drive from the Live desktop if the Live image is working well for you.  During the rest of the release cycle, daily builds will contain [[Releases/Branched|Branched]] content, and to install Rawhide you must use a repository (though you can build a custom spin using Revisor if you need to test a Live distribution).
+
== Goals ==
  
See [[FedoraLiveCD]] for more information.
+
Rawhide has the following Goals:
  
== Installing Rawhide ==
+
* 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.
  
Rawhide is meant to be installable, however, a particular Rawhide tree may not be installable due to bugs in the installer or other packages. There are many ways to install Rawhide.
+
== Using Rawhide ==
  
=== Rawhide mirrors ===
+
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 under "development/rawhide" on the mirrors. You can find a local "development" mirror here: <BR>
+
=== Audience ===
http://mirrors.fedoraproject.org/publiclist/Fedora/development/
+
  
(Continue reading for specific instructions on how to install mirrored content.)
+
Rawhide is targeted at advanced users, testers and package maintainers.  
  
=== How to avoid disturbing an existing system ===
+
As a rawhide consumer, you should:
  
There are a few methods to test Rawhide on a machine without disturbing an existing installation:
+
* 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.
# Test a Live version from CD, DVD, or USB drive.
+
#* To burn to CD or DVD, see the [http://docs.fedoraproject.org/readme-burning-isos/ burning ISOs readme].
+
#* To write to USB, see [[How to create and use Live USB]].
+
#* If you use a LiveUSB with data persistence, you can use the "yum update" method described below to get the latest daily Rawhide RPMs ([https://bugzilla.redhat.com/show_bug.cgi?id=446935 except for the kernel]). Note that you may also need to install the 'fedora-release-rawhide' package and enable the rawhide repository. However, downloading daily ISOs is recommended instead of this method.
+
# Use a virtual machine.  See [[Testing/qemu]].
+
# Install to a separate partition.
+
  
=== Direct Rawhide install via standalone Anaconda ===
+
* 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.
  
Anaconda is the Fedora installer.  It can be booted directly, rather than run from a Live desktop.
+
* 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.
  
==== Using a general release Anaconda ISO ====
+
* 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.
  
You can use the version of Anaconda distributed with a final public release (the latest being Fedora {{FedoraVersion}}).  Using this method, you will be using an older but known-to-be-working installer to install the latest content in the Rawhide repository.
+
* Be willing and able to report bugs as you find them and help maintainers gather information to fix them.  
  
;Option 1 - Use a copy you've already downloaded
+
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 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 Rawhide RPMs.  (See [http://docs.fedoraproject.org/install-guide/f12/en-US/html/ch-new-users.html#sn-howto-download installation guide download page] for instructions if you want to download these files anyway.) A general release ''Live'' image cannot be used to install Rawhide, only the general release version of Fedora which it contains.
+
  
;Option 2 - Download the minimal installer
+
=== Live media ===
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:
+
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]].  
* Go to http://download.fedoraproject.org/ - you will be redirected to a nearby mirror.
+
* Go to releases/{{FedoraVersion}}/Fedora.
+
* Choose the directory for your architecture (i386, x86_64, or ppc - [http://docs.fedoraproject.org/install-guide/f{{FedoraVersion}}/en-US/html/sn-which-arch.html 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 [http://docs.fedoraproject.org/install-guide/f12/en-US/html/ch-new-users.html#sn-making-media] 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
+
=== Virtual instances  ===
  
The Installation Guide documents how to [http://docs.fedoraproject.org/install-guide/f{{FedoraVersion}}/en-US/html/ap-medialess-install.html boot the installer directly from the network], in case you cannot or choose not to create local boot media.
+
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.
  
;What to do after booting Option 1, 2 or 3
+
See the section below on setting up a Rawhide install.
  
Follow the on-screen instructions from Anaconda, the graphical installer.  The installation is very straightforward. You should do a HTTP/FTP install.  To get Rawhide instead of a supported release, for the URL of your 'install tree', use "<mirrorroot>/development/rawhide/<arch>/os/" where <mirrorroot> is the mirror site URL you got from [http://mirrors.fedoraproject.org/publiclist/Fedora/development/ the mirror list] and <arch> is your architecture (i386, x86_64, or ppc).
+
=== Getting a Rawhide install ===
  
[2010-04-09 Note: Anaconda 13.37.2 does not work here because os/install.img cannot be found at any mirror, not even the master http://download.fedora.redhat.com/pub/fedora/linux/development/rawhide/x86_64/os/.]
+
The Rawhide tree is not directly installable so you will often need to install in several steps.
  
;Option 4 - With no network access at install time
+
==== Install from Live media ====
  
If you have no network access during the install process, you will need to download the Rawhide (development) repository from a [http://mirrors.fedoraproject.org/publiclist/Fedora/development/ Rawhide mirror] and use the hard drive installation method described in the [http://docs.fedoraproject.org/install-guide/ Installation Guide], or it might be easier to choose a different method to install Rawhide from another section of this page.
+
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.  
  
==== Using daily Rawhide Anaconda build ====
+
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.
  
Daily Anaconda builds are no longer automatically available in Rawhide, only in [[Releases/Branched|Branched]] code.  Pre-Alpha Anaconda code is generally not testable, and it is important to test the installer that will appear in the next release (since it cannot easily be fixed after distribution media have been created) rather than the release after the next release.
+
==== Point installer to Rawhide ====
  
Installer images ''can'' be provided on demand for test days if they are needed but not automatically available; please contact James Laska.
+
You can sometimes install Rawhide by using a stable install media and pointing it to the Rawhide repository for packages to install.  
  
=== Direct Rawhide install via Live installer ===
+
# 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:<br />https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/x86_64/os/<br />(or i386 for 32bit)
 +
# Finish the install as normal.
  
'''''This method only works pre-Branch Event in the [[Releases/{{FedoraVersion||next}}|release schedule]]; after that, it will produce [[Releases/Branched|Branched]] content.'''''
+
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.
  
* Download a daily Live image (.iso) from http://alt.fedoraproject.org/pub/alt/nightly-composes/
+
==== Yum from Existing install ====
* Follow the steps at [[How to create and use Live USB]] or [[How to create and use a Live CD]] to prepare and boot from the image you select.
+
* Log in and double click on the "Install to Hard Drive" icon on the desktop.
+
* Follow the on-screen instructions.
+
  
=== Yum update from a test release ===
+
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.
  
If a test release or "pre-release" (Alpha or Beta) is currently available, you can download it from: http://fedoraproject.org/get-prerelease
+
See [[Upgrading_Fedora_using_yum#To_rawhide|Upgrading Fedora using yum Rawhide info]]
  
Test releases are not configured to update via Rawhide by default (they follow the [[Releases/Branched|Branched]] version for their release), so you need to first install the "fedora-release-rawhide" package and enable the rawhide repo. You can then run "yum update" or wait for desktop notification of updates.
+
This method may fail if there are upgrade path issues (newer packages in Stable or Branched than Rawhide), or broken dependencies.  
  
If you later want to switch from Rawhide to the final general release, see: https://fedoraproject.org/wiki/Upgrading_from_pre-release_to_final
+
=== Communicating  ===
  
=== Yum update from previous release ===
+
There are a number of ways to communicate with other Rawhide users:
  
This method is available but not recommended for any but the bravest testers.  Anaconda can make changes that are outside what the packaging system can normally deal with.  You may also run into dependency problems which could take time to untangle.  You may also need to upgrade from the immediately previous release (e.g. install Fedora 10, 11, then Fedora 12 Rawhide, not jump directly from Fedora 10 to Fedora 12 Rawhide).  Remember than Rawhide installations in general may need to be wiped and re-installed from scratch at any time.
+
==== IRC ====
  
You can upgrade to the rawhide repository one of two ways. Using graphical applications:
+
Rawhide discussion is on topic and welcome in both the {{fpchat|#fedora-devel}} and {{fpchat|#fedora-qa}} IRC channels.
  
# First, install the {{package|fedora-release|fedora-release-rawhide}} package.
+
==== Mailing Lists ====
# Next, modify your software sources using: <code>gpk-repo</code>
+
#* Leave '''only''' the ''Fedora - Rawhide'' software source enabled
+
# Next, update your system using: <code>gpk-update-viewer</code>
+
  
Alternatively, you may upgrade using the command-line:
+
Rawhide discussion is on topic and welcome in both the {{fplist|test}} and {{fplist|devel}} lists.
  
# Type: <code>yum install fedora-release-rawhide</code>
+
==== Bugzilla ====
# Then type: <code>yum --disablerepo=* --enablerepo=rawhide update</code>
+
  
You may want to enable/disable repositories in /etc/yum.repos.d/ so that only the "Fedora Development" repository is enabledThis will allow daily Rawhide updates to appear by default in desktop notifications and "yum update".
+
Rawhide bugs should be reported against the Fedora Product, rawhide version and the affected componentPlease 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].
  
If you cannot install fedora-release-rawhide from within the package system, you can download the RPM directly from a Rawhide mirror, under: <code>development/rawhide/<arch>/os/Packages/</code>
+
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.
  
===From any release via Preupgrade and Anaconda===
+
== Producing Rawhide ==
  
A faster Anaconda installation can be performed with PreUpgrade.  See [[How to use PreUpgrade]] for instructions; just select "Rawhide" when choosing the version of Fedora you wish to install.
+
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.
  
== Testing Rawhide ==
+
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.
  
There are two important things all Rawhide testers should do. First, read the [https://admin.fedoraproject.org/mailman/listinfo/test test] mailing list, where Rawhide users discuss the latest changes. You'll find discussion of significant changes and warnings of severe breakages here. Reading test-list daily is key to staying on top of Rawhide. Secondly, report all the bugs you find in Rawhide to [http://bugzilla.redhat.com Bugzilla]. Remember to file bugs according to these [[BugsAndFeatureRequests|best practices]]. Please remember that bugs should always be filed in Bugzilla. Reporting bugs on the mailing list or IRC is not sufficient, as these reports rapidly become lost in history. Only on Bugzilla will they always be accessible to other testers and to the developers.
+
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.  
  
Beyond that, here is some general advice which may be of use in using Rawhide:
+
A report for each Rawhide compose is sent to to the {{fplist|test}} and the {{fplist|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.
  
* Approach the test release as a valuable chance to learn more about your system. There is a good chance you will run into some bugs in subsystems or components that you are very unfamiliar with as part of the testing process. Use this an opportunity to learn more about that particular subsystem and get familiar with its documentation. Even documentation has bugs, by following up and trying to learn from the documentation you might be able to help clean up badly worded or out of date documentation as well. The more you learn, the more effective you will be in the future if you participate in the development process again. Be as proactive as you can about reading up on how things work and you will have a much more valuable experience overall.
+
Package maintainers should read and follow the [[Updates_Policy#Rawhide_.2F_devel_.2F_master|Rawhide updates policy]] for building any packages in Rawhide.
* When using yum, take the time to review the list of package actions before you proceed. Don't disable the review step.
+
* Get familiar with the ''/var/log/rpmpkgs'' and ''/var/log/yum.log'' log files.
+
* Get a notebook and make notes about system configuration changes you make. Many problems can be traced to simple configuration errors, but can appear as package update bugs. When working with other testers to confirm the problem, notes as to the other changes you have made since last update/reboot can be invaluable in tracing the problem down accurately.
+
* Keep at least one older kernel around that you are confident works as expected.
+
* Reboot daily, to test to see if any of your updates have affected startup. Its much more difficult to track down a boot up problem that was caused by an old update, if you are updating daily but have not rebooted.
+
* Get familiar with useful grub features for troubleshooting boot up failures.
+
* Don't force or nodeps any package to work around dependency problems. Instead, report them as bugs or to test-list. If no-one reports these problems, they will never get fixed, and will persist into stable releases.
+
* Because the development tree is not guaranteed to be internally consistent every day, you will frequently see ''yum update'' fail with errors. Don't Panic. Most dependency problems will be fixed by the developers in one or two days, sometimes simply by requesting more package rebuilds. If you see a dependency problem with ''yum update'' on your system for several days in a row, and see no discussion of it on test-list, see below to decide whether and how you should report it.
+
* If there is one error (such as a package depending on an old library major) holding you back from a full Rawhide update, you can use ''yum update --skip-broken'' to update all other packages. However, make sure the error has been reported to the maintainer of the offending package.
+
* You might need to disable GPG check in /etc/yum.conf or the fedora-devel repository in /etc/yum.repos.d if packages are incorrectly signed.
+
  
=== When to Report Update Problems ===
+
If needed and approved by [[Fedora_Engineering_Steering_Committee|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.
  
There is a daily build report of the development tree sent to the fedora-test-list every morning as part of the automated push of packages out to the publicly accessible trees. The daily report contains information about new, removed and updated packages. It also contains a summary of known dependency problems for each arch for which the development tree is built for. Please, if you experience any problem updating against the development tree the first thing you should review is the last two or three build reports. If you are seeing a dependency problem summarized in the latest build report, you can be sure the developers are aware of the problem.  Package maintainers receive daily emails when their packages are on this list.
+
Rawhide packages are currently not signed. Work is ongoing to sign at least the majority of them.
  
Note that the broken dependency list which is part of the daily rawhide reports only provides the first layer of dependencies and not the entire list to save build time.  Unlisted packages might also be affected, but fixed when one or more of the listed packages are rebuilt.
+
== Questions and Answers ==
  
If however the problem lingers longer than a few days on your system, and the problem package is not listed in the daily report, that could be an indication that you have run into a situational bug that not everyone is seeing. This is when you can spring into action as a tester and make a difference. But, before you file a new bug report there is a short recipe you can follow to avoid filing unnecessarily. Please remember that test releases exist primarily to help the developers identify problems so they can be fixed in time for release. Unfortunately, reactionary bug filing of duplicate or well known issues can take developer time away from actually fixing issues.
+
'''Q:''' Doesn't rawhide eat babies / kill pets / burn down houses / break constantly?
  
# Read fedora-test-list: Go back into your archives or the web archives for fedora-test-list and read over the threads in the last 48 hours and see if there has been any discussion about the specific update errors you have been seeing. Generally, these sorts of errors are seen by most everyone with similar hardware, so its a very good chance that other testers are already discussing it. Please don't just post a new post to fedora-test-list until after you have reviewed the last 48 hours worth of posts. Having multiple discussions about the same issue is a drain on the time of other testers and developers.
+
A: No. Please stop telling anyone that.  
# Search http://bugzilla.redhat.com: Search to see if there are any reports about the update issue you have seen
+
# Drop a note into fedora-test-list: Please only start a new thread only after you attempted to find previous discussion of this problem in the test-list or in bugzilla. Other testers can help you confirm the problem, or if they can't confirm it they can help you determine if its a configuration problem or user error on your part. The test-list is a great way to assistance from other more experienced testers, but please do what you can to use the archives responsibility to avoid duplication of information and discussion.
+
# File a new bug report: If the exact nature of the dependency problem during updating is lingering for several days or if the problem seems specialized to your situation and it doesn't appear that the developer is aware of this problem.... file a new bug. If you are unsure how to file, experienced testers in fedora-test-list can make suggestions. Please don't assume its a yum bug. Most dependency issues are packaging bugs in one of the packages detailed in the error messages.
+
  
=== What does it mean when something "hits Rawhide"? ===
+
'''Q:''' So Rawhide is very stable and we can all use it?  
  
Rawhide is automatically generated once daily from the latest packages that are built. Packages that are built one day are generally in the next days rawhide.
+
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.  
  
(For the curious, the compose is done at Midnight US Eastern, 0400/0500 UTC.)
+
'''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?
  
=== What is a rawhide "push"? ===
+
A: No. Mixing releases like this is a very bad idea. Your better options are:
  
A rawhide push is simply the rawhide spin for that day. Occasionally, if the push is extremely broken, it may be regenerated more than once.
+
* 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.  
  
=== Where do I communicate issues in Rawhide ? ===
+
'''Q:''' I want to run the rawhide kernel on my Stable Fedora machine. Can I do that?  
  
Use the fedora-test list or #fedora-qa IRC channel in Freenode. For bugs, report them to http://bugzilla.redhat.com
+
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.  
  
=== How can I know what is changing in Rawhide? ===
+
'''Q:''' Is Rawhide a "rolling release" ?
  
Nightly reports are sent to fedora-test-list and fedora-devel-list, with the subject 'rawhide report: <date> changes'.
+
A: It depends on how you define that, but yes.
Included in these reports are what packages have been added, removed, or updated (with short changelog snippets), along with a list of any broken dependencies.
+
  
http://git.fedoraproject.org/ and http://hg.fedoraproject.org/ and https://fedorahosted.org/ are good places to look at
+
'''Q:''' How can I tell when the rawhide compose for the day has finished?
the upstream state of many Fedora projects.
+
  
== Reference ==
+
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.
  
Original press release at http://www.redhat.com/about/presscenter/1998/press_aug1498.html
+
'''Q:''' How do I get out of Rawhide again ? I want to continue on the branch leading to the next release.
 +
 
 +
A: You can simply disable the rawhide repository in /etc/yum.repos.d/rawhide.repo.
 +
 
 +
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.
 +
 
 +
'''Q:''' As a package maintainer do I have to build rawhide packages or does the night 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.
 +
 
 +
== 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 {{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.
 +
 
 +
* 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.
 +
 
 +
== History ==
 +
 
 +
Red Hat Linux "Raw Hide" announcement: [http://lwn.net/1998/0820/rawhide.html on lwn]
 +
 
 +
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:
 +
[[No_Frozen_Rawhide_Proposal]] and branched process which we now follow.

Revision as of 14:37, 25 March 2013

Contents

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

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.

Using Rawhide

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.

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.

Live media

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.

Virtual instances

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.

  1. Download the latest stable or branched install media. (netinstall or DVD install)
  2. Copy to local media (USB or DVD or CD)
  3. Boot media and go to the 'Install Source' section and manually enter:
    https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/x86_64/os/
    (or i386 for 32bit)
  4. 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.

See Upgrading Fedora using yum Rawhide info

This method may fail if there are upgrade path issues (newer packages in Stable or Branched than Rawhide), or broken dependencies.

Communicating

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.

Mailing Lists

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.

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 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?

A: You can see the reports it sends to the test and the devel lists. You can also watch fedmsg for the messages that rawhide compose has finished.

Q: How do I get out of Rawhide again ? I want to continue on the branch leading to the next release.

A: You can simply disable the rawhide repository in /etc/yum.repos.d/rawhide.repo.

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.

Q: As a package maintainer do I have to build rawhide packages or does the night 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.

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.

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 new: No_Frozen_Rawhide_Proposal and branched process which we now follow.