ping

Hi, I would like to install linux-firmware-ath10k and linux-firmware-imx-sdma-imx7d firmware package to my image recipe in kirkstone release but when i append them to IMAGE_INSTALL somewhy each

Agreed, there is an issue here. I just don't think the patch looks quite right. You're arguing we need to set crtime, ctime and atime which I can believe. The mtime however should be fine from the

This patch should be sent upstream first. Same as in your master submission. Alex

From: Christoph Lauer <christoph.lauer@...> Add SDK_ZIP_OPTIONS to remove symbolic link creation in zip archive or add= options, e.g. for encryption of the zip archive. Signed-off-by:

python2 has been deprecated, use python3 instead Signed-off-by: Sakib Sajal <sakib.sajal@...> --- ...plot.py-ask-for-python3-specifically.patch | 35 +++++++++++++++++++

This is not inappropriate, or oe-specific, please send the patch upstream first. Alex

Hi Richard, Thank you for the comment! Well, the environment described in reproducible guides currently does not provide binary reproducability due to extfs implementation. Moreover, building on some

python2 has been deprecated, use python3 instead Signed-off-by: Sakib Sajal <sakib.sajal@...> --- ...plot.py-ask-for-python3-specifically.patch | 35 +++++++++++++++++++

<richard.purdie@...> wrote: good catch. LGTM

Per discussion on GitHub, this is fine to merge as is. Thanks

Whilst SDE definitely needs to be exported, the fallback does not as it is only used in our python code via the datastore. It was introduced as an export in

The source date epoch for gcc isn't being transferred from the shared workdir to the current WORKDIR for the specific recipe. This results in the clamping code within sstate.bbclass using a value from

Understood. Great. Thank you. -- Patrick Williams

This patchset was tested and sent out for review prior to the 3.0.7 upgrade hitting master. Note that I have the 3.0.7 upgrade in the patches currently under test for both langdale and

Ya, I think what you have is fine with a minor change; the limitations of not handling non-kernel shared source very well isn't changing. I did leave a minor comment in github, but otherwise LGTM

When building with CONFIG_MODVERSIONS=3Dy and CONFIG_RANDSTRUCT=3Dy we ne= ed to copy the build assets generated for the randstrutc seed to STAGING_KERNEL_BUILDDIR, otherwise the out-of-tree modules

I don't think this is the correct behaviour as it will effectively remove all timestamp information. Many of the timestamps are ok to use and are reproducible (e.g anything from the packaging

Instead of picking up this patch, wouldn't it make a lot more sense to go to 3.0.7 like we did with [1]? Since 3.0.7 contains a HIGH severity CVE fix as well as the one mentioned here, it seems like

From: Sergei Zhmylev <s.zhmylev@...> Ext2/3/4 FS contains not only mtime, but also ctime, atime and crtime. Currently, all the files are being added into the rootfs image using mkfs -d