packaging: Drop shim alongside bootupd when switching to systemd-boot - #2349
Merged
Conversation
We sign and boot systemd-boot directly with our own Secure Boot test key (and for sealed images, the UKI itself); shim's chain of trust is never used in either case. Remove shim in the same rpm -e call as bootupd so it doesn't linger in test images, mirroring the same cleanup done in redhat-cop/rhel-bootc-examples#18. Package name varies by arch (shim-x64 on x86_64, shim-aa64 on aarch64), and neither package is guaranteed to be present, so detect the arch and only remove what's actually installed. Assisted-by: AI Signed-off-by: Colin Walters <walters@verbum.org>
jeckersb
approved these changes
Jul 28, 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
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.
We sign and boot systemd-boot directly with our own Secure Boot test key (and for sealed images, the UKI itself); shim's chain of trust is never used in either case. Remove shim in the same rpm -e call as bootupd so it doesn't linger in test images, mirroring the same cleanup done in redhat-cop/rhel-bootc-examples#18.
Package name varies by arch (shim-x64 on x86_64, shim-aa64 on aarch64), and neither package is guaranteed to be present, so detect the arch and only remove what's actually installed.
Assisted-by: AI