[rhcos-4.17] support cosa buildextend-qemu-secex
#3929
Merged
Conversation
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
Member
Author
|
We effectively did this in This is just applying something similar to older streams. |
- 'stages/coreos.platform: use shutil.copy' - 'stages/selinux: don't require file_contexts if labels passed' Both are merged and come with osbuild-130.rpm (cherry picked from commit 7f06c1d)
`qemu-secex` is the artifact name used in meta.json and elsewhere so let's support calling it that way like we do for other artifacts. The `cmd-buildextend-secex` symlink is left in place for backwards compatibilty.
dustymabe
force-pushed
the
dusty-buildextend-qemu-secex
branch
from
69c460a to
86386eb
Compare
Member
Author
|
Cherry-picked a few commits from |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
qemu-secexis the artifact name used in meta.json and elsewhere so let's support calling it that way like we do for other artifacts.The
cmd-buildextend-secexsymlink is left in place for backwards compatibilty.