Skip to content

fix: rust-nalgebra0.33: fix upstream-name to match component name#16487

Merged
christopherco merged 1 commit intotomls/base/mainfrom
bphilip/rust-nalgebra0.33
Apr 7, 2026
Merged

fix: rust-nalgebra0.33: fix upstream-name to match component name#16487
christopherco merged 1 commit intotomls/base/mainfrom
bphilip/rust-nalgebra0.33

Conversation

@binujp
Copy link
Copy Markdown
Contributor

@binujp binujp commented Apr 7, 2026

rust-nalgebra0.33: fix upstream-name to match component name

koji/taskinfo?taskID=1128253
closed buildSRPMFromSCM (/microsoft/azurelinux.git:35989ceaada603bdde40bb8c668863f7cceb76b3)
closed buildArch (rust-nalgebra0.33-0.33.2-1.azl4bootstrap.20260405.src.rpm, x86_64)
closed buildArch (rust-nalgebra0.33-0.33.2-1.azl4
bootstrap.20260405.src.rpm, aarch64)

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

Copilot AI review requested due to automatic review settings April 7, 2026 03:04
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Updates the Azure Linux component definition for rust-nalgebra0.33 to correct how the Fedora dist-git source is referenced for the pinned Fedora 43 snapshot.

Changes:

  • Update spec.upstream-name for rust-nalgebra0.33 to rust-nalgebra0.33.
  • Update the pinned spec.upstream-commit SHA for the Fedora 43 source.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@@ -2,4 +2,4 @@
# Pin to the f43 commit used to build the current Fedora 43 package.
Copy link

Copilot AI Apr 7, 2026

Choose a reason for hiding this comment

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

The spec pin uses upstream-commit but the surrounding comment block doesn’t include a reference URL to the exact Fedora dist-git commit being pinned (and why), which makes it hard to audit/refresh later. Please add a full link (e.g., https://src.fedoraproject.org/rpms/rust-nalgebra0.33/c/<sha>) and keep the existing TODO/exit condition so it’s clear when this pin can be dropped.

Suggested change
# Pin to the f43 commit used to build the current Fedora 43 package.
# Pin to the Fedora 43 dist-git commit used to build the current Fedora 43 package:
# https://src.fedoraproject.org/rpms/rust-nalgebra0.33/c/163057b9125cc59b4ce03b328ad6dc3be3d4b1a1

Copilot uses AI. Check for mistakes.
@christopherco christopherco merged commit 7cccdfa into tomls/base/main Apr 7, 2026
9 checks passed
@christopherco christopherco deleted the bphilip/rust-nalgebra0.33 branch April 7, 2026 05:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants