Latest revision as of 08:46, 11 March 2022

Retired Packages

Summary

Ease the task of removing packages, which were retired and no longer receives updates.

Owner

Name: Miroslav Suchý
Email: msuchy@redhat.com

Current status

Targeted release: Fedora Linux 36
Last updated: 2022-03-11
FESCo issue: #2679
Tracker bug: #2018192
Release notes tracker: #759

Updated packages are present in rawhide and in referenced Copr repository.

Subpackage remove-retired-packages has been submitted to Fedora 35 to allow seamless online upgrades from Fedora 35 to 36.

Detailed Description

This follows the Changes/Fedora-Retired-Packages which was withdrawn. This time I provide a script remove-retired-packages (presented in the package of the same name) which identifies packages retired between N-1 and current (N) version. Alternatively, user can run:

   remove-retired-packages 32

which will look for packages between Fedora Linux 32 and the current version.

The packages are suggested to be removed one by one, which allows the admin to skip the package and keep it on their machine despite being retired.

Part of this proposal is to change the documentation for the upgrade.

Feedback

See Changes/Fedora-Retired-Packages#Feedback original feedback page

Discussion on devel mailing list prior this proposal.

Benefit to Fedora

We suggest users to remove packages that are no longer maintained and may contain security vulnerabilities.
We make sure that archaic packages do not break upgrade between two versions of Fedora.

Scope

Proposal owners:

Subpackage remove-retired-packages has been created (subpackage of fedora-upgrade).

Other developers: N/A (not needed for this Change)

Release engineering: N/A (not needed for this Change)

Policies and guidelines: N/A (not needed for this Change)

Edit of https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/#sect-optional-post-upgrade-tasks - will be done after approval from FESCO.

Trademark approval: N/A (not needed for this Change)

Alignment with Objectives: N/A

Upgrade/compatibility impact

No direct impact.

How To Test

   dnf copr enable msuchy/remove-retired-packages 
   dnf install remove-retired-packages
   remove-retired-packages

User Experience

Packages that are no longer maintained are removed during a distribution upgrade.

Dependencies

None.

Contingency Plan

Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
Contingency deadline: N/A (not a System Wide Change)
Blocks release? N/A (not a System Wide Change), Yes/No

Documentation

Documentation for upgrade guide https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/#sect-clean-up-retired-packages [Pull Request]

Release Notes

Suggested wording:

Previously a package retired in Fedora Linux has been removed from repositories, but it remains installed on a user computer. Such packages never receive an update. Not even a security update. We now provide package remove-retired-packages with the tool of the same name which suggests you to remove such packages. The upgrade guide has been amended with steps how to remove retired packages. It is as easy as:

   sudo dnf install remove-retired-packages
   remove-retired-packages

