Buildroot override SOP
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 reporeted 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
method of Koji.
$ koji tag-pkg --help Usage: koji tag-pkg [options] <tag> <pkg> [<pkg>...] (Specify the --help global option for a list of other help options) Options: -h, --help show this help message and exit --force force operation --nowait Do not wait on task
For example, if we were asked to make libwnck-2.18.2-2.f13 available in the F13 buildroots we would issue:
$ koji tag-pkg --force dist-f13-override libwnck-2.18.2-2.fc13
Important to notice that we used the
option. This is necessary as the -override tags are locked. Only admins are allowed to tag packages for these collections.
By convention override tags start with the base collection,
in this case, and end in
To verify that the tag was successful and the build will be available in the buildroot use the
$ 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
- Once dependant builds are done, the -override should be cleared. Use
to accomplish this.
- Periodically check the -override tag for stale tags via
found in Fedora releng git.