Skip to content

update-m1n1: Don't store name and timestamp in the gzip header - #76

Open
yarosvla wants to merge 1 commit into
AsahiLinux:mainfrom
yarosvla:update-m1n1-gzip-no-name
Open

yarosvla wants to merge 1 commit into
AsahiLinux:mainfrom
yarosvla:update-m1n1-gzip-no-name

Conversation

@yarosvla

Copy link
Copy Markdown

On rpm-ostree based systems files in /usr have an mtime of 0. GNU gzip warns that the timestamp is out of range and exits with status 2, which aborts update-m1n1 (set -e) before boot.bin is replaced.

Pass -n to gzip so the original file name and timestamp are not stored. The decompressed data is unchanged and the resulting boot.bin becomes reproducible.

Fixes #71

On rpm-ostree based systems files in /usr have an mtime of 0. GNU gzip
warns that this timestamp is out of range for the gzip format and exits
with status 2, which aborts update-m1n1 due to `set -e` before boot.bin
is replaced.

Pass -n to gzip so the original file name and timestamp are not stored.
The decompressed data is unchanged and the resulting boot.bin becomes
reproducible.

Fixes: AsahiLinux#71
Signed-off-by: Yaroslav Vlasov <vlasov.yaroslav.00@gmail.com>
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.

update-m1n1 aborts on ostree epoch-zero u-boot mtime

1 participant