azurelinux
azurelinux copied to clipboard
edk2: package upgrade to 202402
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 theirRelease
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 (
./SPECS/LICENSES-AND-NOTICES/data/licenses.json
,./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md
,./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON
) - [ ] All source files have up-to-date hashes in the
*.signatures.json
files - [ ]
sudo make go-tidy-all
andsudo make go-test-coverage
pass - [ ] Documentation has been updated to match any changes to the build system
- [ ] Ready to merge
Summary
What does the PR accomplish, why was it needed?
Change Log
- upgrade to 202402, including upfating .patch files, .spec file and sources files
- removed patches no longer work for bundled openssl, and update a patch for newer ver of openssl
- bring a patch from 2.0 to this pr to get into 3.0-dev
Does this affect the toolchain?
YES/NO
Associated issues
- #xxxx
Links to CVEs
- https://nvd.nist.gov/vuln/detail/CVE-YYYY-XXXX
Test Methodology
- Pipeline build id: xxxx