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

Include release number in kernel version entanglement check #12161

Draft
wants to merge 8 commits into
base: 3.0-dev
Choose a base branch
from

Conversation

binujp
Copy link
Contributor

@binujp binujp commented Jan 31, 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

What does the PR accomplish, why was it needed?

Change Log
  • Change
  • Change
  • Change
Does this affect the toolchain?

YES/NO

Associated issues
  • #xxxx
Links to CVEs
Test Methodology
  • Pipeline build id: xxxx

@microsoft-github-policy-service microsoft-github-policy-service bot added Packaging Tools 3.0-dev PRs Destined for AzureLinux 3.0 labels Jan 31, 2025
rlmenge and others added 7 commits January 31, 2025 20:33
Enable support for ipmitool. ipmitool is available through the ipmitool package on AzureLinux. The config changes in this PR ensure the devices created are visible in /dev/. From the ipmitool project: "ipmitool is a utility for managing and configuring devices that support the Intelligent Platform Management Interface. IPMI is an open standard for monitoring, logging, recovery, inventory, and control of hardware that is implemented independent of the main CPU, BIOS, and OS."

Co-authored-by: Thomas Ballasi <[email protected]>
Updates SymCrypt to 103.8.0 with ML-DSA and changes for FIPS
Updates SymCrypt-OpenSSL to 1.7.0 with minor bugfixes, configurable debug logging, and KeysInUse logging (off by default)
…age to libs (#12176)

openssl has a Recommends on SymCrypt and SymCrypt-OpenSSL. However, it's actually the subpackage openssl-libs that needs these and we have a customer that sees these not being installed if they only install openssl-libs on a minimal container. This change moves the Recommends from the main package to the libs subpackage
Signed-off-by: Kshitiz Godara <[email protected]>
Co-authored-by: Kshitiz Godara <[email protected]>
Signed-off-by: Mayank Singh <[email protected]>
Co-authored-by: Mayank Singh <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3.0-dev PRs Destined for AzureLinux 3.0 Packaging Tools
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants