Description
Packages are often retired or renamed from Fedora. When this happens, release engineering needs to "block" the package from being published and inherited in various koji tags.
Action
Find Block requests
Block 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 block 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 blocking
Discover proper place to block
The ticket should tell you which Fedora releases to block the package in. Typically it'll say "Fedora 13" or "F14". This means we need to block it at that Fedora level and all future tags. However we do not block packages in a Fedora release that has gone public unless.
The appropriate place to block a package is at the "f??" tag level. This way the setting of block or not is inherited into future tags.
Performing the package block
To block a package for a tag, use the block-pkg method of Koji.
$ koji block-pkg --help Usage: koji block-pkg [options] tag package [package2 ...] (Specify the --help global option for a list of other help options) Options: -h, --help show this help message and exit
For example, if we were asked to block python-psyco in Fedora 20 we would issue:
$ koji block-pkg f20 python-psyco
Now the ticket can be closed.
Verification
To verify that the package was successfully blocked use the list-pkgs koji command:
$ koji list-pkgs --show-blocked --package python-psyco
We should see the package listed as blocked:
Package Tag Extra Arches Owner ----------------------- ----------------------- ---------------- --------------- python-psyco f20 konradm [BLOCKED]
We should not see it listed in any later Fedora tags.
Consider Before Running
- Don't block packages in a released Fedora unless it is a rename. We cannot remove the package from the release repository
- Watch the next day's rawhide/branched/whatever report for a slew of broken deps related to the package. We may have to unblock the package in order to fix the deps.