OOT Modules -> Add kernel version and release nb into release nb

[nicogbg]

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

OOT Modules -> Add kernel version and release nb into release nb

Change Log

• Change
• Change
• Change

Does this affect the toolchain?

NO

Associated issues

• #xxxx

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-YYYY-XXXX

Test Methodology

• Pipeline build id: xxxx

[PawelWMS]

Nit-pick:

Suggested change

	Name: %{_name}-signed
	Name: %{_name}-signed

[PawelWMS]

Suggested change

	Release: 17%{release_suffix}%{?dist}
	Release: 17%{release_suffix}%{?dist}

[binujp]

Looks good, I focused on the spec changes and less so on the validation scripts.

[binujp]

Thanks for all the efforts in pushing this change, Nicolas! Have we made sure the new version schema is upgradable from the existing one? i.e. "rpm upgrade" of the new versioned package replaces the existing one.

[Copilot]

Pull Request Overview

This PR updates several SPEC files and related workflow scripts to incorporate dynamic kernel version extraction and release suffix generation. The changes replace hardcoded kernel version strings with dynamically queried values using RPM macros and update dependent package declarations and changelogs accordingly.

• Updated kernel version extraction macros in SPEC files.
• Updated BuildRequires/Requires fields to use the new computed macro (_mofed_full_version).
• Adjustments to GitHub workflow scripts to handle chroot environments for cgmanifest validation.

Reviewed Changes

Copilot reviewed 23 out of 23 changed files in this pull request and generated 1 comment.

File	Description
SPECS/*	Updated kernel version extraction and release suffix macros in multiple SPEC files.
.github/workflows/*	Adjusted workflow scripts to incorporate chroot-based spec parsing and improved error handling.
Others	Changelog and dependency changes for new kernel version details.

Comments suppressed due to low confidence (1)

.github/workflows/validate-cg-manifest.sh:194

• Ensure that the alternate source URL variable is consistently named (e.g. 'source0_alt') throughout the script to improve code clarity and avoid confusion with any legacy variable names.

+  source0_alt=""

[Copilot]

Consider refactoring the repeated kernel version extraction macros (including target_kernel_version_full, target_azl_build_kernel_version, target_kernel_release, and release_suffix) into a common include file to reduce duplication across the SPEC files and ease future maintenance.

[christopherco]

Generally looks fine. Please consider my comments on consolidating duplicated version and release values into individual macros/defines within spec so that it reduces the probability of desync due to human error on update.

[christopherco]

If the release number were to get incremented due to a change to the spec, this value would need to change too, correct?
If so, would it make sense to make the release number also a %define so there is only one spot to update in the spec when incrementing the release number? I can see someone inadvertently missing this, and causing the requires _mofed_full_version go out of sync with the package itself.

[christopherco]

Should this use %{_version} so this value is controlled by one define?