|
|
| Line 1: |
Line 1: |
| = Remove libcap-ng Syslog Patch =
| |
|
| |
|
| {{Change_Proposal_Banner}}
| |
|
| |
| == Summary ==
| |
| Libcap-ng currently syslogs some errors rather than returning an error code. Errors found by syslog messages should have been fixed by now and we should remove the patch.
| |
|
| |
| == Owner ==
| |
| * Name: [[User:sgrubb| Steve Grubb]]
| |
| * Email: sgrubb@redhat.com
| |
| <!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
| |
| * FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
| |
| -->
| |
|
| |
| == Current status ==
| |
| [[Category:ChangePageIncomplete]]
| |
| <!-- When your change proposal page is completed and ready for review and announcement -->
| |
| <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
| |
| <!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) -->
| |
| <!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete-->
| |
|
| |
| [[Category:SystemWideChange]]
| |
|
| |
| * Targeted release: [https://docs.fedoraproject.org/en-US/releases/f40/ Fedora Linux 40]
| |
| * Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}
| |
| <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page
| |
| Bugzilla state meanings:
| |
| ASSIGNED -> accepted by FESCo with ongoing development
| |
| MODIFIED -> change is substantially done and testable
| |
| ON_QA -> change is fully code complete
| |
| -->
| |
| * [<will be assigned by the Wrangler> devel thread]
| |
| * FESCo issue: <will be assigned by the Wrangler>
| |
| * Tracker bug: <will be assigned by the Wrangler>
| |
| * Release notes tracker: <will be assigned by the Wrangler>
| |
|
| |
| == Detailed Description ==
| |
| <!-- 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. -->
| |
|
| |
| == Benefit to Fedora ==
| |
| Libcap-ng would match upstream code and probably other distributions. Developers can better detect actual errors.
| |
|
| |
| == Scope ==
| |
| * Proposal owners:
| |
| Create a modified patch that still sends an error message to syslog while returning and error code. Later, remove the patch.
| |
|
| |
| * Other developers:
| |
| If you have a package with a direct dependency on libcap-ng-devel, then you should check syslog after exercising the application that uses it. If any message from libcap-ng is found, it will need to be corrected. Also, you should scan your build logs to see if there are any warnings about unused results related to any function names starting with capng_
| |
|
| |
| * Release engineering: [https://pagure.io/releng/issues #Releng issue number] <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
| |
| Not affected.
| |
|
| |
| * Policies and guidelines: N/A
| |
|
| |
| * Trademark approval: N/A
| |
|
| |
| * Alignment with Community Initiatives: N/A
| |
|
| |
| == Upgrade/compatibility impact ==
| |
| There should be no impact.
| |
|
| |
| == How To Test ==
| |
| <!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be.
| |
|
| |
| Remember that you are writing this how to for interested testers to use to check out your change implementation - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your change.
| |
|
| |
| A good "how to test" should answer these four questions:
| |
|
| |
| 0. What special hardware / data / etc. is needed (if any)?
| |
| 1. How do I prepare my system to test this change? What packages
| |
| need to be installed, config files edited, etc.?
| |
| 2. What specific actions do I perform to check that the change is
| |
| working like it's supposed to?
| |
| 3. What are the expected results of those actions?
| |
| -->
| |
|
| |
| <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
| |
|
| |
|
| |
| == User Experience ==
| |
| If testing went well, this change should be unnoticed by the end user.
| |
|
| |
| == Dependencies ==
| |
| <!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this change depends? In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel change)? -->
| |
|
| |
| <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
| |
|
| |
|
| |
| == Contingency Plan ==
| |
|
| |
| * Contingency mechanism: Reapply the original patch
| |
| * Contingency deadline: beta freeze
| |
| * Blocks release? No
| |
|
| |
|
| |
| == Documentation ==
| |
| <!-- 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 -->
| |
| N/A (not a System Wide Change)
| |
|
| |
| == Release Notes ==
| |
| <!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are at https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/ -->
| |
| <!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this change, indicate them here. A link to upstream documentation will often satisfy this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release.
| |
|
| |
| Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.
| |
| -->
| |
