chore(comps): annotate backport overlays with category metadata - #17727
Conversation
| replacement = "" | ||
| # Overlays live as one-logical-change-per-file under ./overlays/. | ||
| # See https://github.com/microsoft/azure-linux-dev-tools/blob/main/docs/user/reference/config/overlays.md#per-file-overlay-format-overlaytoml | ||
| overlay-dir = "overlays" |
There was a problem hiding this comment.
It would be great to update the AI instructions to explain when to use this pattern vs. not, and what sort of data to add to each overlay.
There was a problem hiding this comment.
Yes, I'll add a SKILL.md and instruction in a separate PR for using this pattern and suggesting annotations for new overlays.
93c3e9b to
e29cdb5
Compare
23ed86c to
4107a39
Compare
There was a problem hiding this comment.
Pull request overview
This PR annotates the Azure Linux overlays previously flagged by the overlay classifier with structured metadata (a category plus upstream commits/pr/bugs), so future Fedora rebases can mechanically identify and retire backported overlays once they land upstream. It also bumps the pinned azldev version to one that understands these annotations and a new per-file overlay layout.
Changes:
- Inline annotations (17 components): add a
[components.<name>.overlays.metadata]block to existing single-/few-overlay.comp.tomlfiles. Note these attach per-overlay (to the immediately preceding overlay), which is used deliberately in some files (e.g.sos,sssd) but is inconsistent inxbean. - Per-file migration (7 components):
cpio,gnulib,javapackages-tools,qemu,zbar,apache-ivy,cloud-initmove inline overlays intooverlays/*.overlay.tomlfiles (top-level[metadata]+[[overlays]], withsourcepaths rewritten to../to point back at the component root).qemualso consolidates per-section subpackage removals intospec-remove-subpackage(verified output-equivalent against the rendered spec). .azldev-versionbump to enable the newoverlay-files/metadatafeatures; the committed authoritative schema was not regenerated to match.
Reviewed changes
Copilot reviewed 39 out of 39 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
.azldev-version |
Bumps pinned azldev to a version supporting overlay-files/metadata; committed schema not regenerated (flagged). |
base/comps/{ant,atlas,glade,gt,intel-qpl,maven,maven4,xclock,xmvn,xmvn5}/*.comp.toml |
Single-overlay inline metadata annotations (correct attachment). |
base/comps/{sos,sssd,kdump-utils,rust-podman-sequoia,vamp-plugin-sdk}/*.comp.toml |
Multi-overlay inline metadata with distinct per-overlay commits (correct). |
base/comps/xbean/xbean.comp.toml |
Inline metadata; remove/add openjdk retarget pair annotated inconsistently (flagged). |
base/comps/cpio/* |
Migrated to per-file overlay; rmt BR drop annotated. |
base/comps/gnulib/* |
Migrated; temporary Source-URL backport annotated. |
base/comps/javapackages-tools/* |
Migrated; openjdk21-drop multi-commit backport consolidated. |
base/comps/qemu/* |
Migrated to 4 overlay files; subpackage removals consolidated to spec-remove-subpackage (output-equivalent). |
base/comps/zbar/* |
Migrated; GIR-drop (backport) and video-disable (pruning) split into two files. |
base/comps/apache-ivy/* |
Migrated; 0001 overlays lack required description fields (flagged nit). |
base/comps/cloud-init/* |
Migrated to 3 overlay files (cpe-fix, azl4 patch series, branding); ../ source paths point at component-root patches. |
4107a39 to
13381f7
Compare
- apache-ivy: add per-overlay descriptions to the pack200 backport file (hygiene rule #1 — every overlay must explain why the change is needed). - gnulib: drop the redundant per-component overlay-files declaration; the project-wide [default-component-config] already discovers overlays/*.overlay.toml. - grub2: reconcile the os-prober revert overlays (0002 + 0003) to a single category. Re-disabling os-prober restores upstream GRUB's secure default that Fedora diverged from (it will not retire on a Fedora rebase), so both halves are azl-security-compliance and the misleading backport commits are dropped. - external/schemas/azldev.schema.json: regenerate against the pinned azldev (4b5f72c) so the authoritative schema knows the new metadata / overlay-files / BugRef fields used throughout this PR. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
f55c1ce to
7db736c
Compare
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 60 out of 60 changed files in this pull request and generated no new comments.
Comments suppressed due to low confidence (3)
base/comps/components.toml:11
- The project schema is still stale:
external/schemas/azldev.schema.jsondefinesComponentConfigwithadditionalProperties: falsebut has nooverlay-filesproperty (lines 102-155), and it also lacks the new overlay metadata definitions. Consequently this newly added setting is rejected by the repository's authoritative schema even though the pinned CLI accepts it. Regenerate and commit the schema using the final.azldev-versionpin.
overlay-files = ["overlays/*.overlay.toml"]
base/comps/gnulib/overlays/0001-fix-source-url-filter.overlay.toml:9
- This is not a backport of
41cae067: that Fedora commit replaces the erislabs URLs with salsa.debian.org, whereas these overlays deliberately retain the old URLs and add fragment hints as a temporary filter workaround. The pinned azldev definition reservesazl-temp-workaroundfor transient workarounds waiting on an external fix, so labeling thisupstream-backportrecords inaccurate provenance for the retirement tooling.
category = "upstream-backport"
base/comps/gt/overlays/0001-add-std-gnu89-cflags.overlay.toml:10
- The referenced Fedora commit does not backport this
-std=gnu89change; it adds and applies the source-levelgt-0.4-std23.patch. This overlay is an alternative compiler-mode workaround that can be removed once that Fedora fix is imported, which matchesazl-temp-workaround, notupstream-backport. Keeping the current category makes the structured provenance claim that the Fedora change itself was backported.
category = "upstream-backport"
67be8e2 to
6f1f478
Compare
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 61 out of 61 changed files in this pull request and generated no new comments.
Comments suppressed due to low confidence (1)
base/comps/vamp-plugin-sdk/overlays/0001-re-number-existing-patch.overlay.toml:14
- This metadata says the fix is only
upstreamable, but the immediately preceding comment identifies it as already shipped in Fedora Rawhide 2.10-4. Under the status convention used here, that makes itupstreamed; keeping the current value prevents the rebase-retirement tooling from recognizing the Fedora landing. Record the Fedora dist-git commit as well so the retirement provenance is machine-readable.
6f1f478 to
6dbe7ee
Compare
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 61 out of 61 changed files in this pull request and generated no new comments.
Comments suppressed due to low confidence (1)
base/comps/gnulib/overlays/0001-fix-source-url-filter.overlay.toml:2
- This shim does not backport
41cae067: it keeps the old URLs and adds filename fragments while waiting for that Fedora change. Calling it a backport conflicts with theazl-temp-workaroundclassification and may mislead future retirement work; describe it as a workaround pending that commit instead.
# Temporary backport of upstream Fedora commit 41cae067 ("Update to git4a3650d
# branch stable-202601") which updated the Source URLs from erislabs.net to
6dbe7ee to
e3b0ed9
Compare
|
/azp run |
|
Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command. |
tobiasb-ms
left a comment
There was a problem hiding this comment.
I confirmed via before/after runs of azldev component list --all-components that the only changes are the addition of metadata and a few new description fields.
Seems good.
Annotate every overlay surfaced by the overlay classifier with structured [metadata] so future Fedora rebases can mechanically identify and retire overlays that have landed upstream. - Add a project-wide [default-component-config] in base/comps/components.toml with overlay-files = ["overlays/*.overlay.toml"], so each component discovers its own per-file overlays without redeclaring the glob. - Migrate all 24 annotated components to the per-file overlay-files layout: inline overlays move into per-logical-change overlays/*.overlay.toml files, each carrying one file-level [metadata] block. Patch source paths are rewritten to ../<patch> to point back at the component root. - Categories: most overlays are upstream-backport (with verified commits); the rest are labelled by intent (azl-pruning, azl-security-compliance, azl-compatibility, azl-branding-policy, and azl-temp-workaround for the gnulib source-URL filter shim and the gt -std=gnu89 compiler workaround, which are alternative/transient fixes rather than backports of their referenced Fedora commits). Pure annotation/restructuring: the rendered spec is byte-identical before and after (verified via prepare-sources), and azldev comp update reports no lock drift (metadata is excluded from fingerprints).
Regenerate external/schemas/azldev.schema.json against the pinned .azldev-version (661c69b6) so the authoritative schema matches the CLI. Adds the overlay-files property to ComponentConfig and the OverlayMetadata definitions (category, upstream-status, commits) required by the per-file overlay layout.
e3b0ed9 to
7aee486
Compare
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 62 out of 62 changed files in this pull request and generated no new comments.
Comments suppressed due to low confidence (1)
base/comps/apache-ivy/overlays/0001-pack200-commons-compress.overlay.toml:7
- This file-level metadata is stamped onto all six overlays, but Source5 is not part of the referenced backport:
d772841adds/renamesplugins/pack/Pack200Packing.java, whileremove-Pack200Packing-java.patchdeletes that file again. Classifying the whole document asupstream-backporttherefore gives the downstream deletion false provenance and could make retirement tooling drop it when Fedora importsd772841. Split the Source5 removal into a separately classified AZL overlay document (and keep only the exact backport under this metadata), or classify the combined change as a non-backport.
category = "upstream-backport"
upstream-status = "upstreamable"
commits = [{ url = "https://github.com/apache/ant-ivy/commit/d77284167b6695903b80c72afed57469ffab5cc3" }]
|
/azp run |
|
Azure Pipelines: 3 pipeline(s) were filtered out due to trigger conditions. |
Discussed offline; changes look good now.
This PR annotates the overlays surfaced by the overlay classifier with structured
[metadata](acategoryplus, for genuine backports, the verified upstreamcommits), so future Fedora rebases can mechanically identify and retire overlays that have landed upstream. It also pinsazldevto a version that understands these annotations and the per-fileoverlay-fileslayout, and regenerates the authoritative JSON schema to match.Changes:
Project config
base/comps/components.tomlgains a project-wide[default-component-config]withoverlay-files = ["overlays/*.overlay.toml"], so every component discovers its ownoverlays/*.overlay.tomlwithout redeclaring the glob.Per-file overlay migration (24 components)
ant, apache-ivy, atlas, cloud-init, cpio, glade, gnulib, grub2, gt, intel-qpl, javapackages-tools, kdump-utils, maven, maven4, rust-podman-sequoia, sos, sssd, vamp-plugin-sdk, xbean, xclock, xmvn, xmvn5, xsimd, zbar — inline overlays were moved into per-logical-change
overlays/*.overlay.tomlfiles, each carrying one file-level[metadata]block. Multi-commit backports (e.g.javapackages-toolsopenjdk21 drop) consolidate related upstream commits into a single file viacommits = [url1, url2, …]. Patchsourcepaths are rewritten to../<patch>to point back at the component root.Category spread
Most overlays are
upstream-backport(with verified upstreamcommits). A few non-backport overlays surfaced alongside them are labelled accordingly:azl-pruning(e.g. grub2 xen-module disable),azl-security-compliance(grub2 os-prober reverts — restoring upstream GRUB's secure default Fedora diverged from),azl-compatibility,azl-branding-policy, andazl-temp-workaroundfor thegnulibsource-URL filter shim and thegt-std=gnu89compiler workaround, which are alternative/transient fixes rather than backports of their referenced Fedora commits.Validation
prepare-sourcesdiffs for every migrated component).azldev comp updatereports no lock drift (metadata is excluded from fingerprints; theoverlay-filesrestructuring keeps the same input set).azldev comp renderall passed in PR check.