diff options
| author | Mike Frysinger <vapier@chromium.org> | 2019-11-13 00:07:56 -0500 |
|---|---|---|
| committer | Commit Bot <commit-bot@chromium.org> | 2019-11-13 10:05:11 +0000 |
| commit | c48a593b26d2353eb8788dd85ba8618555180f55 (patch) | |
| tree | 2b57286c1fee99287c81a59420fb9ba418a51dad /tests/vb2_secdata_fwmp_tests.c | |
| parent | b35c2d1012625593c5a4a8be67ca6368aa3304df (diff) | |
| download | vboot-c48a593b26d2353eb8788dd85ba8618555180f55.tar.gz | |
futility: updater: sync mtimes
When unpacking files, unzip will retain timestamps on the outputs.
This makes it easy to recreate the firmware unpacker with the same
exact contents. futility doesn't copy update timestamps anywhere,
so all the mtimes are $now, which makes it impossible to recreate
the same archive.
Update the API to pass around mtimes by reading them from inputs,
setting them on outputs, and copying them across.
BUG=None
TEST=`futility update -a chromeos-firmwareupdate --unpack out` has timestamps on outputs
BRANCH=None
Change-Id: Icc0ae833390115082e1677d190d1b2a029b78439
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/vboot_reference/+/1913067
Reviewed-by: Hung-Te Lin <hungte@chromium.org>
Commit-Queue: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Diffstat (limited to 'tests/vb2_secdata_fwmp_tests.c')
0 files changed, 0 insertions, 0 deletions