From Fedora Project Wiki

(→‎Procedure: update to current situation)
(Replaced content with "{{admon/warning |This page has been moved out of the wiki. The current version of this document is located at")
Tag: Replaced
(44 intermediate revisions by 17 users not shown)
Line 1: Line 1:
{{admon/warning |This page has been moved out of the wiki. The current version of this document is located at 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 and retire the package in package DB (requires fedpkg 1.13 or newer).  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 ('Package obsoleted by bar', '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:
# Not necessary with fedpkg 1.13 or newer: 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 [ 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 [ 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. (There is a experimental service that takes care of this, therefore please only create a ticket if the package is not blocked in koji five minutes after it has been retired in package DB). Check whether it is blocked with koji, e.g. for the package <code>curry</code> there should the a entry with <code>[BLOCKED]</code> for each branch the package was retired in:
$ koji list-pkgs  --show-blocked --tag f21 --package curry                             
Package                Tag                    Extra Arches    Owner         
----------------------- ----------------------- ---------------- ---------------
curry                  f20                                      gemi            [BLOCKED]
== 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]]

Revision as of 06:10, 7 September 2021

This page has been moved out of the wiki. The current version of this document is located at Please update your bookmarks.