Carlwgeorge (talk | contribs) (provides are not required for upgrade path https://fedoraproject.org/wiki/Upgrade_paths_%E2%80%94_renaming_or_splitting_packages#Do_I_need_to_Provide_my_old_package_names.3F) |
Carlwgeorge (talk | contribs) (I was mistaken with my last change, turns out that only applies to font packages.) |
||
| Line 5: | Line 5: | ||
When you wish to rename a package, you '''MUST''' request a re-review of your package through the [[Package Review Process|normal review process]]. In this review request, you '''MUST''' state that this is a re-review request for a package rename, and the old package name that this is replacing. | When you wish to rename a package, you '''MUST''' request a re-review of your package through the [[Package Review Process|normal review process]]. In this review request, you '''MUST''' state that this is a re-review request for a package rename, and the old package name that this is replacing. | ||
The reviewer of the package '''MUST''' explicitly acknowledge this fact, and check the package for the proper Obsoletes (see [[Packaging:NamingGuidelines#Renaming.2Freplacing_existing_packages|the naming guidelines]] for more information.) They '''MUST''' document in the review request that they have done so. | The reviewer of the package '''MUST''' explicitly acknowledge this fact, and check the package for the proper Obsoletes and Provides (see [[Packaging:NamingGuidelines#Renaming.2Freplacing_existing_packages|the naming guidelines]] for more information.) They '''MUST''' document in the review request that they have done so. | ||
== After the review == | == After the review == | ||
Revision as of 16:29, 1 October 2018
For a variety of reasons it may become necessary to rename a package in Fedora. The goal of this page is to outline the process that must be followed when such an event occurs.
Re-review required
When you wish to rename a package, you MUST request a re-review of your package through the normal review process. In this review request, you MUST state that this is a re-review request for a package rename, and the old package name that this is replacing.
The reviewer of the package MUST explicitly acknowledge this fact, and check the package for the proper Obsoletes and Provides (see the naming guidelines for more information.) They MUST document in the review request that they have done so.
After the review
After the review is completed, and is satisfactory (for the avoidance of doubt, the lack of a clean upgrade path for users of the package in the form of proper Provides and Obsoletes is considered a blocker to the review), request git for the package as you normally would for a new package.
After the new package is imported into git, you can then follow the package retirement process for the old package.