Add the release package when needed#3189
Merged
Conversation
teclator
approved these changes
Feb 19, 2026
Contributor
teclator
left a comment
teclator
left a comment
There was a problem hiding this comment.
LGTM, although the branch is out of date, fill free to merge it there are no conflicts.
imobachgs
added a commit
that referenced
this pull request
Feb 25, 2026
In #3189 used the wrong name for the release packages.
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
2 participants
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.
Problem
According to bsc#1258271 Agama selects the wrong
-releasepackage when using the immutable mode.However, Agama does not select any
-releasepackage, it just selects the base product. The problem is that both release packages provide the same product in this case(see comment #7).
Solution
Add the corresponding release package to the list of
mandatory_packagesfor each mode.