rpm: map portage ignition to the ignition-flatcar RPM - #42
Merged
Conversation
The package catalog maps app-admin/ignition and sys-apps/ignition to the RPM name "ignition", but Azure Linux 3 ships no package by that name - only ignition-flatcar. Nothing provides, obsoletes or requires the name "ignition" in any of the base, ms-oss, extended, cloud-native or ms-non-oss repositories. The build still works today only because dnf5 resolves the unmatched spec to the single available ignition-* package. That is incidental behaviour, not something the catalog should depend on: it hides the mistake, and it stops being correct on any release where a package literally named "ignition" exists. Name the RPM explicitly. Verified against a production build: build_image passes the literal string "ignition" to dnf5, and ignition-flatcar-2.22.0-5 is listed under the transaction's top-level "Installing:" section, so the substitution is performed by dnf5 rather than by a dependency or a Provides. No functional change - the same package is installed either way. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: fab45d77-734c-40d0-88ab-1a4d1ac60611
There was a problem hiding this comment.
Pull request overview
Updates the RPM package catalog mapping so Portage app-admin/ignition and sys-apps/ignition resolve explicitly to the Azure Linux 3 RPM ignition-flatcar, avoiding reliance on incidental dnf5 spec resolution behavior.
Changes:
- Map
app-admin/ignitiontoignition-flatcar. - Map
sys-apps/ignitiontoignition-flatcar. - Add an in-file note explaining why the explicit mapping is required on Azure Linux 3.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
aadhar-agarwal
approved these changes
Jul 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
The package catalog maps
app-admin/ignitionandsys-apps/ignitionto the RPM nameignition. Azure Linux 3 ships no package by that name — onlyignition-flatcar. This maps them to the real package name.Why
Nothing in the AzL 3.0 repositories (
base,ms-oss,extended,cloud-native,ms-non-oss) is namedignition, and nothing provides, obsoletes or requires that name. Checked all five repos' repodata directly.The build works today only because dnf5 resolves the unmatched spec to the single available
ignition-*package. Confirmed against a production build:build_imagelogsInstalling 149 RPM packages using dnf5: ... hwdata ignition inih ...— the literal stringignitionis what reaches the dnf5 command line.ignition-flatcar x86_64 2.22.0-5 azurelinux-official-baseunder the top-levelInstalling:header, not underInstalling dependencies:— so dnf5 itself performed the substitution, silently and with no warning.That is incidental behaviour rather than something the catalog should rely on. It hides the mistake, and it stops being correct on any release that ships a package literally named
ignition— which would then be installed in place of the Flatcar fork.Risk
None. The same package is installed either way; this only makes the intent explicit.
Work item: AB#22684