Allow to specify keyring file when building the chroot #3236
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
nickygerritsen
force-pushed
the
chroot-allow-to-specify-keyring
branch
from
ae423e2 to
59d66d9
Compare
vmcj
approved these changes
Nov 28, 2025
nickygerritsen
force-pushed
the
chroot-allow-to-specify-keyring
branch
from
59d66d9 to
3d2dda7
Compare
eldering
reviewed
Nov 28, 2025
nickygerritsen
force-pushed
the
chroot-allow-to-specify-keyring
branch
from
3d2dda7 to
8bb1fad
Compare
For the ICPC image we need a custom keyring since the sysops repo has a custom signing key.
nickygerritsen
force-pushed
the
chroot-allow-to-specify-keyring
branch
from
8bb1fad to
4de9608
Compare
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.
For the ICPC image we need a custom keyring since the sysops repo has a custom signing key.