@@ Line 1: / Line 1: @@
-{{admon/tip | Guidance | For details on how to fill out this form, see the [https://docs.fedoraproject.org/en-US/program_management/changes_guide/ documentation].}}
 <!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
-= Change Proposal Name =
+= Retired Packages =
 <!-- The name of your change proposal -->
 == Summary ==
-Easy the task of removing packages, which were retired and no longer receives updates.
+Ease the task of removing packages, which were retired and no longer receives updates.
 <!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. Note that motivation for the change should be in the Benefit to Fedora section below, and this part should answer the question "What?" rather than "Why?". -->
@@ Line 24: / Line 22: @@
 == Current status ==
-[[Category:ChangePageIncomplete]]
+[[Category:ChangeAcceptedF36]]
 <!-- When your change proposal page is completed and ready for review and announcement -->
 <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
@@ Line 42: / Line 40: @@
 ON_QA -> change is fully code complete
 -->
-* FESCo issue: <will be assigned by the Wrangler>
+* FESCo issue: [https://pagure.io/fesco/issue/2679 #2679]
-* Tracker bug: <will be assigned by the Wrangler>
+* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=2018192 #2018192]
-* Release notes tracker: <will be assigned by the Wrangler>
+* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/759 #759]
+Updated packages are present in rawhide and in referenced Copr repository.
+Subpackage `remove-retired-packages` [https://bodhi.fedoraproject.org/updates/FEDORA-2022-bd7e9b853f has been submitted to Fedora 35] to allow seamless online upgrades from Fedora 35 to 36.
 == Detailed Description ==
-This follows the [[Changes/Fedora-Retired-Packages]] which was withdrawn. This time I provide a script `remove-retired-packages` (presented in the package of the same name) which identifies packages retired between N-1 and current (N) version. Alternatively user can run:
+This follows the [[Changes/Fedora-Retired-Packages]] which was withdrawn. This time I provide a script `remove-retired-packages` (presented in the package of the same name) which identifies packages retired between N-1 and current (N) version. Alternatively, user can run:
      remove-retired-packages 32
@@ Line 55: / Line 57: @@
 The packages are suggested to be removed one by one, which allows the admin to skip the package and keep it on their machine despite being retired.
-Part of this proposal is to change [[https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/#sect-optional-post-upgrade-tasks the documentation for the upgrade]].
+Part of this proposal is to change [https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/#sect-optional-post-upgrade-tasks the documentation for the upgrade].
 <!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
 == Feedback ==
 <!-- Summarize the feedback from the community and address why you chose not to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised gives FESCo a clearer view of your proposal and leaves a good record for the future. If you get no feedback, that is useful to note in this section as well. For innovative or possibly controversial ideas, consider collecting feedback before you file the change proposal. -->
+See [[Changes/Fedora-Retired-Packages#Feedback original feedback page]]
+[https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/XQMUSHK7HX65LQUJBFDNY47YPMCPI5MG/#XQMUSHK7HX65LQUJBFDNY47YPMCPI5MG Discussion] on devel mailing list prior this proposal.
 == Benefit to Fedora ==
@@ Line 89: / Line 95: @@
       https://fedoraproject.org/wiki/Changes/perl5.26 (major upgrade to a popular software stack, visible to users of that stack)
 -->
+* We suggest users to remove packages that are no longer maintained and may contain security vulnerabilities.
+* We make sure that archaic packages do not break upgrade between two versions of Fedora.
 == Scope ==
 * Proposal owners:
 <!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
+Subpackage `remove-retired-packages` has been created (subpackage of `fedora-upgrade`).
-* Other developers: <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Other developers: N/A (not needed for this Change)
 <!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
-* Release engineering: [https://pagure.io/releng/issues #Releng issue number] <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Release engineering: N/A (not needed for this Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuild required?  include a link to the releng issue.
 The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->
@@ Line 103: / Line 113: @@
 * Policies and guidelines: N/A (not needed for this Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 <!-- Do the packaging guidelines or other documents need to be updated for this feature?  If so, does it need to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. Please submit a pull request with the proposed changes before submitting your Change proposal. -->
+Edit of https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/#sect-optional-post-upgrade-tasks - will be done after approval from FESCO.
 * Trademark approval: N/A (not needed for this Change)
 <!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://pagure.io/Fedora-Council/tickets/issues ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. -->
-* Alignment with Objectives:
+* Alignment with Objectives: N/A
 <!-- Does your proposal align with the current Fedora Objectives: https://docs.fedoraproject.org/en-US/project/objectives/ ? It's okay if it doesn't, but it's something to consider -->
@@ Line 114: / Line 125: @@
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+No direct impact.
 == How To Test ==
@@ Line 133: / Line 144: @@
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+    dnf copr enable msuchy/remove-retired-packages
+    dnf install remove-retired-packages
+    remove-retired-packages
 == User Experience ==
@@ Line 145: / Line 159: @@
   - Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system.
 -->
+Packages that are no longer maintained are removed during a distribution upgrade.
 == Dependencies ==
@@ Line 150: / Line 165: @@
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+None.
 == Contingency Plan ==
@@ Line 165: / Line 180: @@
 <!-- Is there upstream documentation on this change, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+Documentation for upgrade guide https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/#sect-clean-up-retired-packages [[https://pagure.io/fedora-docs/quick-docs/pull-request/427 Pull Request]]
-N/A (not a System Wide Change)
 == Release Notes ==
@@ Line 174: / Line 188: @@
 Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.
 -->
+Suggested wording:
+Previously a package retired in Fedora Linux has been removed from repositories, but it remains installed on a user computer. Such packages never receive an update. Not even a security update. We now provide package `remove-retired-packages` with the tool of the same name which suggests you to remove such packages. The upgrade guide has been amended with [https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/#sect-clean-up-retired-packages steps how to remove retired packages].
+It is as easy as:
+    sudo dnf install remove-retired-packages
+    remove-retired-packages

Search

Changes/RetiredPackages: Difference between revisions