Add dependency checks to verify-release-candidate script #15009
Merged
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.
Which issue does this PR close?
Rationale for this change
Check all build dependencies are available before running the script.
Background: I'll use a separate docker to verify the release candidate. And I always forget to install some of the build dependencies. Then I need to install it and restart from the very beginning. I list all the things I'm aware of (or need to be installed in a fresh ubuntu image) and check them before the build starts.
What changes are included in this PR?
A new function
check_dependencies
indev/release/verify-release-candidate.sh
that checks build dependencies in advance.Are these changes tested?
Yes, I use this version to verify 46.0.0 RC2 release
Are there any user-facing changes?
no