However, when building for any of the release branches below rawhide, builds are usually only available once they are pushed to "stable". Often it isn't practical or convenient to wait for this to happen. You can work around this problem by submitting a BuildRoot Override for any package builds you need that haven't yet made it to "stable". This will place the package into the BuildRoot for the branch that you specify, until the expiry date that you specify. During this time, the package is available to be built against. It is good practice to specify an expiry date that is only as long as you need (eg, a few days). It can easily be extended if needed. You can also manually expire the Override before the expiry date.

To submit a BuildRoot override for a package, you need commit access. If you don't have commit access, you can ask the maintainer for the package you are interested in (or a proven packager) to submit the BuildRoot Override for you.

It usually takes about 15 to 30 minutes for a new BuildRoot Override to take effect.

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.