When a package reaches the end of its useful life, the following procedure will let other people -- and automated processes! -- know both not to expect any more releases, and why it was removed. The process is called retirement.
Please execute the following steps in the order indicated.
If the package is being replaced by some other package, ensure that the Obsoletes/Provides tags are properly set by the new package, see Renaming/Replacing Guidelines.
fedpkg retire DESCRIPTION in all non-stable Fedora branches and EPEL
branches, if applicable. The retiring needs to start with the oldest branch
(e.g. retire on f24 before you retire on master)
DESCRIPTIONparameter should explain why the package was retired, good messages are:
Obsoleted by bar
Renamed to bar
- The command will remove all files from the branch, add a file name
dead.packagecontaining the description and push the changes. Starting with fedpkg 1.13 it will also retire the package in package DB.
git rmall files in the other branches only if there are special factors at work, like licensing issues, or package being removed completely from Fedora.
- If you retired master before other older branches you want to retire, just continue with the older branches. It will still work, but will block the package in more Koji tags, because tag inheritance will not be used automatically then.
Ensure that the package is marked as retired in the package database system. This should happen automatically with fedpkg 1.13 and newer if you provide your FAS credentials. If it failed, you can retire the package with the following command:
pkgdb-cli orphan --retire PACKAGENAME master
- After the package was retired in package DB, you will not be able to commit changes to GIT. Therefore clean up GIT first.
masterto the respective branch
- Start with the oldest branch
Remove the package from comps if it is listed.
Remove the package from any spin kickstart file
Upstream Release Monitoring
Remove the package from Upstream_release_monitoring if it is listed.
To keep retired packages from being pushed to the mirrors, they need to be blocked in koji. This will happen during the next Rawhide/Branched compose (also for EPEL). If it did not happen file a
ticket for rel-eng (component
koji) and mention the package name and the branch the package needs to be blocked.
- Please wait long enough before opening a ticket to avoid unnecessary work.
- Use one ticket for all packages you retired at once, do not open one ticket for each package if you retired several packages.
- You check whether a package is blocked in koji, e.g. for the package
currythere should the a entry with
[BLOCKED]for each branch the package was retired in. It is enough for a package to be retired in an older tag to be also blocked in a newer tag due to inheritance:
$ koji list-pkgs --show-blocked --tag f21 --package curry Package Tag Extra Arches Owner ----------------------- ----------------------- ---------------- --------------- curry f20 gemi [BLOCKED]
Note that you can use this process for EPEL as well with one difference:
- You can remove the package from any EPEL branch whether or not it has been released.
For example, if your package has been added to base RHEL in RHEL-6.4 then perform the steps above but use the
el6 branch instead of