Migrating to thud branch with raspberry pi

Building in thud environment I get following warnigs: I have not changed the patch file and is cloned from git clone -b thud git://github.com/mendersoftware/meta-mender

WARNING: u-boot-1_2018.07-r0 do_patch:
Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
The context lines in the patches can be updated with devtool:
    devtool modify <recipe>
    devtool finish --force-patch-refresh <recipe> <layer_path>

Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.html
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10450

Details:
Applying patch 0001-CONFIGS-rpi-enable-mender-requirements.patch
patching file configs/rpi_0_w_defconfig
Hunk #1 succeeded at 36 (offset 11 lines).
patching file configs/rpi_2_defconfig
Hunk #1 succeeded at 36 (offset 4 lines).
patching file configs/rpi_3_32b_defconfig
Hunk #1 succeeded at 39 (offset 5 lines).
patching file configs/rpi_3_defconfig
Hunk #1 succeeded at 39 (offset 5 lines).
patching file configs/rpi_defconfig
Hunk #1 succeeded at 36 (offset 4 lines).
patching file include/configs/rpi.h
Hunk #1 succeeded at 77 with fuzz 2 (offset -14 lines).

Now at patch 0001-CONFIGS-rpi-enable-mender-requirements.patch

Edit: @mirzak: Formatting

Hi @aps and welcome to the Mender community.

The mentioned warnings is something that has been there for a while, but should not affect functionality.

You are welcome to clean that up and send a pull-request :slight_smile:

1 Like