data: import RH v4 key or rhel-10.1+ only#2101
Merged
achilleas-k merged 6 commits intoosbuild:rhel-9.7_10.1from Dec 19, 2025
Merged
data: import RH v4 key or rhel-10.1+ only#2101achilleas-k merged 6 commits intoosbuild:rhel-9.7_10.1from
achilleas-k merged 6 commits intoosbuild:rhel-9.7_10.1from
Conversation
There is a new produce signing key (v4) that recently added [0][1] and will be used for rhel-10.1 and rhel-9.7. We do not import it for rhel-9.7 (yet) but we do add it for 10.1+. Note that this also adds a extra newline (`\n`) after the `-----BEGIN PGP PUBLIC KEY BLOCK-----` which is omited in the upstream key but that is apparently a mistake. [0] https://access.redhat.com/security/team/key [1] https://security.access.redhat.com/data/6afedf8f.txt
achilleas-k
requested review from
bcl,
lzap,
ondrejbudai and
supakeen
and removed request for
supakeen
These check against the main branch of the other projects, which will eventually fail anyway.
Contributor
|
The patch also pulls an extra commit, can you elaborate in the description I guess you are fixing tests so it is original work? |
Member
Author
Done. |
Member
Author
|
https://gitlab.com/redhat/services/products/image-builder/ci/images/-/jobs/12487309975 download.eng.bos has been retired, so I'm pulling in a commit from main that updates the repo snapshots. |
The URL that we used stopped working, but we should have been using rpmrepo snapshot for testing anyway. Let's fix it. Signed-off-by: Tomáš Hozza <thozza@redhat.com>
Member
Author
|
Had to update ssh keys and the CI variable name in the test configs. |
Backport of c00ecdc
achilleas-k
force-pushed
the
rhel-9.7_10.1
branch
from
f684ead to
e61df34
Compare
ondrejbudai
approved these changes
Dec 19, 2025
ochosi
approved these changes
Dec 19, 2025
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
6 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.
There is a new produce signing key (v4) that recently added [0][1] and will be used for rhel-10.1 and rhel-9.7. We do not import it for rhel-9.7 (yet) but we do add it for 10.1+.
Note that this also adds a extra newline (
\n) after the-----BEGIN PGP PUBLIC KEY BLOCK-----which is omited in the upstream key but that is apparently a mistake.[0] https://access.redhat.com/security/team/key
[1] https://security.access.redhat.com/data/6afedf8f.txt
Backport of #2097
The second commit disables reverse dependency tests because it doesn't make sense to test a release branch against the
mainbranch of osbuild-composer and image-builder-cli.