Skip to content
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

update_engine/init: Use Omaha hash_sha256 attribute for OEM packages #1198

Merged
merged 1 commit into from
Sep 28, 2023

Conversation

pothos
Copy link
Member

@pothos pothos commented Sep 27, 2023

This pulls in
flatcar/update_engine#26
and
flatcar/init#108
to use the newer Omaha hash_sha256 attribute.

How to use

Backport to Alpha

Testing done

Jenkins: cl.update.oem passed.
I've also checked that the flatcar-update invocation uses the XML dump.

  • Changelog entries added in the respective changelog/ directory (user-facing change, bug fix, security fix, update)
  • Inspected CI output for image differences: /boot and /usr size, packages, list files for any missing binaries, kernel modules, config files, kernel modules, etc.

@pothos pothos requested a review from a team September 28, 2023 13:23
@pothos pothos merged commit 75c9eb4 into main Sep 28, 2023
1 check failed
@pothos pothos deleted the kai/omaha-sha256 branch September 28, 2023 14:07
pothos added a commit that referenced this pull request Sep 28, 2023
update_engine/init: Use Omaha hash_sha256 attribute for OEM packages
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants