From Fedora Project Wiki

m (Master to rawhide)
(Move policy material to separate page, link there)
Line 1: Line 1:

== About Orphan and Retired (Deprecated) Packages ==
This page contains instructions for working with orphan packages as specified in [[Policy for Orphan and Retired Packages]].
When Fedora maintainers do not want or are not able to maintain a package any
longer, they can orphan or [[How_to_remove_a_package_at_end_of_life|retire]] the
package. When they think that the package is still useful for Fedora, they
should orphan it. Then other maintainers that are interested in maintaining it,
can take ownership of this package. In case the package is no longer useful for
Fedora, e.g. because it was renamed, upstream does not exist anymore, then it
should be retired. But this is only possible for development releases such as Branched or Rawhide.
Orphaned packages remain in stable releases and are the responsibility of the collective packaging community to maintain.
{{admon/warning|Retiring packages|Orphan packages will be retired if they remain orphaned for six weeks. Packages will be retired in Fedora Rawhide and Branched (until the Beta Freeze).}}
{{admon/warning|When to orphan and retire your packages|We encourage maintainers considering orphaning their packages to do it as early in the development cycle as possible. Shortly after the prior release is branched is a good time.}}

== Orphaning Procedure ==
== Orphaning Procedure ==
Line 34: Line 20:

== Claiming Ownership of a Retired Package ==
== Claiming Ownership of a Retired Package ==
{{admon/warning|Un-Retiring long-time retired packages|Packages that are retired for Rawhide for more than 8 weeks need to be reviewed again before they can be un-retired. This is also true for EPEL-only packages.}}

If you really want to maintain a retired package, you need to be aware that
If you really want to maintain a retired package, you need to be aware that
Line 53: Line 38:
*  [ A list of currently orphaned and/or retired packages]
*  [ A list of currently orphaned and/or retired packages]

== References ==
[[Category:Package Maintainers]]
=== EPEL ===
[[Category:Package Maintainers]] [[Category:Policy]]

Revision as of 11:46, 14 June 2021

This page contains instructions for working with orphan packages as specified in Policy for Orphan and Retired Packages.

Orphaning Procedure

  1. If the package has co-maintainers, contact them to ask whether one of them wants to take over ownership of the package. This step is optional. If no co-maintainer can be found to take over the package, the package should be given to the "orphan" user.

    The current list of maintainers can be found in the "Users & Groups" tab of the setting for the package repo. The URL will look something like this —
  2. After the first step is finished, go again to the settings tab for your package's Pagure repository. Navigate down to the Give Project section and "give" the project to the new maintainer or the "orphan" user (in case no new maintainer was selected).
  3. For completeness, under the Users and Groups section, remove yourself from the list as well.
  4. Also reset your watch status if you do not want to be CC'ed on new package bugs.
  5. If the package was given to the "orphan" user, announce on devel which package you orphaned, so that others have a chance to take over as maintainer.
  6. Reassign the package's tickets to the orphan user,

Claiming Ownership of an Orphaned Package

  1. Check why the package was orphaned by looking for the email to devel.
  2. Announce on devel which packages you want to take over.
  3. Log in to On the page with the orphaned package, click the ✋ Take button in the left column. (If the option doesn't work for you, submit a ticket to the Release Engineering team, stating which package you want to claim and that this option didn't work.)
  4. Reassign and claim all open bug reports for the package in Bugzilla.

Claiming Ownership of a Retired Package

If you really want to maintain a retired package, you need to be aware that if upstream is dead, fixing release critical bugs, etc becomes your responsibility. This is to ensure the high quality and standards of packaging remain for Fedora package collection. There may be additional issues with retired packages. If possible, consult with the former maintainer for more information. The process is a bit different from unorphaning a package

  1. See if you can figure out why the package was retired including searching for information about orphaned packages on devel mailing list or emailing the former maintainer. You can also check dead.package in the SCM (url like:
  2. Announce on devel which packages you would like to become the owner of.
  3. Retired Fedora packages (rawhide branch retired) require a re-review if they are retired for more than eight weeks or if there is no previous review of the package. Submit a review request (a new bugzilla ticket) and have the package approved by a reviewer as if it were new to Fedora. See the package review process for more information. To unretire a EPEL branch if the package is still in Fedora, no re-review is required.
  4. Request unretirement by filing a releng ticket. Specify all branches that need to be un-retired (inlcuding "rawhide" for Rawhide, unless it is for EPEL only) and include the link to re-review. In this ticket, request that the Release Engineering team unblock the package for the releases that the package should be un-retired for. In this request, clearly specify which branches should be unblocked.
  5. Restore the contents in GIT and prepare a new build and update (if necessary).

Lists of Orphan and Retired Packages