-
Notifications
You must be signed in to change notification settings - Fork 190
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Cherry scarthgap]: fix: package artifact-verify-key.pem in mender-update #2208
[Cherry scarthgap]: fix: package artifact-verify-key.pem in mender-update #2208
Conversation
@mender-test-bot, Let me know if you want to start the integration pipeline by mentioning me and the command "start pipeline". my commands and optionsYou can trigger a pipeline on multiple prs with:
You can start a fast pipeline, disabling full integration tests with:
You can trigger GitHub->GitLab branch sync with:
You can cherry pick to a given branch or branches with:
|
@mender-test-bot start pipeline |
Hello 😺 I created a pipeline for you here: Pipeline-1556542161 Build Configuration Matrix
|
The path ${sysconfdir}/mender/artifact-verify-key.pem was not explicitly added to a FILES:${} variable, and therefore added to the default ${PN}-named package. As that is derived from the recipe file name, it ended up as the only file in the "mender" package, yielding artifact signature verification in mender-update broken. This adds the verification key to the "mender-update" package. Changelog: Title Ticket: MEN-7204 Signed-off-by: Josef Holzmayr <[email protected]> (cherry picked from commit 22c5088)
fda288b
to
c218cd4
Compare
Merging these commits will result in the following changelog entries: Changelogsmeta-mender (cherry-scarthgap-fix_verification_key_packaging)New changes in meta-mender since scarthgap: Bug Fixes
|
@mender-test-bot start pipeline |
Hello 😺 I created a pipeline for you here: Pipeline-1558694797 Build Configuration Matrix
|
Cherry pick of PR: #2207
For you :)