Skip to content

Conversation

@bfjelds
Copy link
Member

@bfjelds bfjelds commented Jan 6, 2026

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

Create Trident RPM

Change Log
  • Create SPECS/trident spec, signatures, etc
Does this affect the toolchain?

NO

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

could include the installation of certain RPMs, updating the SELinux mode, and
enabling DM-Verity.

%package osmodifier
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can trident include osmodifier without adding a subpackage?

@@ -0,0 +1,8 @@
{
"Signatures": {
"azurelinux-image-tools-1.0.0.tar.gz": "fac3fd48c1e0527109239deb8f4df7a526513409fa7474d1d7ffac978c1521d1",
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove azurelinux-image-tools tarballs


%build
%if %{undefined rpm_ver}
export TRIDENT_VERSION="%{version}-%{release}"
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

version will be: 0.20.0-1.azl3

should we include release?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3.0 PRs Destined for 3.0 Packaging

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants