From Fedora Project Wiki

< Bodhi

Revision as of 13:40, 26 August 2013 by Jamielinux (talk | contribs) (Add information about what buildroot overrides actually are and why you would need it)

What is a BuildRoot Override

Sometimes a package you are trying to build can't be done until another package that it depends on is updated. When building packages for rawhide, successful builds become available fairly soon after they complete. These packages can then be used to build other packages against.

However, when building for any of the release branches below rawhide, builds are usually only available once they are pushed to "stable". You can work around this problem by submitting a BuildRoot Override for this particular build. This will place it into the BuildRoot for the branch that you specify, until the date that you specify. During this time, the package is available to be built against.

Using Bodhi to manage Koji Buildroot Overrides

This document describes how to manage your Koji BuildRoot Overrides using Bodhi. Each section contains URLs for performing actions via the web and commands for doing it from the console.

Legacy method
Legacy method/backup plan: submit releng ticket:

Submitting a new override

    bodhi --buildroot-override=<name-version-release> --duration=5 --notes="Useful details."

Viewing your own overrides

    bodhi --my-overrides [--show-expired]

Viewing all overrides

    bodhi --list-overrides [--show-expired]

Manually expiring your buildroot override<name-version-release>

    bodhi --expire-override=<name-version-release>

Extending your duration or editing override notes<name-version-release>

    bodhi --edit-override=<name-version-release> --duration=10 --notes="Oh hai"