| commit | 609e2fa5f72079601e4be25d6ff801c99eacafdf | [log] [tgz] |
|---|---|---|
| author | Bowgo Tsai <bowgotsai@google.com> | Thu Feb 13 18:09:04 2025 +0800 |
| committer | Android Build Cherrypicker Worker <android-build-cherrypicker-worker@google.com> | Sun Feb 16 20:07:40 2025 -0800 |
| tree | f10b299b526b7dcf3fc7482a5a7a824c20f6ce84 | |
| parent | 39de17cfe50d08373350f456a459643cc8560dc6 [diff] |
Fix pvmfw.img signing error
This commit fixes the following error, by extracting
'SYSTEM/apex/com.android.virt.apex' from a target-files
zip file to a temp file, then gets the Microdroid AVB
key from it.
FileNotFoundError:
[Errno 2] No such file or directory: 'SYSTEM/apex/com.android.virt.apex'
Bug: 384813199
Bug: 395932577
Test: m sign_target_files_apks
Test: sign_target_files_apks --allow_gsi_debug_sepolicy \
--extra_apex_payload_key com.android.virt.apex= \
-e com.android.virt.apex= \
gsi_arm64-target_files-${build_id}.zip signed.zip
Test: unzip signed.zip IMAGES/pvmfw.img
Test: avbtool extract_public_key --key external/avb/test/data/testkey_rsa4096.pem --out key.pub
Test: grep -U -F -f key.pub IMAGES/pvmfw.img => grep: IMAGES/pvmfw.img: binary file matches
(cherry picked from https://android-review.googlesource.com/q/commit:a7d257cc8fc0055812b93912926e3f5bf827f162)
Merged-In: I4a4129d221778906fb739a574d7adb48e91e9eda
Change-Id: I4a4129d221778906fb739a574d7adb48e91e9eda
This is the Makefile-based portion of the Android Build System.
For documentation on how to run a build, see Usage.txt
For a list of behavioral changes useful for Android.mk writers see Changes.md
For an outdated reference on Android.mk files, see build-system.html. Our Android.mk files look similar, but are entirely different from the Android.mk files used by the NDK build system. When searching for documentation elsewhere, ensure that it is for the platform build system -- most are not.
This Makefile-based system is in the process of being replaced with Soong, a new build system written in Go. During the transition, all of these makefiles are read by Kati, and generate a ninja file instead of being executed directly. That's combined with a ninja file read by Soong so that the build graph of the two systems can be combined and run as one.