|
|
| (45 intermediate revisions by 17 users not shown) |
| Line 1: |
Line 1: |
| {{autolang|base=yes}} | | {{admon/warning |This page has been moved out of the wiki. The current version of this document is located at https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/ Please update your bookmarks.}} |
| | |
| 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 simple.
| |
| | |
| == Procedure ==
| |
| | |
| Please execute the following steps in the order indicated.
| |
| | |
| # Make sure the package is properly Obsoleted/Provided by something '''if''' it is being replaced, see [[Packaging:Guidelines#Renaming.2FReplacing_Existing_Packages|Renaming/Replacing Guidelines]]. If not, go on to the next step.
| |
| # Run <code>fedpkg retire MSG</code>. This will recursively remove all files, then add a <code>dead.package</code> file to git. This should be done for <code>master</code> and sometimes the branched release if it has not yet released ('''Do not''' do this for released Fedora versions as there's no way to remove the package from end-user's systems) . The MSG parameter is a message which should briefly explain where this package went ('Obsolete package', 'Renamed to bar' or the like) and will be written in the dead.package file.
| |
| # <code>git rm</code> all files in the other branches '''only if''' there are special factors at work, like licensing issues, or package being removed completely from Fedora.
| |
| # Remove the package from [[How_to_use_and_edit_comps.xml_for_package_groups| comps]] if it is listed.
| |
| # Check for and remove the package from any spins kickstarts files: http://git.fedorahosted.org/git/spin-kickstarts.git
| |
| # Do '''not''' execute this step if you have not already completed steps 2 and 3, otherwise you will have to ask a [[Provenpackager policy|provenpackager]] to perform those steps for you. Mark the package as "retired" in [https://admin.fedoraproject.org/pkgdb the package database system]: log in with your FAS credentials, go to the page for your package, and click the '''Retire package''' button for each branch on which you are retiring the package.
| |
| # If the package was registered on [[Upstream_release_monitoring]], remove it from that page
| |
| # File a [https://fedorahosted.org/rel-eng/newticket ticket] for rel-eng (component <code>koji</code>) asking the package (or packages if there are many) to be blocked from the appropriate collections in which it is retired. You can mention several packages in one ticket.
| |
| | |
| == EPEL ==
| |
| Note that you can use this process for EPEL as well with a few differences:
| |
| | |
| * You can remove the package from any EPEL branch whether or not it has been released.
| |
| * The component for the rel-eng ticket is <code>epel</code> rather than <code>koji</code>.
| |
| | |
| For example, if your package has been added to base RHEL in RHEL-6.4 then perform the steps above but use the <code>el6</code> branch instead of <code>master</code>. When you open your rel-eng ticket to have the package blocked, use component <code>epel</code> instead of <code>koji</code>.
| |
| | |
| [[Category:Package Maintainers]]
| |
| [[Category:Packaging guidelines]]
| |
