DO NOT MERGE: Test bump sb-signing-utils to latest commit #2324
Conversation
This file contains 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
Signed-off-by: Dave Heller <[email protected]>
|
I have determined the reason for failure is that the level of BR2_HOSTBOOT_STABLE_VERSION is not sufficient to support the recent sb-signing-utls changes. I will not be able to bump the sb-signing-utils version until BR2_HOSTBOOT_STABLE_VERSION is brought up the the level of BR2_HOSTBOOT_LATEST_VERSION, or at least a version including the latest "genPnorImage.pl" changes in hostboot. |
|
Dave Heller <[email protected]> writes:
I have determined the reason for failure is that the level of
BR2_HOSTBOOT_STABLE_VERSION is not sufficient to support the recent
sb-signing-utls changes. I will not be able to bump the
sb-signing-utils version until BR2_HOSTBOOT_STABLE_VERSION is brought
up the the level of BR2_HOSTBOOT_LATEST_VERSION, or at least a version
including the latest "genPnorImage.pl" changes in hostboot.
I suspect we should bump it up anyway, as that version isn't really a
tree that gets updates or anything.
…--
Stewart Smith
OPAL Architect, IBM.
|
|
On 9/10/2018 12:52 AM, Stewart Smith wrote:
Dave Heller ***@***.***> writes:
> I have determined the reason for failure is that the level of
> BR2_HOSTBOOT_STABLE_VERSION is not sufficient to support the recent
> sb-signing-utls changes. I will not be able to bump the
> sb-signing-utils version until BR2_HOSTBOOT_STABLE_VERSION is brought
> up the the level of BR2_HOSTBOOT_LATEST_VERSION, or at least a version
> including the latest "genPnorImage.pl" changes in hostboot.
I suspect we should bump it up anyway, as that version isn't really a
tree that gets updates or anything.
Thanks for letting me know. I'll adjust sb-signing-utils so it's
compatible with the old version.
It was all about wanting to deprecate the use of --hwPrivKeyX in favor
of --hwKeyX, since the same command line option accepts any key. But
it's no big deal to keep supporting both, I just document the latter now.
open-power/sb-signing-utils#8
… --
Stewart Smith
OPAL Architect, IBM.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#2324 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA_abcpztmLLSTWsjvs8vQbk6CtO0LFxks5uZfAngaJpZM4WWu9Y>.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Signed-off-by: Dave Heller [email protected]