Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cleanup for gnutls spec and patches #11906

Closed
wants to merge 1 commit into from
Closed

Cleanup for gnutls spec and patches #11906

wants to merge 1 commit into from

Conversation

gjswalling
Copy link
Contributor

@gjswalling gjswalling commented Jan 14, 2025

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

  • The toolchain has been rebuilt successfully (or no changes were made to it)
  • The toolchain/worker package manifests are up-to-date
  • Any updated packages successfully build (or no packages were changed)
  • Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
  • Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
  • All package sources are available
  • cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
  • LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
  • All source files have up-to-date hashes in the *.signatures.json files
  • sudo make go-tidy-all and sudo make go-test-coverage pass
  • Documentation has been updated to match any changes to the build system
  • Ready to merge

Summary

Cleanup for gnutls spec and patches

Change Log
  • remove unused patch files
  • fix changelog date in spec file
Does this affect the toolchain?

NO

Test Methodology
  • Pipeline build id: 715962

@gjswalling gjswalling marked this pull request as ready for review January 21, 2025 18:09
@gjswalling gjswalling requested a review from a team as a code owner January 21, 2025 18:09
@gjswalling
Copy link
Contributor Author

CVE was resolved on scanner side, and it's not worth going through shiproom for this cleanup...abandoning

@gjswalling gjswalling closed this Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
main PR Destined for main Packaging
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant