diff options
| author | Rasmus Villemoes <ravi@prevas.dk> | 2024-11-06 16:02:58 +0100 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2024-11-19 11:26:24 +0000 |
| commit | b5b4fad3e9ba828d411e32229e8a20a171954968 (patch) | |
| tree | 6e95cd9c05dc8b9670a0c4d4f290bbe980b3d050 /bitbake/SECURITY.md | |
| parent | 131872001abf6c76bd1ed7e31cc68c88ede8ca2c (diff) | |
| download | poky-b5b4fad3e9ba828d411e32229e8a20a171954968.tar.gz | |
dosfstools: add backported patch for honouring SOURCE_DATE_EPOCH
Currently, file system images created with mkfs.vfat are not
reproducible, because both the file system creation time and the
volume id are derived from the current time.
Upstream has added a patch for deriving those from SOURCE_DATE_EPOCH,
when defined, many years ago, but unfortunately there is no official
release containing that patch.
The issue [1] is 2.5 years old, so there's no reason to believe such a
release would be just around the corner.
The patch applies cleanly, and e.g. Arch Linux already uses this exact
combination of source tarball and this single patch [2], so I think
this should be ok. It certainly works for the images I've tested on.
[1] https://github.com/dosfstools/dosfstools/issues/179
[2] https://gitlab.archlinux.org/archlinux/packaging/packages/dosfstools/-/blob/main/PKGBUILD?ref_type=heads
(From OE-Core rev: bf9e6bf884bc780547d3dc88c3977c8102e1faeb)
Signed-off-by: Rasmus Villemoes <ravi@prevas.dk>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/SECURITY.md')
0 files changed, 0 insertions, 0 deletions