Buildroot override SOP

Description
As it currently stands, the buildroots used for Fedora updates building are not self updating. They only contains things from the release, and stable released updates. This means that one update candidate cannot be built against another update candidate without rel-eng interaction. That interaction is to tag a build for an "override" collection which will make it available in the buildroot for future builds.

Find tag requests
Tag requests are usually reported in the rel-eng trac instance at Fedorahosted in the component koji. You can use a trac query to list all unassigned Koji tickets. This query also includes requests, that are not a tag request, because there is no automated way to distinguish them. The results of the query are also available as an RSS feed, the link is in the footer of the page.

Perform the tagging
First assign the ticket to yourself to show, that you are handling the request. Then to tag a package for an override collection, use the           tag is empty. You need to use  instead. E.g. }}

To check several releases at once, use a bash for loop: $ for release in {12..13}; do ./clean-overrides.py dist-f$release-{override,updates}; done

Verification
To verify that the tag was successful and the build will be available in the buildroot use the  koji command: $ koji latest-pkg dist-f13-build libwnck Build                                    Tag                   Built by libwnck-2.18.2-2.fc13                     dist-f13-override     rhughes We should see the build nvr we tagged, and see that it is coming from the -override tag.

Consider Before Running

 * Once tagged, new repodata may take 20~ minutes to generate and the build to be available in buildroots.
 * Buildroot overrides usually means that something is soname bumping. Be sure this is a sane update to do in Fedora